On Thu, Jan 20, 2022 at 11:22:28AM -0600, Eric Blake wrote:
On Wed, Jan 19, 2022 at 06:57:48PM +0000, Richard W.M. Jones wrote:
qemu-nbd --shared (-e) flag controls how many clients can connect concurrently. 0 means unlimited.
As of qemu commit 3dcf56e625 (v6.0.0). Does v2v need to cater to older qemu, or are we at the point where we can say "using this version of v2v requires at least X minimum version of qemu"?
For modular virt-v2v we need a new qemu. It's not pinned down in the virt-v2v README file but we can certainly demand at least v6.0.
We want to allow the sockets to be queried by other processes while virt-v2v is running and it should be safe to do this. The default configuration of qemu-nbd doesn't allow this so add --shared=0.
Note this does not (in current qemu) enable multi-conn because we aren't using the -r (read-only) flag.
Yeah, I still need to work on that for qemu 7.0 (my attempt for 6.2 garnered some interesting review comments from Kevin, which I still need to address).
Thanks, Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones Read my programming and virtualization blog: http://rwmj.wordpress.com libguestfs lets you edit virtual machines. Supports shell scripting, bindings from many languages. http://libguestfs.org