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.
Bug 1515393 - bootindex is not taken into account for virtio-scsi devices on ppc64 if the LUN is >= 256
Summary: bootindex is not taken into account for virtio-scsi devices on ppc64 if the L...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: qemu-kvm-rhev
Version: 7.5
Hardware: ppc64le
OS: Linux
low
low
Target Milestone: rc
: ---
Assignee: Thomas Huth
QA Contact: Yongxue Hong
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-11-20 17:47 UTC by Thomas Huth
Modified: 2018-04-11 00:51 UTC (History)
6 users (show)

Fixed In Version: qemu-kvm-rhev-2.10.0-9.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-04-11 00:49:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1431584 0 low CLOSED SLOF does not support LUNs greater than 255 2021-02-22 00:41:40 UTC
Red Hat Product Errata RHSA-2018:1104 0 None None None 2018-04-11 00:51:20 UTC

Internal Links: 1431584

Description Thomas Huth 2017-11-20 17:47:28 UTC 
Description of problem:
When using virtio-scsi disks with "bootindex" properties, the guest firmware (SLOF) fails to honor the boot order of devices that are using a LUN >= 256.

Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.10.0-4.el7
SLOF-20170724-2.git89f519f.el7.noarch

How reproducible:
100%

Steps to Reproduce:
Start QEMU for example with a command line like this:
sudo /usr/libexec/qemu-kvm -nodefaults -serial mon:stdio -nographic -enable-kvm -device virtio-scsi-pci,id=vsp0,bus=pci.0 -drive id=hdimg1,if=none,format=qcow2,file=/var/lib/libvirt/images/disk.img -device scsi-hd,drive=hdimg1,id=hd1,bus=vsp0.0,bootindex=0,channel=0,scsi-id=0,lun=256 -drive id=cdimg1,if=none,media=cdrom,file=/var/lib/libvirt/images/RHEL-7.iso -device scsi-cd,id=cd1,drive=cdimg1,bus=vsp0.0,bootindex=1

Actual results:
SLOF boots from the CD-ROM device (that has bootindex=1).

Expected results:
SLOF should boot from the harddisk device (that has bootindex=0)

Additional info:
I've already suggested a patch for this problem on the upstream qemu mailing list here:
https://lists.gnu.org/archive/html/qemu-devel/2017-11/msg03521.html
("hw/ppc/spapr: Fix virtio-scsi bootindex handling for LUNs >= 256")
Comment 2 Miroslav Rezanina 2017-11-28 10:52:57 UTC 
Fix included in qemu-kvm-rhev-2.10.0-9.el7
Comment 3 Minjia Cai 2017-11-30 08:53:21 UTC 
Reproduced Version:
Host (RHEL7.5):
Compose: RHEL-7.5-20171107.1
kernel-3.10.0-797.el7
qemu-kvm-rhev-2.10.0-7.el7
SLOF-20170724-2.git89f519f.el7.noarch

Guest:
Compose: RHEL-7.5-20171107.1
kernel-3.10.0-797.el7
Steps to Reproduce is same the as comment0：

/usr/libexec/qemu-kvm -nodefaults -serial mon:stdio -nographic -enable-kvm -device virtio-scsi-pci,id=vsp0,bus=pci.0 -drive id=hdimg1,if=none,format=qcow2,file=/home/micai/RHEL.7.5.qcow2  -device scsi-hd,drive=hdimg1,id=hd1,bus=vsp0.0,bootindex=0,channel=0,scsi-id=0,lun=256 -drive id=cdimg1,if=none,media=cdrom,file=/home/micai/RHEL-7.5-20171107.1-Server-ppc64-dvd1.iso  -device scsi-cd,id=cd1,drive=cdimg1,bus=vsp0.0,bootindex=1

Actual results:
SLOF boots from the CD-ROM device (that has bootindex=1).

Steps to verified is same the as comment0：
Change qemu-kvm-rhev-2.10.0-7.el7 to qemu-kvm-rhev-2.10.0-9.el7
Actual results:

