Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Created attachment 1581259[details]
html format log
Description of problem:
Version-Release number of selected component (if applicable):
kernel-4.18.0-80.4.1.el8_0.x86_64.rpm
qemu-kvm-3.1.0-27.module+el8.0.1+3253+c5371cb3.x86_64
seabios-1.12.0-1.module+el8.0.1+2959+fecd1a40.x86_64
virtio-win-1.9.8-2.el8.iso -viostor
virtio-win-prewhql-0.1-172.iso -netkvm
How reproducible:
100%
Steps to Reproduce:
1.boot guest with the following usb device(usb3.0),one usb controller,one usb hub and two usb storage.
-device nec-usb-xhci,id=controller -device usb-hub,id=usbhub,bus=controller.0,port=1 \
-drive file=usb-disk-1.raw,if=none,id=drive-usb-1-0,media=disk,format=raw,cache=none,werror=stop,rerror=stop,aio=threads -device usb-storage,port=1.1,drive=drive-usb-1-0,id=usb-1-0,removable=on \
-drive file=usb-disk-2.raw,if=none,id=drive-usb-2-0,media=disk,format=raw,cache=none,werror=stop,rerror=stop,aio=threads -device usb-storage,port=1.2,drive=drive-usb-2-0,id=usb-2-0,removable=on \
2.submit job "USB Exposed Port System Test"
3.
Actual results:
failed as the following error info.
***Failing Exposed Connector***
Failed to verify consistent USB 3.0 Port Mapping. USB 3.0 Hub must enumerate on each exposed connector.
Expected results:
pass.
Additional info:
1 pass this job with "-device usb-ehci,id=controller,..."(usb2.0),as this job actually was skipped(and pass) when attach usb2.0 controller as this is a usb3.0 job.
2 qemu-kvm only emulate usb 1.1 hub.
- PCI UHCI, OHCI, EHCI or XHCI USB controller and a virtual USB-1.1 hub
> Failed to verify consistent USB 3.0 Port Mapping. USB 3.0 Hub must enumerate
> on each exposed connector.> 2 qemu-kvm only emulate usb 1.1 hub.
> - PCI UHCI, OHCI, EHCI or XHCI USB controller and a virtual USB-1.1 hub
USB-3 hubs are needed to pass this test,
but qemu can only emulate an USB-1.1 hub.
So there is no easy way to make this test pass.
We could write a USB-3 hub emulation.
That would be a non-trivial effort though.
Reopen this bz as now it blocks CNV SVVP certification.
CNV use default USB3.0 controller and not allow to configure it. So now QE can not workaround it with USB2.0 controller.
Either CNV allows configuration to USB2.0 or qemu should support a 3.0 USB hub. Otherwise this will block CNV release.
Rather than reopening some old bug, a new feature request should have been made referencing this bug.
Given Gerd's feedback in Comment 3 and Comment 9, it does not seem a high priority for the upstream qemu community and there are currently no resources to work on a usb-3 hub. This would need to be planned for some future release and come thru PM channels.
Created attachment 1581259 [details] html format log Description of problem: Version-Release number of selected component (if applicable): kernel-4.18.0-80.4.1.el8_0.x86_64.rpm qemu-kvm-3.1.0-27.module+el8.0.1+3253+c5371cb3.x86_64 seabios-1.12.0-1.module+el8.0.1+2959+fecd1a40.x86_64 virtio-win-1.9.8-2.el8.iso -viostor virtio-win-prewhql-0.1-172.iso -netkvm How reproducible: 100% Steps to Reproduce: 1.boot guest with the following usb device(usb3.0),one usb controller,one usb hub and two usb storage. -device nec-usb-xhci,id=controller -device usb-hub,id=usbhub,bus=controller.0,port=1 \ -drive file=usb-disk-1.raw,if=none,id=drive-usb-1-0,media=disk,format=raw,cache=none,werror=stop,rerror=stop,aio=threads -device usb-storage,port=1.1,drive=drive-usb-1-0,id=usb-1-0,removable=on \ -drive file=usb-disk-2.raw,if=none,id=drive-usb-2-0,media=disk,format=raw,cache=none,werror=stop,rerror=stop,aio=threads -device usb-storage,port=1.2,drive=drive-usb-2-0,id=usb-2-0,removable=on \ 2.submit job "USB Exposed Port System Test" 3. Actual results: failed as the following error info. ***Failing Exposed Connector*** Failed to verify consistent USB 3.0 Port Mapping. USB 3.0 Hub must enumerate on each exposed connector. Expected results: pass. Additional info: 1 pass this job with "-device usb-ehci,id=controller,..."(usb2.0),as this job actually was skipped(and pass) when attach usb2.0 controller as this is a usb3.0 job. 2 qemu-kvm only emulate usb 1.1 hub. - PCI UHCI, OHCI, EHCI or XHCI USB controller and a virtual USB-1.1 hub