On Sat, May 21, 2016 at 11:53:12PM +0200, Wouter Verhelst wrote: > On Tue, May 17, 2016 at 10:50:01AM -0600, Eric Blake wrote: > > Option 2: An alternative solution would be to allow nbdkit to fail > > NBD_OPT_LIST with NBD_REP_ERR_UNSUP, at which point qemu client of 2.6 > > should just ignore the failure and proceed on to NBD_OPT_EXPORT_NAME. > > It is the fact that it is returning NBD_REP_ACK with 0 names that is > > giving qemu grief. > > I think this makes most sense. If you don't look at export names, you > effectively don't support them, and you can't be expected to send a list > of "supported" names, because *everything* is supported (or, put a > different way, nothing is). > > I note that nbdkit has been patched to now send the empty name, which > is also fine as a way to fix interoperability in this particular case --
nbdkit now fully supports export names via the '-e' option. This discussion is moot. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com virt-p2v converts physical machines to virtual machines. Boot with a live CD or over the network (PXE) and turn machines into KVM guests. http://libguestfs.org/virt-v2v