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.
Test it on rhel 6, steps as followings:
1.boot guests using following cli:
/usr/libexec/qemu-kvm -m 2G \
-device virtio-scsi-pci,id=scsi0 \
-drive file=/mnt/windows_img/win2012-64-virtio.raw,if=none,id=disk1,format=raw,snapshot=on \
-device scsi-hd,drive=disk1,id=sys-disk1,scsi-id=100,lun=0,bootindex=0 \
-boot menu=on -monitor stdio -vnc :2 \
-drive file=/mnt/linux_img/RHEL-Server-7.0-64.raw,if=none,id=disk2,snapshot=on \
-device scsi-hd,drive=disk2,id=sys-disk2,scsi-id=0,lun=0,bootindex=3 -S
2.check the boot order in seabios.
Press F12 for boot menu.
Actual results:
sys-disk2 is the first disk and sys-disk1 is the second disk when press F12.
Such as:
1. virtio-scsi Drive QEMU QEMU HARDDISK 1.5.
2. virtio-scsi Drive QEMU QEMU HARDDISK 1.5.
...
Expected results:
the order of the boot device in seabios should the same to we specified the bootindex in qemu-kvm command line.
Version of components:
# rpm -qa|grep qemu-kvm && rpm -qa|grep seabios
qemu-kvm-debuginfo-0.12.1.2-2.436.el6.x86_64
qemu-kvm-tools-0.12.1.2-2.436.el6.x86_64
qemu-kvm-0.12.1.2-2.436.el6.x86_64
seabios-0.6.1.2-28.el6.x86_64
Reproduce this bug as follow version:
Host
# uname -r
2.6.32-539.el6.x86_64
# rpm -q qemu-kvm-rhev
qemu-kvm-rhev-0.12.1.2-2.448.el6.x86_64
# rpm -q seabios
seabios-0.6.1.2-28.el6.x86_64
Steps
1.Boot guest with
..-device virtio-scsi-pci,id=scsi0 -drive file=/home/rhel6.6.raw,if=none,id=disk1,format=raw -device scsi-hd,drive=disk1,id=sys-disk1,scsi-id=100,lun=0,bootindex=0 -boot menu=on -monitor stdio -vnc :2 -drive file=/home/win8-64-virtio.raw,if=none,id=disk2 -device scsi-hd,drive=disk2,id=sys-disk2,scsi-id=0,lun=0,bootindex=3...
Results: guest boot up from the "bootindex=3" imag.
Verify this bug as follow version.
Host
# uname -r
2.6.32-539.el6.x86_64
# rpm -q qemu-kvm-rhev
qemu-kvm-rhev-0.12.1.2-2.448.el6.x86_64
# rpm -q seabios
seabios-0.6.1.2-29.el6.x86_64
Steps as same as reproduce
Resutls:
Guest boot up from "bootindex=0" imag, work well
According to above test , this bug has been fixed.
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://rhn.redhat.com/errata/RHEA-2015-1355.html