Created attachment 708405 [details] build log Description of problem: several of the self checks fail on PPC with this error: libguestfs: [159547ms] launch libvirt guest *stdin*:2: libguestfs: error: could not create appliance through libvirt: internal error process exited while connecting to monitor: qemu-system-ppc: -device piix3-usb-uhci,id=usb,bus=pci,addr=0x1.0x2: PCI: single function device can't be populated in function 1.2 qemu-system-ppc: -device piix3-usb-uhci,id=usb,bus=pci,addr=0x1.0x2: Device 'piix3-usb-uhci' could not be initialized [code=1 domain=10] libguestfs: trace: launch = -1 (error) Version-Release number of selected component (if applicable): libguestfs-1.21.18-1.fc19 How reproducible: always Steps to Reproduce: 1. ppc-koji build --scratch f19 libguestfs-1.21.18-1.fc19.src.rpm 2. 3. Actual results: http://ppc.koji.fedoraproject.org/koji/taskinfo?taskID=981494 Expected results: Additional info:
It's not hugely surprising since libvirt doesn't properly support ppc. Note that it's libvirt which is adding this PIIX (ie. PC-only) device.
I already have work assigned to me that will change libvirt to only auto-add macthinetype-appropriate default devices (this is also needed in order to properly support the new pc-q35 machinetype).
This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19
There's been upstream work over the past year to tease out these types of issues on some non-x86 architectures, but they aren't likely to be backported, only rebased in with new fedora versions. In the meantime I believe libguestfs disabled the failing tests or similar, so the initial report is no longer an issue.