On 05/20/2016 04:17 AM, Eugen Block wrote:
For completeness sake, I ran an additional test case and now see the following behavior:
- KVM, boot from volume: "driver_name" provided by Nova - KVM, boot from image: "driver_name" provided by libvirt - Xen, boot from volume: "driver_name" provided by Nova - Xen, boot from image: error, no-one provides "driver_name"
Ah, thanks for this summary. Can you provide the full <disk> config produced by nova for the KVM and Xen boot from image cases? Sensitive info can be replaced with 'xxxx' or something else of your choosing :-).
So to achieve some kind of consistency it seems that it would be necessary to change libvirt to provide the driver name if an instance is launched from an image without creating a new volume.
Network backed disks (<disk type='network .../>) in Xen are only supported via qdisk. So I think it is reasonable for the libvirt libxl driver to use 'qemu' when a driver name is not specified. Also, it should produce an error if the driver name is specified but not equal to qemu.
What is the way to go for me now? Should I file a bug report?
Yes, please. File it under the Virtualization:Tools component and provide the <disk> config requested above, along with other relevant info from this thread. Regards, Jim -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org