On 1/18/19 7:47 AM, Vladimir Sementsov-Ogievskiy wrote: >> >> Interesting, I don't get it again. Searched in outlook online, I found only >> v2 of it, >> checked spam folder and filters. Magic.
Weird indeed. Maybe there's enough @ signs due to .texi content in there that a spam filter somewhere along the line ate it silently? >> >> anyway, I can look at >> https://lists.gnu.org/archive/html/qemu-devel/2019-01/msg04328.html >> >> > > just look at it in your qemu-nbd-list-v4 tag: Thanks for that extra effort. > > > Only expose MBR partition @var{num}. Understands physical partitions > > 1-4 and logical partitions 5-8. > > I'm afraid, I'm too lazy to sort out these things I don't know, so just > believe. It at least > corresponds to limits in code that it should be 1 <= partition <= 8 ;) > > > @item -c, --connect=@var{dev} > > Connect @var{filename} to NBD device @var{dev} (Linux only). > > @item -d, --disconnect > > Disconnect the device @var{dev} (Linux only). > > Yes, and we now have clean code which establish this limitation > > > @item -e, --shared=@var{num} > > Allow up to @var{num} clients to share the device (default > > @samp{1}). Safe for readers, but for now, consistency is not > > guaranteed between multiple writers. > > Hmm, don't understand, why you decided to move @samp{1}). on the following > line, it looks > better as it was. And with a period it's only 69 symbols, the file have a lot > longer lines. Emacs auto-reflowed the line as I edited the paragraph. End-of-lines doesn't really matter in .texi files (it gets reflowed again in the creation of output documentation from the .texi input), so if my editor tries to stick to certain column lengths, I don't really fight it. > > @example > > qemu-nbd \ > > --object tls-creds-x509,id=tls0,endpoint=server,dir=/path/to/qemutls \ > > --tls-creds tls0 -t -x subset -p 10810 \ > > --image-opts > driver=raw,offset=1M,length=1M,file.driver=file,file.filename=file.raw > > @end example > > I don't know tls-related, the other options looks fine. I looked through past git logs to see the command lines that Dan used when initially implementing things; as well as comparison to iotest 233. > > upd (decided to run the command, with dropped tls): > looks fine but not work, as s/length/size. Oh, good catch! Will fix. > > > > > Serve a read-only copy of just the first MBR partition of a guest > > image over a Unix socket with as many as 5 simultaneous readers, with > > a persistent process forked as a daemon: > > > > @example > > qemu-nbd --fork -t -e 5 -s /path/to/sock -p 1 -r -f qcow2 file.qcow2 > > @end example > > Oops. s/-s/-k/, s/-p/-P/, Ouch. Yes, thanks for catching that. and idea: may be, use self-descriptive long option names in > examples? Hmm. The nice part about short options is that they are less typing and shorter lines; but verbose options are also useful. Maybe listing the same example twice, in both the short and long form? > > > > > Expose the guest-visible contents of a qcow2 file via a block device > > /dev/nbd0 (and possibly creating /dev/nbd0p1 and friends for > > partitions found within), then disconnect the device when done. > > @emph{CAUTION}: Do not use this method to mount filesystems from an > > untrusted guest image - a malicious guest may have prepared the image > > to attempt to trigger kernel bugs in partition probing or file system > > mounting. > > > > @example > > should we note, that nbd kernel-module should be loaded for this to work? Yes, that's worth mentioning (some distros include that module to be running or autoload already, but it's not universal, so such a note is indeed warranted). > > > qemu-nbd -c /dev/nbd0 -f qcow2 file.qcow2 > > qemu-nbd -d /dev/nbd0 > > @end example > > With fixed wrong option names and s/length/size: > for 03/21: > Reviewed-by: Vladimir Sementsov-Ogievskiy <vsement...@virtuozzo.com> > > -- Eric Blake, Principal Software Engineer Red Hat, Inc. +1-919-301-3226 Virtualization: qemu.org | libvirt.org
signature.asc
Description: OpenPGP digital signature
