RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

QEMU upstream has gained USB 2.0 (EHCI) support. The way this is implemented in QEMU will require some additional work in libvirt to enable its use.

Specifically the ECHI device will need to be explicitly added to the guest, and USB devices attached to the guest will need to be explicitly connected to that device, rather than the default USB 1.0 device.

This will require

 - Additional <controller> type in guest XML to represent the USB controllers used for initial startup
 - The same for hotplug/unplug of the USB 2.0 device controller
 - Additional <address type='usb'/> to specify the USB controller, and the USB socket to connect to, for any USB devices

We likely also want to consider whether the node device XML actually contains enough info to determine if a host device needs USB 2.0 support or not, so apps can validate it before trying to connect the device to the guest.

See also

http://www.redhat.com/archives/libvir-list/2011-June/msg00296.html
http://www.kraxel.org/cgit/qemu/tree/docs/usb2.txt?h=usb.15

https://www.redhat.com/archives/libvir-list/2011-September/msg00104.html

Patches from Marc-Andre Lureau are in upstream.

According to Comment 10 & 11, move it to VERIFIED.

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.

http://rhn.redhat.com/errata/RHSA-2012-0748.html