On Tue, Apr 05, 2016 at 01:47:33PM +0200, Cédric Bosdonnat wrote: > To add this support, the existing code searches for either the viostor > or the VMDP (Virtual Machine Driver Pack) files and updates the registry > accordingly. > > Note that VMDP's block driver pvvxblk depends on the ballooning driver > pvvxbn.
Can you please elaborate on this? Is the balloon driver *used* by the storage driver so that the latter won't work without the former? What will happen if the virtio-balloon device isn't configured in the VM? Or is it just a matter of ordering of the balloon driver within the driver start sequence, so that it can get its hands on the system as early as possible for its own purposes, and the storage driver doesn't require balloon's presence? Thanks, Roman. _______________________________________________ Libguestfs mailing list Libguestfs@redhat.com https://www.redhat.com/mailman/listinfo/libguestfs
