** Description changed:
[impact]
qemu's various architecture-specific emulators expect the pci bus to be
referred to either as 'pci' or 'pci.0', and libvirt must know which to
use. On trusty, the latest qemu-system-ppc (and ppc64) emulators
require 'pci.0' when using the 'pseries' machine type, but the libvirt
uses 'pci'.
The result is no ppc/ppc64 virsh instance can be started; they will fail with:
$ virsh start ppc64_test
error: Failed to start domain ppc64_test
error: internal error: process exited while connecting to monitor: Warning:
Disabling some instructions which are not emulated by TCG (0x0, 0x4)
qemu-system-ppc64: -device VGA,id=video0,bus=pci,addr=0x3: Bus 'pci' not found
the upstream patch to fix this is commit
27b2b987bf41ba1ba3aab8c8d9b2d8bc740fd925 ('Fix pci bus naming for PPC')
[test case]
on a trusty system, install:
uvtool
qemu (which pulls in the qemu-system-ppc package)
qemu-slof
openbios-ppc
- after installing uvtool/libvirt, you're added to the libvirtd group, so
- you need to log out/in for that to take effect; use 'id' to make sure
- you're in that group.
+ follow the uvt-kvm man page instructions for getting a base image with
+ uvt-simplestreams-libvirt, and creating a new libvirt instance. Note
+ you can use a x86 base image, just to get the libvirt xml created; e.g.
- then get a base image for ppc64:
+ $ uvt-simplestreams-libvirt sync
+ $ uvt-kvm create ppc64_test
- $ uvt-simplestreams-libvirt -v sync release=trusty arch=ppc64el
-
- that takes a while but should not print any error. then create a new
- instance:
-
- $ uvt-kvm create ppc64_test arch=ppc64el
-
- that will create a virsh instance, but with the wrong xml; so:
+ that will create a virsh instance, but for x86; so:
$ virsh destroy ppc64_test
$ virsh edit ppc64_test
change the xml like this, to make the instance actually ppc64:
@@ -1,11 +1,11 @@
-<domain type='kvm'>
+<domain type='qemu'>
<name>ppc64_test</name>
<uuid>f3d6cc82-01b7-4f0d-b910-1f2f11c504f4</uuid>
<memory unit='KiB'>524288</memory>
<currentMemory unit='KiB'>524288</currentMemory>
<vcpu placement='static'>1</vcpu>
<os>
- <type arch='x86_64' machine='pc-i440fx-trusty'>hvm</type>
+ <type arch='ppc64' machine='pseries'>hvm</type>
<boot dev='hd'/>
</os>
<features>
@@ -18,7 +18,7 @@
<on_reboot>restart</on_reboot>
<on_crash>destroy</on_crash>
<devices>
- <emulator>/usr/bin/kvm-spice</emulator>
+ <emulator>/usr/bin/qemu-system-ppc64</emulator>
<disk type='file' device='disk'>
<driver name='qemu' type='qcow2'/>
<source file='/var/lib/uvtool/libvirt/images/ppc64_test.qcow'/>
save it, and try to start it.
now try to start it:
$ virsh start ppc64_test
it will fail with the reported error.
[regression potential]
since the patch to fix this changes when libvirt uses the 'pci' name or
the 'pci.0' name, this may break existing virsh instances if the logic
is not correct to map the pci naming to the current qemu arch and
version. However this only changes behavior for qemu-system-ppc and
-ppc64; no regression is possible for qemu-system-x86_64 or -i386 or any
other qemu-system-* besides -ppc and -ppc64.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1571075
Title:
ppc emulated pseries expecting 'pci.0' bus fails to start
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1571075/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
