-
-
Notifications
You must be signed in to change notification settings - Fork 16.6k
OVMF: include UninstallMemAttrProtocol patch #420069
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
OVMF: include UninstallMemAttrProtocol patch #420069
Conversation
420 69 epic |
a8def94
to
11b932c
Compare
|
What? Is there an upstream edk2 report for this patch? If it's critical for some distributions, and both those distros are including it, I would hope to see it being upstreamed. |
look at pr id
yes, but stalebot closed it tianocore/edk2#10667 also just noticed that Dasharo reverts this completely, so it's also being done on actual hardware Dasharo/edk2#236 |
It seems like upstream considers this a bug in the shim, and even Debian isn't enabling this by default. Is there any reason you can't disable secureboot until RedHat fixes this on their end? |
Secure boot is off in my vm, these features are always enabled |
What's the scope of impact here? Just RHEL-based distros? |
no idea, I only have NixOS and Alma Linux 9 in vms |
Any chance this gets merged? It shouldn't affect anything unless qemu is started with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks alright to me, especially since it's only adding an optional patch that won't affect normal OVMF calls, but I'll defer to @adamcstephens' judgement here.
Newer UEFI specs have some memory protection features which break secure boot shim used at least in RHEL 9. Trying to boot RHEL 9 or clones using our OVMF builds will end up with this on serial
This patch is applied in Debian and Fedora, didn't check anywhere else. They additionally enable it by default on non-secureboot variant, in case of this PR It'll be required to add this to libvirtd domain config:
we could enable it too by setting
--pcd PcdUninstallMemAttrProtocol=TRUE
build flag but idk if this will be correct:Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.