Bug 1720974 - [virtio-win][svvp][ws2019/ws2022] job "USB Exposed Port System Test" failed with "Failed to verify consistent USB 3.0 Port Mapping."
Summary: [virtio-win][svvp][ws2019/ws2022] job "USB Exposed Port System Test" failed w...
Keywords:
Status: CLOSED CANTFIX
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: qemu-kvm
Version: 9.2
Hardware: Unspecified
OS: Unspecified
medium
urgent
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: Qianqian Zhu
URL:
Whiteboard:
Depends On:
Blocks: 2105905 2165847
TreeView+ depends on / blocked
 
Reported: 2019-06-17 03:12 UTC by xiagao
Modified: 2023-03-07 07:25 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-03-07 07:25:11 UTC
Type: Feature Request
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
html format log (283.08 KB, text/html)
2019-06-17 03:12 UTC, xiagao
no flags Details
all hlk logs (13.66 MB, application/gzip)
2019-06-17 03:14 UTC, xiagao
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-147241 0 None None None 2023-02-01 08:12:29 UTC

Description xiagao 2019-06-17 03:12:52 UTC
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

Comment 1 xiagao 2019-06-17 03:14:43 UTC
Created attachment 1581260 [details]
all hlk logs

Comment 3 Gerd Hoffmann 2019-07-30 13:23:19 UTC
> 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.

Comment 7 Qianqian Zhu 2023-02-01 08:09:42 UTC
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.

Comment 10 John Ferlan 2023-02-07 11:32:04 UTC
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.


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