Hide Forgot
Description of problem: The Power build of qemu, like the x86 build, includes the EHCI USB controller. The EHCI is not terribly well tested on Power - neither the qemu emulation nor the guest side driver. We've hit some problems with EHCI in the past which have gone away with XHCI. In particular EHCI's expectation of a companion controller for USB1 devices adds a bunch of extra confusion and complication. There's really no reason to ever use an EHCI instead of an XHCI on Power guests, so to reduce dev and test workload, remove the EHCI controller from qemu-kvm-rhev.
Fix included in qemu-kvm-rhev-2.8.0-2.el7
List usb controller in qemu-kvm-rhev-2.6.0-28.el7_3.9.ppc64le /usr/libexec/qemu-kvm -device help USB devices: name "ich9-usb-ehci1", bus PCI name "ich9-usb-ehci2", bus PCI name "nec-usb-xhci", bus PCI name "pci-ohci", bus PCI, desc "Apple USB Controller" name "sysbus-ohci", bus System, desc "OHCI USB Controller" name "usb-ehci", bus PCI List usb controller in qemu-kvm-rhev-2.9.0-1.el7.ppc64le USB devices: name "nec-usb-xhci", bus PCI name "pci-ohci", bus PCI, desc "Apple USB Controller" name "qemu-xhci", bus PCI name "sysbus-ohci", bus System, desc "OHCI USB Controller" Try to run qemu cmdline with ehci controller with qemu-kvm-rhev-2.9.0-1.el7.ppc64le [root@ibm-p8-kvm-02-qe xuma]# /usr/libexec/qemu-kvm -device ich9-usb-ehci1 qemu-kvm: -device ich9-usb-ehci1: 'ich9-usb-ehci1' is not a valid device model name [root@ibm-p8-kvm-02-qe xuma]# /usr/libexec/qemu-kvm -device ich9-usb-ehci2 qemu-kvm: -device ich9-usb-ehci2: 'ich9-usb-ehci2' is not a valid device model name [root@ibm-p8-kvm-02-qe xuma]# /usr/libexec/qemu-kvm -device usb-ehci qemu-kvm: -device usb-ehci: 'usb-ehci' is not a valid device model name Base results above ,the ehci controllers have been remove from qemu-2.9.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2017:2392