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:
The edk2-ovmf package provides sym link only for OVMF_VARS.fd but not for OVMF_CODE.fd.
Some tools expect to find both CODE and VARS in /usr/share/OVMF so it would be helpful to add sym links from /usr/share/OVMF to /usr/share/edk2/ovmf for at least all the .fd files, perhaps for others as well. Thanks.
Thanks for looking into this.
Yes, in particular I was affected by missing the sym link for OVMF_CODE.fd but perhaps other would be helpful as well.
Thanks.
Comment 3Miroslav Rezanina
2022-10-21 11:32:12 UTC
Just a note - there's no OVMF_CODE.fd shipped for RHEL.
Please refer to the discussion in bug 2132951.
OVMF_CODE.fd has traditionally not been provided in RHEL (unlike in Fedora) because it does not include the (Secure Boot + SMM) feature set. The original idea was to avoid providing a firmware binary in RHEL that lacked the ability to implement (securely) the Secure Boot operational mode.
With the advent of Confidential Computing, a new use case has appeared for a firmware binary that lacks the (Secure Boot + SMM) feature set. However, this binary is not meant as the reinstatement of "OVMF_CODE.fd" in RHEL. Hence the new filename "OVMF_CODE.cc.fd", and the deliberate lack of a compatibility symlink. Please refer to the commit message in <https://gitlab.com/redhat/rhel/src/edk2/-/commit/14f5d2513745> (which is on the "rhel-8.5.0-20200602" branch).
Thus, I'd argue against additional symlinks in RHEL. Either way, I believe bug 2132951 should be solved first.
Comment 6Miroslav Rezanina
2022-10-25 12:47:03 UTC
As we do not provide required package so we can't create link and there isn't good enough reason for linking other files, closing the BZ.