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.
Description of problem:
boot a guest with a simulated usb-storage using xhci controller, but the seabios fail to detect it in boot menu.
BTW, both the Q35 and pc-i440fx-1.4 have this issue. if i test the usb-storage using echi controller, it have no such issue.
Version-Release number of selected component (if applicable):
host info:
host info:
kernel-3.9.0-0.rc4.45.el7.x86_64
qemu-kvm-1.4.0-1.el7.x86_64
seabios-1.7.2-0.2.gita810e4e7.el7.x86_64
guest info:
windows: win2012/win8 64bit
rhel7: kernel-3.9.0-0.rc4.45.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1.boot a guest with a simulated usb-storage using xhci controller.
e.g:...-boot menu=on...-device nec-usb-xhci,id=xhci0 -drive file=/home/my-usb-storage.qcow2,if=none,id=drive-usb-0-1,media=disk,format=qcow2,cache=none,aio=native -device usb-storage,drive=drive-usb-0-1,id=usb-0-1,removable=on
2.press F12 during POST.
3.info block/usb in HMP monitor.
Actual results:
after step 2, there is no usb storage device listed in boot menu, i will attach the screenshot later.
Press F12 for boot menu.
Select boot device:
1. virtio-scsi Drive QEMU HARDDISK 1.4.
2. virtio-scsi Drive QEMU HARDDISK 1.4.
3. Legacy option rom
4. Floppy [drive A]
5. iPXE (PCI 00:05.0)
after step 3,
(qemu) info block
drive-system-disk: removable=0 io-status=ok file=/home/RHEL-Server-7.0-64-scsi.qcow2 ro=0 drv=qcow2 encrypted=0 bps=0 bps_rd=0 bps_wr=0 iops=0 iops_rd=0 iops_wr=0
drive-data-disk: removable=0 io-status=ok file=/home/my-data-disk.raw ro=0 drv=raw encrypted=0 bps=0 bps_rd=0 bps_wr=0 iops=0 iops_rd=0 iops_wr=0
drive-usb-0-1: removable=1 locked=0 tray-open=0 io-status=ok file=/home/my-usb-storage.qcow2 ro=0 drv=qcow2 encrypted=0 bps=0 bps_rd=0 bps_wr=0 iops=0 iops_rd=0 iops_wr=0
ide1-cd0: removable=1 locked=0 tray-open=0 [not inserted]
floppy0: removable=1 locked=0 tray-open=0 [not inserted]
sd0: removable=1 locked=0 tray-open=0 [not inserted]
(qemu) info usb
Device 0.1, Port 1, Speed 480 Mb/s, Product QEMU USB Tablet
Device 0.1, Port 2, Speed 12 Mb/s, Product QEMU USB Mouse
Device 1.0, Port 1, Speed 5000 Mb/s, Product QEMU USB MSD
(qemu)
Expected results:
the seabios should list the usb storage device correctly, like:
Press F12 for boot menu.
Select boot device:
1. virtio-scsi Drive QEMU HARDDISK 1.4.
2. virtio-scsi Drive QEMU HARDDISK 1.4.
3. Legacy option rom
4. Floppy [drive A]
5. iPXE (PCI 00:05.0)
6. USB MSC Drive QEMU QEMU HARDDISK 1.4. <-----example
Additional info:
This request was resolved in Red Hat Enterprise Linux 7.0.
Contact your manager or support representative in case you have further questions about the request.