Bug 2228485

Summary: "No bootable device" with OS boot disk interface VirtIO-SCSI and with more than 9 VirtIO disks. [rhel-8.8.0.z]
Product: Red Hat Enterprise Linux 8 Reporter: RHEL Program Management Team <pgm-rhel-tools>
Component: seabiosAssignee: Jon Maloy <jmaloy>
Status: CLOSED ERRATA QA Contact: Xueqiang Wei <xuwei>
Severity: high Docs Contact:
Priority: unspecified    
Version: 8.6CC: aliang, coli, gveitmic, jinzhao, jmaloy, juzhang, osteffen, pbonzini, pkang, qinwang, tzheng, vgoyal, virt-maint, xuwei, ymankad, zhguo
Target Milestone: rcKeywords: Triaged, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: seabios-1.16.0-4.module+el8.8.0+19627+2d14cb21 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 2227373 Environment:
Last Closed: 2023-09-19 14:37:12 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 2227373    
Bug Blocks:    

Comment 6 Yanan Fu 2023-08-10 11:19:48 UTC
QE bot(pre verify): Set 'Verified:Tested,SanityOnly' as gating/tier1 test pass.

Comment 7 Xueqiang Wei 2023-08-14 17:36:39 UTC
Reproduced it with seabios-bin-1.16.0-3.module+el8.8.0+16781+9f4724c2.noarch, boot a guest with 1 virio-scsi disk and 10 virio-blk disks, hitting "No bootable device".

Tested with seabios-bin-1.16.0-4.module+el8.8.0+19627+2d14cb21.noarch, not hit this issue.
1. boot a guest with 1 virio-scsi disk and 10 virio-blk disks, the guest boot successfully.
2. boot a guest with 1 virio-scsi disk and 16 virio-blk disks, the guest boot successfully.

And run seabios test loop, no new bug was found. So set status to VERIFIED.

Versions:
kernel-4.18.0-477.23.1.el8_8.x86_64
qemu-kvm-6.2.0-32.module+el8.8.0+18361+9f407f6e
seabios-bin-1.16.0-4.module+el8.8.0+19627+2d14cb21.noarch

Comment 11 errata-xmlrpc 2023-09-19 14:37:12 UTC
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 (Important: virt:rhel and virt-devel:rhel security and bug fix update), 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-2023:5264