SLOF should boot from the harddisk device (that has bootindex=0)
Comment 5 Qunfang Zhang 2017-12-04 03:30:32 UTC 
(In reply to Minjia Cai from comment #3)
> Reproduced Version:
> Host (RHEL7.5):
> Compose: RHEL-7.5-20171107.1
> kernel-3.10.0-797.el7
> qemu-kvm-rhev-2.10.0-7.el7
> SLOF-20170724-2.git89f519f.el7.noarch
> 
> Guest:
> Compose: RHEL-7.5-20171107.1
> kernel-3.10.0-797.el7
> Steps to Reproduce is same the as comment0：
> 
> /usr/libexec/qemu-kvm -nodefaults -serial mon:stdio -nographic -enable-kvm
> -device virtio-scsi-pci,id=vsp0,bus=pci.0 -drive
> id=hdimg1,if=none,format=qcow2,file=/home/micai/RHEL.7.5.qcow2  -device
> scsi-hd,drive=hdimg1,id=hd1,bus=vsp0.0,bootindex=0,channel=0,scsi-id=0,
> lun=256 -drive
> id=cdimg1,if=none,media=cdrom,file=/home/micai/RHEL-7.5-20171107.1-Server-
> ppc64-dvd1.iso  -device scsi-cd,id=cd1,drive=cdimg1,bus=vsp0.0,bootindex=1
> 
> Actual results:
> SLOF boots from the CD-ROM device (that has bootindex=1).
> 
> Steps to verified is same the as comment0：
> Change qemu-kvm-rhev-2.10.0-7.el7 to qemu-kvm-rhev-2.10.0-9.el7
> Actual results:
> 
> SLOF should boot from the harddisk device (that has bootindex=0)

Hi, Minjia

In the test result of qemu-kvm-rhev-2.10.0-9.el7, you used the word "should", but actually SLOF indeed boot from harddisk that has bootindex=0, right?

Thanks,
Qunfang
Comment 6 Minjia Cai 2017-12-04 04:29:29 UTC 
(In reply to Qunfang Zhang from comment #5)
> (In reply to Minjia Cai from comment #3)
> > Reproduced Version:
> > Host (RHEL7.5):
> > Compose: RHEL-7.5-20171107.1
> > kernel-3.10.0-797.el7
> > qemu-kvm-rhev-2.10.0-7.el7
> > SLOF-20170724-2.git89f519f.el7.noarch
> > 
> > Guest:
> > Compose: RHEL-7.5-20171107.1
> > kernel-3.10.0-797.el7
> > Steps to Reproduce is same the as comment0：
> > 
> > /usr/libexec/qemu-kvm -nodefaults -serial mon:stdio -nographic -enable-kvm
> > -device virtio-scsi-pci,id=vsp0,bus=pci.0 -drive
> > id=hdimg1,if=none,format=qcow2,file=/home/micai/RHEL.7.5.qcow2  -device
> > scsi-hd,drive=hdimg1,id=hd1,bus=vsp0.0,bootindex=0,channel=0,scsi-id=0,
> > lun=256 -drive
> > id=cdimg1,if=none,media=cdrom,file=/home/micai/RHEL-7.5-20171107.1-Server-
> > ppc64-dvd1.iso  -device scsi-cd,id=cd1,drive=cdimg1,bus=vsp0.0,bootindex=1
> > 
> > Actual results:
> > SLOF boots from the CD-ROM device (that has bootindex=1).
> > 
> > Steps to verified is same the as comment0：
> > Change qemu-kvm-rhev-2.10.0-7.el7 to qemu-kvm-rhev-2.10.0-9.el7
> > Actual results:
> > 
> > SLOF should boot from the harddisk device (that has bootindex=0)
> 
> Hi, Minjia
> 
> In the test result of qemu-kvm-rhev-2.10.0-9.el7, you used the word
> "should", but actually SLOF indeed boot from harddisk that has bootindex=0,
> right?
> 
> Thanks,
> Qunfang

Hi,Qunfang
 Yes，you are right.I want to express that SLOF boots from harddisk that has bootindex=0.Sorry,I use the wrong word "should"
Comment 7 Qunfang Zhang 2017-12-05 06:35:37 UTC 
(In reply to Minjia Cai from comment #6)
> 
> Hi,Qunfang
>  Yes，you are right.I want to express that SLOF boots from harddisk that has
> bootindex=0.Sorry,I use the wrong word "should"

Thanks for confirmation, never mind.
Comment 10 errata-xmlrpc 2018-04-11 00:49:36 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, 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-2018:1104
Note You need to log in before you can comment on or make changes to this bug.