From: "Lukas Sichert" <l.sichert@proxmox.com>
To: "Fiona Ebner" <f.ebner@proxmox.com>, <pve-devel@lists.proxmox.com>
Subject: Re: [PATCH edk2-firmware/qemu-server/manager 0/4] ovmf: support pre-enrolled-keys for ARM EFI disks
Date: Wed, 22 Jul 2026 14:43:05 +0200 [thread overview]
Message-ID: <DK53X818MWGT.20OCF8X0YMPCU@proxmox.com> (raw)
In-Reply-To: <20260520142044.502304-1-f.ebner@proxmox.com>
On 2026-05-20 16:20, Fiona Ebner <f.ebner@proxmox.com> wrote:
> Have the firmware package for ARM ship the secureboot-enabled CODE
> image. The VARS image with the pre-enrolled-keys was already shipped.
>
> Let qemu-server actually honor the pre-enrolled-keys setting and use
> those images when requested.
>
> Finally, a small UX improvment to make the task warning when the
> firmware package is outdated visible in the UI.
>
> Might be nice to have soonish after the next point release since ARM
> support was generally improved with that release.
I tested this by building pve-edk2-firmware on an x86 machine and the
qemu-server and pve-manager packages on an ARM machine, then installing
all packages on that ARM machine.
Before applying the patch, the following warning was printed in the task
log:
WARN: EFI disk without 'ms-cert=2023k' option, suggesting that not all
UEFI 2023 certificates from Microsoft are enrolled yet.
After applying the patch, the warning disappeared and the EFI disk had
the ms-cert=2023k option. Inside the VM, I verified the result using:
'mokutil --sb-state', which returned 'SecureBoot enabled'.
One minor issue:
I do not know whether this is intentional, but after applying only the
first patch in pve-edk2-firmware, make deb fails. After applying the
second patch as well, it succeeds.
This fixes the issue for me, so please consider:
Tested-by: Lukas Sichert <l.sichert@promxox.com>
prev parent reply other threads:[~2026-07-22 12:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 14:20 [PATCH edk2-firmware/qemu-server/manager 0/4] ovmf: support pre-enrolled-keys for ARM EFI disks Fiona Ebner
2026-05-20 14:20 ` [PATCH edk2-firmware 1/4] d/rules: use dedicated install dir for AAVMF build Fiona Ebner
2026-05-20 14:20 ` [PATCH edk2-firmware 2/4] d/{rules,install}: build secureboot-enabled image for aarch64 Fiona Ebner
2026-05-20 14:20 ` [PATCH qemu-server 3/4] ovmf: honor pre-enrolled-keys setting " Fiona Ebner
2026-05-20 14:20 ` [PATCH manager 4/4] ui: qemu: hardware edit: create EFI disk via asynchronous API Fiona Ebner
2026-07-22 12:43 ` Lukas Sichert [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=DK53X818MWGT.20OCF8X0YMPCU@proxmox.com \
--to=l.sichert@proxmox.com \
--cc=f.ebner@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.