On Tue, 2016-04-05 at 15:52 +0300, Roman Kagan wrote:
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?
It's just that without the virtio balloon driver installed, the virtio block one won't start properly, resulting in the famous 0x7B error.
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?
It's not ordering, it really requires it. -- Cedric