From: Tomas Volf <~@wolfsden.cz>
To: 68286@debbugs.gnu.org
Subject: bug#68286: ovmf does not contain secureboot firmware
Date: Sat, 6 Jan 2024 14:45:17 +0100 [thread overview]
Message-ID: <ZZlZbUOr1BGtKJ0q@ws> (raw)
[-- Attachment #1: Type: text/plain, Size: 2116 bytes --]
Hello,
looking at the ovmf package, is seems that it does not contain files required
for secureboot. When I compare what Archlinux ships:
usr/share/edk2/ia32/OVMF.4m.fd
usr/share/edk2/ia32/OVMF.fd
usr/share/edk2/ia32/OVMF_CODE.4m.fd
usr/share/edk2/ia32/OVMF_CODE.csm.4m.fd
usr/share/edk2/ia32/OVMF_CODE.csm.fd
usr/share/edk2/ia32/OVMF_CODE.fd
usr/share/edk2/ia32/OVMF_CODE.secboot.4m.fd
usr/share/edk2/ia32/OVMF_CODE.secboot.fd
usr/share/edk2/ia32/OVMF_VARS.4m.fd
usr/share/edk2/ia32/OVMF_VARS.fd
usr/share/edk2/x64/
usr/share/edk2/x64/MICROVM.4m.fd
usr/share/edk2/x64/MICROVM.fd
usr/share/edk2/x64/OVMF.4m.fd
usr/share/edk2/x64/OVMF.fd
usr/share/edk2/x64/OVMF_CODE.4m.fd
usr/share/edk2/x64/OVMF_CODE.csm.4m.fd
usr/share/edk2/x64/OVMF_CODE.csm.fd
usr/share/edk2/x64/OVMF_CODE.fd
usr/share/edk2/x64/OVMF_CODE.secboot.4m.fd
usr/share/edk2/x64/OVMF_CODE.secboot.fd
usr/share/edk2/x64/OVMF_VARS.4m.fd
usr/share/edk2/x64/OVMF_VARS.fd
with what we do:
/gnu/store/nqv29p1kz1lwc6g3rifyi5mrapcx97wf-ovmf-202308/share/firmware/ovmf_code_ia32.bin
/gnu/store/nqv29p1kz1lwc6g3rifyi5mrapcx97wf-ovmf-202308/share/firmware/ovmf_code_x64.bin
/gnu/store/nqv29p1kz1lwc6g3rifyi5mrapcx97wf-ovmf-202308/share/firmware/ovmf_ia32.bin
/gnu/store/nqv29p1kz1lwc6g3rifyi5mrapcx97wf-ovmf-202308/share/firmware/ovmf_vars_ia32.bin
/gnu/store/nqv29p1kz1lwc6g3rifyi5mrapcx97wf-ovmf-202308/share/firmware/ovmf_vars_x64.bin
/gnu/store/nqv29p1kz1lwc6g3rifyi5mrapcx97wf-ovmf-202308/share/firmware/ovmf_x64.bin
There seem to be some files missing. The secboot would be useful, but the csm
might be as well.
I tried to make a patch to build multiple firmwares, however due to how other
packages inherit from it, it was quite messy. I wonder if having just a single
ovmf package would simplify things. The size bloat from merging them
seems... negligible. At least for the QEMU use case.
Have a nice day,
Tomas Volf
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
reply other threads:[~2024-01-06 13:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZZlZbUOr1BGtKJ0q@ws \
--to=~@wolfsden.cz \
--cc=68286@debbugs.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).