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.
We would like to evaluate the pros/cons and feasibility of having an extra build of edk2 streamlined for SEV-ES. A minimalistic binary is desired for a reduced footprint and attack surface, but it also might be required due to limitations in the implementation.
The idea here is to have multiple builds of edk2 generated from the same SRPM (as sub-packages).
Some upstream references:
[edk2-devel] [PATCH v3 0/5] SEV-ES TPM enablement fixes
https://edk2.groups.io/g/devel/message/74608 (Merged in commit range ab957f036f67..1e6b0394d6c0, via <https://github.com/tianocore/edk2/pull/1620>).
We're planning a rebase of edk2 in RHEL-8.5: Bug #1938238
(BTW, this bug is open to the public)
Virt-QE: for the time being, the new subpackage / binary should only be sanity checked; it should work equivalently to the usual edk2-ovmf package, except you should expect that the Secure Boot feature is not built into the binary. Actual SEV-ES support will come with bug 1868079. Thanks!
Virt-QE: comment 5 applies only to the raw QEMU command line. If you want to regression-test with libvirt, you'll have to wait until a libvirt RHBZ exists (and is fixed) for recognizing the "amd-sev-es" feature in the fw descriptor. The upstream libvirt ticket for that is <https://gitlab.com/libvirt/libvirt/-/issues/156>. Thanks.
(In reply to Laszlo Ersek from comment #5)
> Virt-QE: for the time being, the new subpackage / binary should only be
> sanity checked; it should work equivalently to the usual edk2-ovmf package,
> except you should expect that the Secure Boot feature is not built into the
> binary. [...]
(In reply to Laszlo Ersek from comment #6)
> Virt-QE: comment 5 applies only to the raw QEMU command line. [...]
Note that the QEMU command line is affected. The following option must be *removed*, relative to what you are used to:
-global driver=cfi.pflash01,property=secure,value=on
Thanks.
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 (Moderate: edk2 security, bug fix, and enhancement update), 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://access.redhat.com/errata/RHSA-2021:4198