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:
Sub-option bootindex doesn't work for vfio-pci. If specify bootindex=1 for vfio-pci and don't add such option for other bootable devices, seabios doesn't boot from it as top priority.
Version-Release number of selected component (if applicable):
qemu-kvm-rhev-2.3.0-10.el7.x86_64
seabios-1.7.5-11.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1. assign a VF to guest with romfile as well as bootindex=1 specified, like:
-device vfio-pci,host=03:10.6,romfile=808610ca.rom,rombar=1,bootindex=1,addr=0xb
2. don't add bootindex to other devices
3.
Actual results:
SeaBIOS (version seabios-1.7.5-11.el7)
iPXE (http://ipxe.org) 00:0B.0 CA00 PCI2.10 PnP PMM+BFF989E0+BFEF89E0 CA00
Press ESC for boot menu.
Booting from Hard Disk...
Boot failed: not a bootable disk
Booting from ROM...
iPXE (PCI 00:0B.0) starting execution...ok
iPXE initialising devices...ok
Expected results:
After hint "Press ESC for boot menu", the assigned VF should be picked to try booting
Additional info:
This is a regression bug, since qemu-kvm-rhev-2.1.2-23.el7_1.6.x86_64.rpm cannot reproduce such issue. Here is the log:
Press ESC for boot menu.
Booting from ROM...
iPXE (PCI 00:0B.0) starting execution...ok
iPXE initialising devices...ok
iPXE 1.0.0+ () -- Open Source Network Boot Firmware -- http://ipxe.org
Features: DNS HTTP iSCSI TFTP AoE ELF MBOOT PXE bzImage Menu PXEXT
net0: 56:a9:81:44:00:61 using igbvf on PCI00:0b.0 (open)
[Link:up, TX:0 TXE:0 RX:0 RXE:0]
Configuring (net0 56:a9:81:44:00:61)...... ok
(In reply to Alex Williamson from comment #3)
> Does bootindex work for an emulated NIC?
Found it. The problem is isolated to vfio-pci, the code split in preparation for vfio-platform devices added bootindex as a device property, which makes the actual bootindex ignored. Patch posted upstream:
http://lists.nongnu.org/archive/html/qemu-devel/2015-07/msg04435.html
Comment 5Miroslav Rezanina
2015-08-05 08:19:55 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://rhn.redhat.com/errata/RHBA-2015-2546.html