openstack team mailing list archive

[Vishvananda Ishaya <vishvananda@xxxxxxxxx>]

Looks like there is something wrong with the xml.  You might try navigating to the instances dir/instance-00000001/libvirt.xml and see if there is anything that looks wrong.
if you try: virsh create dir/instance-00000001/libvirt.xml you might get some more useful error message about what is wrong with the xml
(or LIBVIRT_DEBUG=1 virsh create...)

Vish

On Aug 16, 2011, at 4:16 PM, Joshua Harlow wrote:

> Ok, seems like it go past this error.
> 
> 2011-08-16 16:12:24,218 DEBUG nova.utils [-] Running cmd (subprocess): sudo losetup --detach /dev/loop0 from (pid=5538) execute /home/ctoteam/nova/nova/utils.py:143
> 2011-08-16 16:12:24,262 WARNING nova.virt.libvirt_conn [-] instance instance-00000001: ignoring error injecting data into image 3 (Unexpected error while running command.
> Command: sudo tune2fs -c 0 -i 0 /dev/loop0
> Exit code: 1
> Stdout: 'tune2fs 1.42-WIP (02-Jul-2011)\n'
> Stderr: "tune2fs: Invalid argument while trying to open /dev/loop0\nCouldn't find valid filesystem superblock.\n")
> libvir: Xen Daemon error : XML error: failed to parse domain description
> 2011-08-16 16:12:24,270 ERROR nova.exception [-] Uncaught exception
> (nova.exception): TRACE: Traceback (most recent call last):
> (nova.exception): TRACE:   File "/home/ctoteam/nova/nova/exception.py", line 97, in wrapped
> (nova.exception): TRACE:     return f(*args, **kw)
> (nova.exception): TRACE:   File "/home/ctoteam/nova/nova/virt/libvirt/connection.py", line 603, in spawn
> (nova.exception): TRACE:     domain = self._create_new_domain(xml)
> (nova.exception): TRACE:   File "/home/ctoteam/nova/nova/virt/libvirt/connection.py", line 1078, in _create_new_domain
> (nova.exception): TRACE:     domain = self._conn.defineXML(xml)
> (nova.exception): TRACE:   File "/usr/lib/python2.6/dist-packages/libvirt.py", line 1869, in defineXML
> (nova.exception): TRACE:     if ret is None:raise libvirtError('virDomainDefineXML() failed', conn=self)
> (nova.exception): TRACE: libvirtError: XML error: failed to parse domain description
> (nova.exception): TRACE: 
> 2011-08-16 16:12:24,273 ERROR nova.compute.manager [-] Instance '1' failed to spawn. Is virtualization enabled in the BIOS? Details: XML error: failed to parse domain description
> (nova.compute.manager): TRACE: Traceback (most recent call last):
> (nova.compute.manager): TRACE:   File "/home/ctoteam/nova/nova/compute/manager.py", line 329, in _run_instance
> (nova.compute.manager): TRACE:     self.driver.spawn(instance, network_info, bd_mapping)
> (nova.compute.manager): TRACE:   File "/home/ctoteam/nova/nova/exception.py", line 124, in wrapped
> (nova.compute.manager): TRACE:     raise Error(str(e))
> (nova.compute.manager): TRACE: Error: XML error: failed to parse domain description
> (nova.compute.manager): TRACE: 
> libvir: Xen error : Domain not found: xenUnifiedDomainLookupByName
> 
> Any idea about that one? Is this another setting for libvirt+xen usage that needs to be disabled?
> 
> ctoteam@buildingbuild:~$ dpkg -l | grep xen
> ii  libc6-xen                            2.13-10                          Embedded GNU C Library: Shared libraries [Xen version]
> ii  libxenstore3.0                       4.1.1-1                          Xenstore communications library for Xen
> ii  xen-hypervisor-4.1-i386              4.1.1-1                          Xen Hypervisor on i386
> ii  xen-linux-system-3.0.0-1-686-pae     3.0.0-1                          Xen system with Linux 3.0.0 on modern PCs (meta-package)
> ii  xen-linux-system-686-pae             3.0.0+39                         Xen system with Linux for modern PCs (meta-package)
> ii  xen-utils-4.1                        4.1.1-1                          XEN administrative tools
> ii  xen-utils-common                     4.1.0~rc6-1                      XEN administrative tools - common files
> ii  xenstore-utils                       4.1.1-1                          Xenstore utilities for Xen
> 
> ctoteam@buildingbuild:~$ dpkg -l | grep virt
> ii  libvirt-bin                          0.9.3-4                          programs for the libvirt library
> ii  libvirt0                             0.9.3-4                          library for interfacing with different virtualization systems
> ii  python-libvirt                       0.9.3-4                          libvirt Python bindings
> ii  qemu-kvm                             0.14.1+dfsg-4                    Full virtualization on x86 hardware
> 
> 
> 
> On 8/16/11 2:31 PM, "Joshua Harlow" <harlowja@xxxxxxxxxxxxx> wrote:
> 
> Thanks,
> 
> I’ll give it a try and see if the libvirt stuff works, or I’ll just switch to the native xen usage in openstack.
> 
> -Josh
> 
> On 8/16/11 11:44 AM, "Vishvananda Ishaya" <vishvananda@xxxxxxxxx> wrote:
> 
> NBD shouldn't be needed for xen.  You probably need to set
> --nouse_cow_images
> which will stop nova from trying to use qcow2 as the image format.
> 
> Vish
> 
> On Aug 16, 2011, at 11:06 AM, Joshua Harlow wrote:
> 
> ctoteam@buildingbuild:~$ sudo modprobe nbd
> ctoteam@buildingbuild:~$ 
> 
> Is there supposed to be devices there??
> 
> On 8/15/11 10:23 PM, "Yuriy Taraday" <yorik.sar@xxxxxxxxx <x-msg://460/yorik.sar@xxxxxxxxx> > wrote:
> 
> You probably should try to do "modprobe nbd" before running nova. This will create list of nbd devices that nova uses to inject keys and get images ready to start VM from them.
> 
> Kind regards, Yuriy.
> 
> 
> 
> On Tue, Aug 16, 2011 at 06:18, Joshua Harlow <harlowja@xxxxxxxxxxxxx <x-msg://460/harlowja@xxxxxxxxxxxxx> > wrote:
> Hi all,
> 
> Another error that others may have seen:
> Is it supposed to continue even if this fails?
> This is for running xen btw (this is running on nova-compute in a xen dom0 instance).
> 
> ting data into image 3 (Unexpected error while running command.
> Command: sudo qemu-nbd -c /dev/nbd14 /home/ctoteam/nova/nova/..//instances/instance-0000000a/disk
> Exit code: 1
> Stdout: ''
> Stderr: "qemu-nbd: Could not access '/dev/nbd14': No such file or directory\n")
> libvir: Xen Daemon error : XML error: failed to parse domain description
> 2011-08-15 19:16:29,374 ERROR nova.exception [-] Uncaught exception
> (nova.exception): TRACE: Traceback (most recent call last):
> (nova.exception): TRACE:   File "/home/ctoteam/nova/nova/exception.py", line 97, in wrapped
> (nova.exception): TRACE:     return f(*args, **kw)
> (nova.exception): TRACE:   File "/home/ctoteam/nova/nova/virt/libvirt/connection.py", line 603, in spawn
> (nova.exception): TRACE:     domain = self._create_new_domain(xml)
> (nova.exception): TRACE:   File "/home/ctoteam/nova/nova/virt/libvirt/connection.py", line 1078, in _create_new_domain
> (nova.exception): TRACE:     domain = self._conn.defineXML(xml)
> (nova.exception): TRACE:   File "/usr/lib/python2.6/dist-packages/libvirt.py", line 1869, in defineXML
> (nova.exception): TRACE:     if ret is None:raise libvirtError('virDomainDefineXML() failed', conn=self)
> (nova.exception): TRACE: libvirtError: XML error: failed to parse domain description
> (nova.exception): TRACE: 
> 2011-08-15 19:16:29,375 ERROR nova.compute.manager [-] Instance '10' failed to spawn. Is virtualization enabled in the BIOS? Details: XML error: failed to parse domain description
> (nova.compute.manager): TRACE: Traceback (most recent call last):
> (nova.compute.manager): TRACE:   File "/home/ctoteam/nova/nova/compute/manager.py", line 329, in _run_instance
> (nova.compute.manager): TRACE:     self.driver.spawn(instance, network_info, bd_mapping)
> (nova.compute.manager): TRACE:   File "/home/ctoteam/nova/nova/exception.py", line 124, in wrapped
> (nova.compute.manager): TRACE:     raise Error(str(e))
> (nova.compute.manager): TRACE: Error: XML error: failed to parse domain description
> (nova.compute.manager): TRACE: 
> libvir: Xen error : Domain not found: xenUnifiedDomainLookupByName
> 2011-08-15 19:16:51,893 INFO nova.compute.manager [-] Found instance 'instance-00000005' in DB but no VM. State=5 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx <x-msg://460/openstack@xxxxxxxxxxxxxxxxxxx> 
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
> 
> 
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
> 
> 
>