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 1280366[details]
cmd file
Description of problem:
can't bootup from image when attached multi-virtio-scsi disks with multi-luns
Version-Release number of selected component (if applicable):
host:
kernel-3.10.0-666.el7.x86_64
qemu-kvm-rhev-2.9.0-5.el7
guest:
kernel-3.10.0-666.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. run test.sh (refer to the attachment)
Actual results:
can't bootup from image
Expected results:
bootup normally
Additional info:
Not hit this issue on RHEL.7.3:
kernel-3.10.0-514.16.1.el7.x86_64
qemu-kvm-rhev-2.6.0-28.el7_3.9
Not hit this issue:
qemu-kvm-rhev-2.9.0-3.el7
qemu-kvm-rhev-2.9.0-4.el7
set lun=0 for boot image also can not bootup normally.
It is seabios issue:
Not hit this issue on below version:
seabios-1.10.2-2.el7.x86_64.rpm
seabios-bin-1.10.2-2.el7.noarch.rpm
seavgabios-bin-1.10.2-2.el7.noarch.rpm
Hit this issue on:
seabios-1.10.2-3.el7.x86_64.rpm
seabios-bin-1.10.2-3.el7.noarch.rpm
seavgabios-bin-1.10.2-3.el7.noarch.rpm
These patches were rejected upstream:
https://www.mail-archive.com/seabios@seabios.org/msg10086.html
The suggestion is to allocate virtqueue info in high memory, which would allow virtio drivers to support more drives. However, I'm not sure that it would support the full amount used in this testcase (it could still go out of memory).
Reproduced this bug with seabios-1.10.2-4.el7.x86_64 & seabios-1.10.2-3.el7.x86_64 & qemu-kvm-rhev-2.10.0-7.el7.x86_64
steps:
use script test.sh in attachment
result:
can't bootup from image
Verified bug with seabios-1.10.2-7.el7.x86_64 & qemu-kvm-rhev-2.10.0-7.el7.x86_64
Result:
All disks can be found inside guest. and guest works well
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.
https://access.redhat.com/errata/RHBA-2018:0814
Created attachment 1280366 [details] cmd file Description of problem: can't bootup from image when attached multi-virtio-scsi disks with multi-luns Version-Release number of selected component (if applicable): host: kernel-3.10.0-666.el7.x86_64 qemu-kvm-rhev-2.9.0-5.el7 guest: kernel-3.10.0-666.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. run test.sh (refer to the attachment) Actual results: can't bootup from image Expected results: bootup normally Additional info: Not hit this issue on RHEL.7.3: kernel-3.10.0-514.16.1.el7.x86_64 qemu-kvm-rhev-2.6.0-28.el7_3.9 Not hit this issue: qemu-kvm-rhev-2.9.0-3.el7 qemu-kvm-rhev-2.9.0-4.el7