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.
Agree with comment 3, unless the device has a *bootable* ROM this is the expected behavior. SR-IOV VFs do not have a ROM by definition so the expected results are wrong for this device. Only the PF even has a chance of being bootable without specifying a romfile for the device. If host dmesg reports an invalid rom file message then the rom is not bootable.
Check result:
This is a configuration issue, not a product bug.
XL710 nic need to be configured in "Device Setting" in BIOS.
"Device Setting" ---> XL710 nic --->"NIC Configuration" ---> "Legacy Boot Protocol" ---> "PXE"
By default, the legacy boot protocol is "NONE", so we can not see the PF in seabios even if the device has one bootable rom.
Created attachment 1202807 [details] seabios_esc.log Description of problem: No vfio device displayed on seabios boot menu. Version-Release number of selected component (if applicable): kernel version: 3.10.0-505.el7.x86_64 qemu-kvm-rhev version: 3.10.0-505.el7.x86_64 seabios version: 3.10.0-505.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.Enable iommu(intel_iommu=on) and load vfio/vfio-pci(modprobe vfio/vfio-pci) 2.Get Devices: #lspci ..... 04:00.0 Ethernet controller: Intel Corporation Ethernet Controller XL710 for 40GbE QSFP+ (rev 02) 04:00.1 Ethernet controller: Intel Corporation Ethernet Controller XL710 for 40GbE QSFP+ (rev 02) .... 3.Create a virtual Ethernet Card. #echo 1 > /sys/bus/pci/devices/0000\:04\:00.1/sriov_numvfs 4.Check Devices: #lspci ..... 04:00.0 Ethernet controller: Intel Corporation Ethernet Controller XL710 for 40GbE QSFP+ (rev 02) 04:00.1 Ethernet controller: Intel Corporation Ethernet Controller XL710 for 40GbE QSFP+ (rev 02) 04:0a.0 Ethernet controller: Intel Corporation XL710/X710 Virtual Function (rev 02) .... 5.Check Device Vendor/Device ID. # lspci -n -s 04:00.0 04:00.0 0200: 8086:1583 (rev 02) # lspci -n -s 04:0a.0 04:0a.0 0200: 8086:154c (rev 02) 6.Unbind device from host. #echo 0000:04:00.0 > /sys/bus/pci/devices/0000\:04\:00.0/driver/unbind #echo 0000:04:0a.0 > /sys/bus/pci/devices/0000\:04\:0a.0/driver/unbind 7.Assign Device to vfio-pci # echo "8086 1583" >/sys/bus/pci/drivers/vfio-pci/new_id # echo "8086 1583" >/sys/bus/pci/drivers/vfio-pci/remove_id # echo "8086 154c" >/sys/bus/pci/drivers/vfio-pci/new_id # echo "8086 154c" >/sys/bus/pci/drivers/vfio-pci/remove_id 8.Start guest with assigned device: usr/libexec/qemu-kvm -name rhel7 \ -machine pc,accel=kvm,usb=off,vmport=off \ -cpu host \ -m 4096 \ -realtime mlock=off \ -smp 8 \ -uuid 1534fa42-4818-4493-9f67-eee5ba758385 \ -no-user-config -nodefaults \ -chardev socket,id=qmp_id_catch_monitor,path=/var/tmp/test1,server,nowait \ -mon chardev=qmp_id_catch_monitor,id=monitor,mode=readline \ -no-hpet \ -boot menu=on,splash-time=6000 \ -vga qxl \ -vnc 0:3 \ -netdev tap,id=hostnet10 \ -device virtio-net-pci,netdev=hostnet10,id=net10,mac=50:54:00:49:b2:5f \ -spice ipv4,port=5000,disable-ticketing \ -enable-kvm \ -monitor stdio \ -device vfio-pci,host=04:00.0,id=hostnet_PF \ -chardev socket,id=ovmf_log,path=/var/tmp/seabios,server,nowait \ -device isa-debugcon,chardev=ovmf_log,iobase=0x402 \ -drive file=/home/rhel6_8.qcow2,if=none,id=drive-ide0-0-0-0,format=qcow2,cache=none,aio=native,snapshot=off \ -device ide-hd,bus=ide.0,drive=drive-ide0-0-0-0,id=ide0-0-0-0 \ -device vfio-pci,host=04:0a.0,id=hostnet_VF \ 9.Press ESC to enter boot menu, check the menu, then continue the boot process. Actual results: No vfio device displayed on seabios boot menu. But we can see the assigned device in guest， # lspci 00:00.0 Host bridge: Intel Corporation 440FX - 82441FX PMC [Natoma] (rev 02) 00:01.0 ISA bridge: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] 00:01.1 IDE interface: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] 00:01.3 Bridge: Intel Corporation 82371AB/EB/MB PIIX4 ACPI (rev 03) 00:02.0 VGA compatible controller: Red Hat, Inc. QXL paravirtual graphic card (rev 04) 00:03.0 Ethernet controller: Red Hat, Inc Virtio network device 00:04.0 Ethernet controller: Intel Corporation Ethernet Controller XL710 for 40GbE QSFP+ (rev 02) 00:05.0 Ethernet controller: Intel Corporation XL710/X710 Virtual Function (rev 02 Expected results: vfio device displayed on seabios boot menu. Additional info: a.boot log---attachment:seabios_esc.log b.Screen capture of boot menu ---attachment:boot_menu b.seabios-1.9.1-5 also have this problem.