[Bug 1571075] Re: ppc emulated pseries expecting 'pci.0' bus fails to start
> should we close this bug? probably, yeah. > Can you explain under which cases this bug is needed? Does it depend on the specific ppc64 hardware? i suspect this is a problem on trusty, when using ppc hardware or x86 hardware (meaning, setting up a ppc guest with virsh on either x86 or ppc host hw). But I don't have access to ppc hw so I can't verify there. > Since this patch is upstream and in the xenial tree, I *suspect* your concern > about this patch breaking certain existing cases > shouldn't apply, but I could be wrong. oh i agree, it shouldn't break anything, i was just listing the theoretical regressions. :-) > Certainly such a concern along with a low priority means this probably does > not qualify for > an SRU. well if anyone wanted to use qemu-system-ppc with libvirt on trusty, this would be needed, but I suspect nobody does; and my interest was emulating ppc on an x86 box, which appears to have other problems on trusty, so we'll just move to xenial. ** Changed in: libvirt (Ubuntu Trusty) Status: New => Won't Fix -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571075] Re: ppc emulated pseries expecting 'pci.0' bus fails to start
** Changed in: libvirt (Ubuntu Trusty) Importance: Undecided => Low -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571075] Re: ppc emulated pseries expecting 'pci.0' bus fails to start
Hi, should we close this bug? Can you explain under which cases this bug is needed? Does it depend on the specific ppc64 hardware? Since this patch is upstream and in the xenial tree, I *suspect* your concern about this patch breaking certain existing cases shouldn't apply, but I could be wrong. Certainly such a concern along with a low priority means this probably does not qualify for an SRU. Thanks for digging into this bug! -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571075] Re: ppc emulated pseries expecting 'pci.0' bus fails to start
** Also affects: libvirt (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: libvirt (Ubuntu) Status: In Progress => Fix Released -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571075] Re: ppc emulated pseries expecting 'pci.0' bus fails to start
there appear to be other problems with qemu-system-ppc64, as the ubuntu powerpc iso fails immediately after the boot menu, so this bug probably doesn't really matter. ** Changed in: libvirt (Ubuntu) Importance: Medium => Low -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571075] Re: ppc emulated pseries expecting 'pci.0' bus fails to start
The attachment "lp1571075.debdiff" seems to be a debdiff. The ubuntu- sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571075] Re: ppc emulated pseries expecting 'pci.0' bus fails to start
** 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 @@
-
+
ppc64_test
f3d6cc82-01b7-4f0d-b910-1f2f11c504f4
524288
524288
1
-hvm
+hvm
@@ -18,7 +18,7 @@
restart
destroy
-/usr/bin/kvm-spice
+/usr/bin/qemu-system-ppc64
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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571075] Re: ppc emulated pseries expecting 'pci.0' bus fails to start
** 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]
ppc64_test
524288
524288
1
hvm
destroy
restart
destroy
/usr/bin/qemu-system-ppc64
- on a trusty system, use the above example libvirt xml to define a
- domain. make sure qemu-system-ppc64 is installed along with its
- dependencies, and then virsh start ppc64_test; it will fail with the
- above error.
+ 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.
+
+ then get a base image for ppc64:
+
+ $ 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:
+
+ $ virsh destroy ppc64_test
+ $ virsh edit ppc64_test
+
+ change the xml like this, to make the instance actually ppc64:
+ @@ -1,11 +1,11 @@
+ -
+ +
+ppc64_test
+f3d6cc82-01b7-4f0d-b910-1f2f11c504f4
+524288
+524288
+1
+
+ -hvm
+ +hvm
+
+
+
+ @@ -18,7 +18,7 @@
+restart
+destroy
+
+ -/usr/bin/kvm-spice
+ +/usr/bin/qemu-system-ppc64
+
+
+
+
+ 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.
** 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]
-
-
- ppc64_test
- 524288
- 524288
- 1
-
- hvm
-
-
-
- destroy
- restart
- destroy
-
- /usr/bin/qemu-system-ppc64
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
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.
then get a base image for ppc64:
$ uvt-simplestreams-libvirt -v sync release=trusty
[Bug 1571075] Re: ppc emulated pseries expecting 'pci.0' bus fails to start
** 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')
+ the upstream patch to fix this is commit
+ 27b2b987bf41ba1ba3aab8c8d9b2d8bc740fd925 ('Fix pci bus naming for PPC')
[test case]
- ppc64_test
- 524288
- 524288
- 1
-
- hvm
-
-
-
- destroy
- restart
- destroy
-
- /usr/bin/qemu-system-ppc64
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+ ppc64_test
+ 524288
+ 524288
+ 1
+
+ hvm
+
+
+
+ destroy
+ restart
+ destroy
+
+ /usr/bin/qemu-system-ppc64
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
- on a trusty system, use the above example libvirt xml to define a domain.
make sure qemu-system-ppc64 is installed along with its dependencies, and then
virsh start ppc64_test; it will fail with the above error.
-
+ on a trusty system, use the above example libvirt xml to define a
+ domain. make sure qemu-system-ppc64 is installed along with its
+ dependencies, and then virsh start ppc64_test; it will fail with the
+ above 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
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571075] Re: ppc emulated pseries expecting 'pci.0' bus fails to start
To check any qemu-system-* emulator's expected pci bus naming: $ qemu-system-ppc64 -nographic -nodefconfig -nodefaults -machine pseries -monitor stdio QEMU 2.0.0 monitor - type 'help' for more information (qemu) Warning: Disabling some instructions which are not emulated by TCG (0x0, 0x4) then use the command 'info qtree' which will print something similar to: bus: main-system-bus type System dev: spapr-pci-host-bridge, id "" index = 0 (0) buid = 576460752840294400 (0x8002000) liobn = 2147483648 (0x8000) mem_win_addr = 1102195982336 (0x100a000) mem_win_size = 536870912 (0x2000) io_win_addr = 1101659111424 (0x1008000) io_win_size = 65536 (0x1) irq 0 bus: pci.0 type PCI note the 'bus: pci.0' in the above output. That will work for any qemu-system-* arch emulator. To find what -machine types a specific arch emulator includes, try: $ qemu-system-ppc64 -machine ? Supported machines are: taihutaihu mac99Mac99 based PowerMAC pseries pSeries Logical Partition (PAPR compliant) (default) prep PowerPC PREP platform g3beige Heathrow based PowerMAC bamboo bamboo mpc8544dsmpc8544ds ppce500 generic paravirt e500 platform virtex-ml507 Xilinx Virtex ML507 reference design none empty machine ref405ep ref405ep -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1571075] Re: ppc emulated pseries expecting 'pci.0' bus fails to start
** Patch added: "lp1571075.debdiff" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1571075/+attachment/4637910/+files/lp1571075.debdiff -- 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 ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
