http://bugzilla.opensuse.org/show_bug.cgi?id=981094 Bug ID: 981094 Summary: OpenStack Mitaka: Launching xen instance fails with rbd image Classification: openSUSE Product: openSUSE Distribution Version: Leap 42.1 Hardware: x86-64 OS: openSUSE 42.1 Status: NEW Severity: Normal Priority: P5 - None Component: Virtualization:Tools Assignee: virt-bugs@suse.de Reporter: eblock@nde.ag QA Contact: qa-bugs@suse.de CC: jmozdzen@nde.ag Found By: --- Blocker: --- Created attachment 677903 --> http://bugzilla.opensuse.org/attachment.cgi?id=677903&action=edit nova compute logs and xml configs Issue: I have an OpenStack Cloud (Mitaka) running on Leap with a ceph cluster as storage backend, all the relevant services use ceph as storage backend (glance, cinder-volume, nova). Launching an instance from an rbd image fails on Xen hypervisor due to missing backend driver name 'qemu' in the resulting xml config. Steps to reproduce: 1. Boot an instance with nova CLI or Horizon on a Xen hypervisor, the source image should be located in an rbd cluster. Actual result: Instance fails with ERROR state. nova-compute.log reports libvirtError: internal error: libxenlight failed to create new domain 'instance-00000229' Please find detailed (verbose) log output from nova-compute for both xen and kvm hypervisor in the attached tarball. The log files are truncated. Expected result: Instance boots with a clone of the provided rbd image. Additional information: The instance does boot successfully if you choose "boot from image (creates a new volume)", in that case nova provides the driver name, there's a function call pick_disk_driver_name() in /usr/lib/python2.7/site-packages/nova/virt/libvirt/volume/volume.py. If no volume is created, libxl has to provide the driver name. The package versions I'm using: ---cut here--- compute1:~ # rpm -qi python-nova-13.0.1~a0~dev46-1.1.noarch Name : python-nova Version : 13.0.1~a0~dev46 Release : 1.1 Architecture: noarch Install Date: Di 10 Mai 2016 12:38:57 CEST Group : Development/Languages/Python Size : 16549000 License : Apache-2.0 Signature : RSA/SHA256, Mo 09 Mai 2016 13:39:20 CEST, Key ID 893a90dad85f9316 Source RPM : openstack-nova-13.0.1~a0~dev46-1.1.src.rpm Build Date : Mo 09 Mai 2016 13:38:09 CEST Build Host : cloud113 Relocations : (not relocatable) Vendor : obs://build.opensuse.org/Cloud:OpenStack URL : https://launchpad.net/nova Summary : OpenStack Compute (Nova) - Python module Description : This package contains the core Python module of OpenStack Nova. Distribution: Cloud:OpenStack:Mitaka / openSUSE_Leap_42.1 ################################################################# compute1:~ # rpm -qi xen-libs Name : xen-libs Version : 4.7.0_03 Release : 440.1 Architecture: x86_64 Install Date: Di 10 Mai 2016 13:59:52 CEST Group : System/Kernel Size : 1560640 License : GPL-2.0 Signature : RSA/SHA256, Fr 06 Mai 2016 16:33:12 CEST, Key ID a193fbb572174fc2 Source RPM : xen-4.7.0_03-440.1.src.rpm Build Date : Fr 06 Mai 2016 16:31:47 CEST Build Host : build74 Relocations : (not relocatable) Vendor : obs://build.opensuse.org/Virtualization ################################################################# compute1:~ # rpm -qi qemu-block-rbd Name : qemu-block-rbd Version : 2.5.93 Release : 327.6 Architecture: x86_64 Install Date: Di 10 Mai 2016 14:53:26 CEST Group : System/Emulators/PC Size : 84024 License : BSD-3-Clause and GPL-2.0 and GPL-2.0+ and LGPL-2.1+ and MIT Signature : (none) Source RPM : qemu-2.5.93-327.6.src.rpm Build Date : Di 10 Mai 2016 14:42:57 CEST Build Host : compute1.cloud.hh.nde.ag ---cut here--- As you can see, we're running a self-compiled version of qemu. I'm not sure if it still holds true with above version, but at least with earlier versions, we had to modify the spec file to enable RBD support. 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" Please find further information in the mailing list: https://lists.opensuse.org/opensuse-cloud/2016-05/msg00000.html I have attached a tarball containing 3 xml files (nova-xen-conf.xml, nova-kvm-conf.xml, virsh-kvm-conf.xml) and the nova-compute.logs for both compute nodes (xen and kvm). You can find the <disk> config section created by nova in nova-compute logs or in the seperate xml files. The file virsh-kvm-conf.xml contains output of 'virsh dumpxml <instance>' to illustrate the resulting <disk> section containing a driver name. -- You are receiving this mail because: You are on the CC list for the bug.