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:

qemu-kvm doesn't currently log anything to libvirt when it fails to load the PCI option ROM for a device.  It will also attempt to re-load the ROM on every guest access, which could present unexpected behavior if it doesn't fail consistently.

The following commits improve ROM handling:

d20b43d vfio: warn if host device rom can't be read
e638073 vfio: Do not reattempt a failed rom read
db01eed vfio: Correction in vfio_rom_read when attempting rom loading

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Boot a VM with a vfio-pci assigned device that supports a ROM, but gets an invalid ROM contents message in dmesg
2.
3.

Actual results:
The invalid ROM contents message in dmesg is repeated every time the guest reboots within the same instance and there's no error logged to libvirt.

Expected results:
The libvirt log for the domain should include an error report and we shouldn't attempt to re-load the ROM on reboots within that instance (as noted both by the libvirt log message not being repeated and the kernel invalid ROM contents not being repeated).

Additional info:

Do we need to clone this bz to qemu-kvm-rhev component?

Best Regards,
Junyi

Fix included in qemu-kvm-1.5.3-88.el7

According to comment5 and comment6, set this issue as verified.

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-2213.html