Public bug reported:
I'm developing the installation guide for Icehouse. In this particular
case, I'm installing and testing RC1 on Ubuntu 12.04 with nova
networking. All nodes in this environment run as VMs and the nova-
compute service uses QEMU due to hardware limitations with nested VMs.
Attempting to launch an instance generates the following error (full
traceback attached):
2014-04-07 17:50:52.235 1220 TRACE nova.compute.manager [instance:
4574ce1a-e81f-4bfc-a079-b45c2a1f31ae] libvirtError: internal error: process
exited while connecting to monitor: qemu-system-x86_64: -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:50:c4:59,bus=pci.0,addr=0x1:
PCI: slot 1 function 0 not available for virtio-net-pci, in use by PIIX3
2014-04-07 17:50:52.235 1220 TRACE nova.compute.manager [instance:
4574ce1a-e81f-4bfc-a079-b45c2a1f31ae] qemu-system-x86_64: -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:50:c4:59,bus=pci.0,addr=0x1:
Device initialization failed.
2014-04-07 17:50:52.235 1220 TRACE nova.compute.manager [instance:
4574ce1a-e81f-4bfc-a079-b45c2a1f31ae] qemu-system-x86_64: -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:50:c4:59,bus=pci.0,addr=0x1:
Device 'virtio-net-pci' could not be initialized
Package version information:
nova-compute: :2014.1~rc1-0ubuntu1~cloud0
nova-network: :2014.1~rc1-0ubuntu1~cloud0
libvirt-bin: 1.2.2-0ubuntu7~cloud0
Command output:
$ nova service-list
+------------------+------------+----------+---------+-------+----------------------------+-----------------+
| Binary | Host | Zone | Status | State | Updated_at
| Disabled Reason |
+------------------+------------+----------+---------+-------+----------------------------+-----------------+
| nova-cert | hst-osctl5 | internal | enabled | up |
2014-04-08T00:33:15.000000 | - |
| nova-consoleauth | hst-osctl5 | internal | enabled | up |
2014-04-08T00:33:19.000000 | - |
| nova-scheduler | hst-osctl5 | internal | enabled | up |
2014-04-08T00:33:13.000000 | - |
| nova-conductor | hst-osctl5 | internal | enabled | up |
2014-04-08T00:33:16.000000 | - |
| nova-compute | hst-oscpu5 | nova | enabled | up |
2014-04-08T00:33:15.000000 | - |
| nova-network | hst-oscpu5 | internal | enabled | up |
2014-04-08T00:33:13.000000 | - |
+------------------+------------+----------+---------+-------+----------------------------+-----------------+
$ nova net-list
+--------------------------------------+----------+------------------+
| ID | Label | CIDR |
+--------------------------------------+----------+------------------+
| 7f849be3-4494-495a-95a1-0f99ccb884c4 | demo-net | 172.24.246.24/29 |
+--------------------------------------+----------+------------------+
** Affects: nova
Importance: Undecided
Status: New
** Tags: icehouse-backport-potential
** Attachment added: "nova-compute.txt"
https://bugs.launchpad.net/bugs/1304107/+attachment/4073375/+files/nova-compute.txt
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1304107
Title:
Libvirt error launching instance - Device 'virtio-net-pci' could not
be initialized
Status in OpenStack Compute (Nova):
New
Bug description:
I'm developing the installation guide for Icehouse. In this particular
case, I'm installing and testing RC1 on Ubuntu 12.04 with nova
networking. All nodes in this environment run as VMs and the nova-
compute service uses QEMU due to hardware limitations with nested VMs.
Attempting to launch an instance generates the following error (full
traceback attached):
2014-04-07 17:50:52.235 1220 TRACE nova.compute.manager [instance:
4574ce1a-e81f-4bfc-a079-b45c2a1f31ae] libvirtError: internal error: process
exited while connecting to monitor: qemu-system-x86_64: -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:50:c4:59,bus=pci.0,addr=0x1:
PCI: slot 1 function 0 not available for virtio-net-pci, in use by PIIX3
2014-04-07 17:50:52.235 1220 TRACE nova.compute.manager [instance:
4574ce1a-e81f-4bfc-a079-b45c2a1f31ae] qemu-system-x86_64: -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:50:c4:59,bus=pci.0,addr=0x1:
Device initialization failed.
2014-04-07 17:50:52.235 1220 TRACE nova.compute.manager [instance:
4574ce1a-e81f-4bfc-a079-b45c2a1f31ae] qemu-system-x86_64: -device
virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:50:c4:59,bus=pci.0,addr=0x1:
Device 'virtio-net-pci' could not be initialized
Package version information:
nova-compute: :2014.1~rc1-0ubuntu1~cloud0
nova-network: :2014.1~rc1-0ubuntu1~cloud0
libvirt-bin: 1.2.2-0ubuntu7~cloud0
Command output:
$ nova service-list
+------------------+------------+----------+---------+-------+----------------------------+-----------------+
| Binary | Host | Zone | Status | State | Updated_at
| Disabled Reason |
+------------------+------------+----------+---------+-------+----------------------------+-----------------+
| nova-cert | hst-osctl5 | internal | enabled | up |
2014-04-08T00:33:15.000000 | - |
| nova-consoleauth | hst-osctl5 | internal | enabled | up |
2014-04-08T00:33:19.000000 | - |
| nova-scheduler | hst-osctl5 | internal | enabled | up |
2014-04-08T00:33:13.000000 | - |
| nova-conductor | hst-osctl5 | internal | enabled | up |
2014-04-08T00:33:16.000000 | - |
| nova-compute | hst-oscpu5 | nova | enabled | up |
2014-04-08T00:33:15.000000 | - |
| nova-network | hst-oscpu5 | internal | enabled | up |
2014-04-08T00:33:13.000000 | - |
+------------------+------------+----------+---------+-------+----------------------------+-----------------+
$ nova net-list
+--------------------------------------+----------+------------------+
| ID | Label | CIDR |
+--------------------------------------+----------+------------------+
| 7f849be3-4494-495a-95a1-0f99ccb884c4 | demo-net | 172.24.246.24/29 |
+--------------------------------------+----------+------------------+
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1304107/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
