Hi, I filed a bug report (Bug 981094). For completeness, here are the <disk> configs from nova: Xen: ---cut here--- <disk type='network' device='disk'> <driver type='raw' cache='none'/> <auth username='openstack'> <secret type='ceph' uuid='****'/> </auth> <source protocol='rbd' name='images/867682d4-1ff0-4937-9d66-0423ea512679_disk'> <host name='HOST1' port='6789'/> <host name='HOST2' port='6789'/> <host name='HOST3' port='6789'/> </source> <target dev='xvda' bus='xen'/> </disk> ---cut here--- KVM: ---cut here--- <disk type="network" device="disk"> <driver type="raw" cache="none"/> <source protocol="rbd" name="images/36341065-4fbb-4e3f-bd20-db0eb7299832_disk"> <host name="HOST1" port="6789"/> <host name="HOST2" port="6789"/> <host name="HOST3" port="6789"/> </source> <auth username="openstack"> <secret type="ceph" uuid="****"/> </auth> <target bus="virtio" dev="vda"/> </disk> ---cut here--- The resulting <disk> config for kvm contains the driver name: ---cut here--- <disk type='network' device='disk'> <driver name='qemu' type='raw' cache='none'/> <auth username='openstack'> <secret type='ceph' uuid='****'/> </auth> <source protocol='rbd' name='images/36341065-4fbb-4e3f-bd20-db0eb7299832_disk'> <host name='HOST1' port='6789'/> <host name='HOST2' port='6789'/> <host name='HOST3' port='6789'/> </source> <backingStore/> <target dev='vda' bus='virtio'/> <alias name='virtio-disk0'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </disk> ---cut here--- Thanks for your assistance, Jim. I CC'd you to the bug, if that's okay. Best regards, Eugen Zitat von Jim Fehlig <jfehlig@suse.com>:
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
-- Eugen Block voice : +49-40-559 51 75 NDE Netzdesign und -entwicklung AG fax : +49-40-559 51 77 Postfach 61 03 15 D-22423 Hamburg e-mail : eblock@nde.ag Vorsitzende des Aufsichtsrates: Angelika Mozdzen Sitz und Registergericht: Hamburg, HRB 90934 Vorstand: Jens-U. Mozdzen USt-IdNr. DE 814 013 983 -- To unsubscribe, e-mail: opensuse-cloud+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-cloud+owner@opensuse.org