Re: [Openstack] QEMU Error
Thanks Aaron, i have only qemu-kvm not kvm. The issue was the image type is
qcow2. When I changed it to the following I got pass that issue.
qemu-image create -f qcow2 $IMAGE 5 G
Howerve, I am not getting ISOLINUX 4.02 2010-07-21 ETCD Copyright (C) 1994-2010
H. Peter Anvin et alÿ.
I have tried to boot with the same ISO on a different VM and it worked fined.
Not sure why. any ideas.
AK
Date: Mon, 22 Oct 2012 11:09:19 -0700
Subject: Re: [Openstack] QEMU Error
From: aro...@nicira.com
To: ak_m...@hotmail.com
CC: openstack@lists.launchpad.net
The following should do the trick for you in order to create a new
disk and boot an iso using it :
IMAGE=centos-6.2.img
qemu-img create -f raw $IMAGE 5G
sudo kvm -hda $IMAGE -m 512 -smp 2 -cdrom centos_installer.iso -boot c
Aaron
On Mon, Oct 22, 2012 at 8:36 AM, AK Sathiya ak_m...@hotmail.com wrote:
All, i am a newbi to the openstack. I am trying to create a QCOW2 image from
a Centos Linux installation iso and ran into the a road block. This is what
I did so far (just followed the admin manual for Openstack).
IMAGE=centos-6.2.img
$ qemu-img create -f raw $IMAGE 5G
VNCDISPLAY=:2
$ MONITOR=/tmp/file.mon
$ sudo /usr/libexec/qemu-kvm -m 1024 -drive file=${IMAGE},if=virtio,index=0
\
-boot c -net nic -net user -nographic -vnc ${VNCDISPLAY} \
-monitor unix:${MONITOR},server,nowait
I have the distribution iso on the local directory of the user.
I got the following error. what am i missing here?
qemu-kvm: -drive file=centos-6.2.img,if=virtio,index=0: could not open disk
image centos-6.2.img:Operation not supported
Any help is appreciated.
AK
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] QEMU Error
Can you show the qemu-kvm command you are running?
On Tue, Oct 23, 2012 at 8:48 AM, AK Sathiya ak_m...@hotmail.com wrote:
Thanks Aaron, i have only qemu-kvm not kvm. The issue was the image type is
qcow2. When I changed it to the following I got pass that issue.
qemu-image create -f qcow2 $IMAGE 5 G
Howerve, I am not getting ISOLINUX 4.02 2010-07-21 ETCD Copyright (C)
1994-2010 H. Peter Anvin et alÿ.
I have tried to boot with the same ISO on a different VM and it worked
fined.
Not sure why. any ideas.
AK
Date: Mon, 22 Oct 2012 11:09:19 -0700
Subject: Re: [Openstack] QEMU Error
From: aro...@nicira.com
To: ak_m...@hotmail.com
CC: openstack@lists.launchpad.net
The following should do the trick for you in order to create a new
disk and boot an iso using it :
IMAGE=centos-6.2.img
qemu-img create -f raw $IMAGE 5G
sudo kvm -hda $IMAGE -m 512 -smp 2 -cdrom centos_installer.iso -boot c
Aaron
On Mon, Oct 22, 2012 at 8:36 AM, AK Sathiya ak_m...@hotmail.com wrote:
All, i am a newbi to the openstack. I am trying to create a QCOW2 image
from
a Centos Linux installation iso and ran into the a road block. This is
what
I did so far (just followed the admin manual for Openstack).
IMAGE=centos-6.2.img
$ qemu-img create -f raw $IMAGE 5G
VNCDISPLAY=:2
$ MONITOR=/tmp/file.mon
$ sudo /usr/libexec/qemu-kvm -m 1024 -drive
file=${IMAGE},if=virtio,index=0
\
-boot c -net nic -net user -nographic -vnc ${VNCDISPLAY} \
-monitor unix:${MONITOR},server,nowait
I have the distribution iso on the local directory of the user.
I got the following error. what am i missing here?
qemu-kvm: -drive file=centos-6.2.img,if=virtio,index=0: could not open
disk
image centos-6.2.img:Operation not supported
Any help is appreciated.
AK
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
[Openstack] QEMU Error
All, i am a newbi to the openstack. I am trying to create a QCOW2 image from a
Centos Linux installation iso and ran into the a road block. This is what I did
so far (just followed the admin manual for Openstack).
IMAGE=centos-6.2.img
$ qemu-img create -f raw $IMAGE 5G
VNCDISPLAY=:2
$ MONITOR=/tmp/file.mon
$ sudo /usr/libexec/qemu-kvm -m 1024 -drive file=${IMAGE},if=virtio,index=0 \
-boot c -net nic -net user -nographic -vnc ${VNCDISPLAY} \
-monitor unix:${MONITOR},server,nowait
I have the distribution iso on the local directory of the user.
I got the following error. what am i missing here?
qemu-kvm: -drive file=centos-6.2.img,if=virtio,index=0: could not open disk
image centos-6.2.img:Operation not supported
Any help is appreciated.
AK
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] QEMU Error
The following should do the trick for you in order to create a new
disk and boot an iso using it :
IMAGE=centos-6.2.img
qemu-img create -f raw $IMAGE 5G
sudo kvm -hda $IMAGE -m 512 -smp 2 -cdrom centos_installer.iso -boot c
Aaron
On Mon, Oct 22, 2012 at 8:36 AM, AK Sathiya ak_m...@hotmail.com wrote:
All, i am a newbi to the openstack. I am trying to create a QCOW2 image from
a Centos Linux installation iso and ran into the a road block. This is what
I did so far (just followed the admin manual for Openstack).
IMAGE=centos-6.2.img
$ qemu-img create -f raw $IMAGE 5G
VNCDISPLAY=:2
$ MONITOR=/tmp/file.mon
$ sudo /usr/libexec/qemu-kvm -m 1024 -drive file=${IMAGE},if=virtio,index=0
\
-boot c -net nic -net user -nographic -vnc ${VNCDISPLAY} \
-monitor unix:${MONITOR},server,nowait
I have the distribution iso on the local directory of the user.
I got the following error. what am i missing here?
qemu-kvm: -drive file=centos-6.2.img,if=virtio,index=0: could not open disk
image centos-6.2.img:Operation not supported
Any help is appreciated.
AK
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Qemu error?
This looks like a bug. It appears that you are using xen through libvirt which
hasn't had a whole lot of testing.
Vish
On Aug 15, 2011, at 7:18 PM, Joshua Harlow 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-000a/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-0005' in DB but no VM. State=5
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Qemu error?
ctoteam@buildingbuild:~$ sudo modprobe nbd
ctoteam@buildingbuild:~$
Is there supposed to be devices there??
On 8/15/11 10:23 PM, Yuriy Taraday yorik@gmail.com 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 harlo...@yahoo-inc.com 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-000a/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-0005' in DB but no VM. State=5
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Qemu error?
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@gmail.com 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 harlo...@yahoo-inc.com 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-000a/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-0005' in DB but no VM. State=5
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Qemu error?
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 vishvana...@gmail.com 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@gmail.com
x-msg://460/yorik@gmail.com 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 harlo...@yahoo-inc.com
x-msg://460/harlo...@yahoo-inc.com 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-000a/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-0005' in DB but no VM. State=5
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
x-msg://460/openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
Re: [Openstack] Qemu error?
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-0001: 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-xen2.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.14.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-4Full
virtualization on x86 hardware
On 8/16/11 2:31 PM, Joshua Harlow harlo...@yahoo-inc.com 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 vishvana...@gmail.com 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@gmail.com
x-msg://460/yorik@gmail.com 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 harlo...@yahoo-inc.com
x-msg://460/harlo...@yahoo-inc.com wrote:
Hi all,
Another error that others may have
Re: [Openstack] Qemu error?
You've extended beyond my experience. Never tried open source xen. Perhaps
soren has some insight here.
Vish
On Aug 16, 2011, at 5:06 PM, Joshua Harlow wrote:
Ah, ok.
So updated that.
Now I get the following:
2011-08-16 16:58:33,973 DEBUG nova.utils [-] Running cmd (subprocess): sudo
losetup --detach /dev/loop0 from (pid=6440) execute
/home/ctoteam/nova/nova/utils.py:143
libvir: Xen Daemon error : POST operation failed: xend_post: error from xen
daemon: (xend.err (22, 'Invalid argument'))
2011-08-16 16:58:35,455 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 1080, in
_create_new_domain
(nova.exception): TRACE: domain.createWithFlags(launch_flags)
(nova.exception): TRACE: File
/usr/lib/python2.6/dist-packages/libvirt.py, line 475, in createWithFlags
(nova.exception): TRACE: if ret == -1: raise libvirtError
('virDomainCreateWithFlags() failed', dom=self)
(nova.exception): TRACE: libvirtError: POST operation failed: xend_post:
error from xen daemon: (xend.err (22, 'Invalid argument'))
(nova.exception): TRACE:
2011-08-16 16:58:35,459 ERROR nova.compute.manager [-] Instance '4' failed to
spawn. Is virtualization enabled in the BIOS? Details: POST operation failed:
xend_post: error from xen daemon: (xend.err (22, 'Invalid argument'))
(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: POST operation failed: xend_post: error
from xen daemon: (xend.err (22, 'Invalid argument'))
(nova.compute.manager): TRACE:
Have u seen that?
Although after this I seem to have a instance in “xm list” even though this
errored?
On 8/16/11 4:52 PM, Vishvananda Ishaya vishvana...@gmail.com wrote:
No that is a response from glance, but it looks like it is passing a badly
formed url of some sort so glance is passing back a list of api versions
instead of an image. Perhaps you have a mismatch between the version of
glance client on compute
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
[Openstack] Qemu error?
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-000a/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-0005' in DB but no VM. State=5
___
Mailing list: https://launchpad.net/~openstack
Post to : openstack@lists.launchpad.net
Unsubscribe : https://launchpad.net/~openstack
More help : https://help.launchpad.net/ListHelp
