virt-manager / libvirt fails to create VM due to PCI ordering bug
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
libvirt |
Fix Released
|
Undecided
|
|||
libvirt (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Hi there;
libvirt in trusty has a bug where VM's fail to get defined due to PCI bus ordering bugs.
Redhat bug tracker info here: https:/
Appears to be the same bug.
Steps to reproduce:
* Open Virt-manager
* Define a new VM
( I used reactos installer iso)
* Attempt to run.
Get something like this:
"
Unable to complete install: 'internal error: process exited while connecting to monitor: qemu-system-x86_64: -device rtl8139,
qemu-system-x86_64: -device rtl8139,
qemu-system-x86_64: -device rtl8139,
'
Traceback (most recent call last):
File "/usr/share/
callback(
File "/usr/share/
guest.
File "/usr/lib/
noboot)
File "/usr/lib/
dom = self.conn.
File "/usr/lib/
if ret is None:raise libvirtError(
libvirtError: internal error: process exited while connecting to monitor: qemu-system-x86_64: -device rtl8139,
qemu-system-x86_64: -device rtl8139,
qemu-system-x86_64: -device rtl8139,
"
Attempted resolutions:
Removing Devices/reordering them via virt-manager still fails to solve the issue ( you manually need to hack at the .xml definition).
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libvirt-bin 1.2.2-0ubuntu12
ProcVersionSign
Uname: Linux 3.13.0-23-generic x86_64
ApportVersion: 2.14.1-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Apr 12 17:11:24 2014
InstallationDate: Installed on 2014-03-31 (11 days ago)
InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Daily amd64 (20140330)
SourcePackage: libvirt
UpgradeStatus: No upgrade log present (probably fresh install)
modified.
Changed in libvirt: | |
importance: | Unknown → Undecided |
status: | Unknown → Fix Released |
Description of problem:
Looks like libvirt is sensitive to the order in which the video devices are passed.
Passing them in a wrong order causes the error below.
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
Tried with two VMs, one in which the order was:
<video>
<address domain="0x0000" function="0x0" slot="0x07" type="pci" bus="0x00"/>
<model heads="1" type="qxl" vram="65536"/>
</video>
<video>
<address domain="0x0000" function="0x0" slot="0x02" type="pci" bus="0x00"/>
<model heads="1" type="qxl" vram="65536"/>
</video>
Failed on (from libvirt.log): gramDispatchErr or:174 : internal error Primary video card must have PCI address 0:0:2.0
error : virNetClientPro
In the other VM the order was:
<video>
<address domain="0x0000" function="0x0" slot="0x02" type="pci" bus="0x00"/>
<model heads="1" type="qxl" vram="65536"/>
</video>
<video>
<address domain="0x0000" function="0x0" slot="0x07" type="pci" bus="0x00"/>
<model heads="1" type="qxl" vram="65536"/>
</video>
And it succeeded.
Actual results: gramDispatchErr or:174 : internal error Primary video card must have PCI address 0:0:2.0
The VM in which the order is wrong fails with error:
error : virNetClientPro
Expected results:
Both VMs should start correctly.