Bug 1410674 – qemu: Remove unnecessary EHCI implementation for Power

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1410674 - qemu: Remove unnecessary EHCI implementation for Power

Summary:	qemu: Remove unnecessary EHCI implementation for Power

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	qemu-kvm-rhev (Show other bugs)
Sub Component:
Version:	7.4
Hardware:	ppc64le Unspecified

Priority	unspecified Severity medium
Target Milestone:	rc
Target Release:	---
Assigned To:	David Gibson
QA Contact:	Xujun Ma
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	1386113 1436054
	Show dependency tree / graph

Reported:	2017-01-05 23:29 EST by David Gibson
Modified:	2017-08-01 23:17 EDT (History)
CC List:	7 users (show)

See Also:	1439147
Fixed In Version:	qemu-kvm-rhev-2.8.0-2.el7
Doc Type:	If docs needed, set a value
Doc Text:
Story Points:	---
Clone Of:
Clones:	1436054 (view as bug list)
Environment:
Last Closed:	2017-08-01 19:42:15 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHSA-2017:2392	normal	SHIPPED_LIVE	Important: qemu-kvm-rhev security, bug fix, and enhancement update	2017-08-01 16:04:36 EDT

Groups: None (edit)

Description David Gibson 2017-01-05 23:29:44 EST

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.

Comment 1 Miroslav Rezanina 2017-01-16 07:16:43 EST

Fix included in qemu-kvm-rhev-2.8.0-2.el7

Comment 3 Xujun Ma 2017-04-24 06:26:09 EDT

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.

Comment 5 errata-xmlrpc 2017-08-01 19:42:15 EDT

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

Comment 6 errata-xmlrpc 2017-08-01 21:19:54 EDT

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

Comment 7 errata-xmlrpc 2017-08-01 22:11:53 EDT

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

Comment 8 errata-xmlrpc 2017-08-01 22:52:40 EDT

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

Comment 9 errata-xmlrpc 2017-08-01 23:17:22 EDT

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

Note You need to log in before you can comment on or make changes to this bug.