Thank you Hector for the updates!
After plenty of discussions we agreed that we still want to go with
option (2) from comment #6, i.e. implementing a bigger scope (that is
more isolated, though, inside a new OVMF.amdsev.fd file).
This new OVMF.amdsev.fd file would enable SEV-ES support in addition to
SEV-SNP support (only when used with newer Qemu, e.g. from server-
backports).
It's the same solution we applied to Plucky+ which also covers this reduced
"SEV-ES" scope.
The testplan was updated accordingly to only test for SEV-ES on Noble, as
SEV-SNP is not available by default on Noble.
** Changed in: edk2 (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2122286
Title:
firmware definitions lack "amd-sev-es" feature
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/2122286/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
