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:
OVMF_CODE.fd should exist under /usr/share/OVMF/

Version-Release number of selected component (if applicable):
ovmf package: ovmf-20160419-2.git90bb4c5.el7
kernel:3.10.0-414.el7.x86_64
qemu-kvm-rhev:qemu-kvm-rhev-2.6.0-4.el7.x86_64

How reproducible:


Steps to Reproduce:
1.Install OVMF-20150414-2.gitc9e5618.el7.noarch.rpm first and follow steps of https://bugzilla.redhat.com/show_bug.cgi?id=1308678#c1, upgrade ovmf package to ovmf-20160419-2.git90bb4c5.el7 as steps and continue.
2.
3.

Actual results:
virt-manager report error:
Error starting domain: internal error: process exited while connecting to monitor: 2016-05-30T09:45:34.204380Z qemu-kvm: -drive file=/usr/share/OVMF/OVMF_CODE.fd,if=pflash,format=raw,unit=0,readonly=on: Could not open '/usr/share/OVMF/OVMF_CODE.fd': No such file or directory

Expected results:
At this point we have verified that a firmware binary has been preserved
under the previous pathname (/usr/share/OVMF/OVMF_CODE.fd), that the secure
boot feature has been removed from it, and that preexistent guests continue
working with it

Additional info:

I think you must have missed the following comments:

https://bugzilla.redhat.com/show_bug.cgi?id=1308678#c10
https://bugzilla.redhat.com/show_bug.cgi?id=1308678#c12

The disappearance of the "OVMF_CODE.fd" file is fully intentional. So I'm closing this one as NOTABUG. If you would like to know more, please follow the internal mailing list links in the second comment noted above. Thanks.