From: Fiona Ebner <f.ebner@proxmox.com>
To: Lukas Sichert <l.sichert@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH qemu-server] OVMF: use Microsoft-keyed vars for aarch64 VMs
Date: Tue, 21 Jul 2026 16:57:33 +0200 [thread overview]
Message-ID: <8e68bde2-66b3-4cce-a565-22f59b38952e@proxmox.com> (raw)
In-Reply-To: <20260721132152.57755-1-l.sichert@proxmox.com>
The CODE image is not secure-boot enabled yet. I already sent a series
in May which also covers that:
https://lore.proxmox.com/pve-devel/20260520142044.502304-1-f.ebner@proxmox.com/
Am 21.07.26 um 3:21 PM schrieb Lukas Sichert:
> Currently, starting VMs on aarch64 warns that not all Microsoft UEFI
> 2023 certificates are enrolled.
>
> Select AAVMF_VARS.ms.fd when pre-enrolled keys are requested to provide
> the Microsoft-enrolled variable store.
>
> Signed-off-by: Lukas Sichert <l.sichert@proxmox.com>
> ---
> src/PVE/QemuServer/OVMF.pm | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/src/PVE/QemuServer/OVMF.pm b/src/PVE/QemuServer/OVMF.pm
> index 7a765fad..ffb2b850 100644
> --- a/src/PVE/QemuServer/OVMF.pm
> +++ b/src/PVE/QemuServer/OVMF.pm
> @@ -52,6 +52,9 @@ my $OVMF = {
> default => [
> "$EDK2_FW_BASE/AAVMF_CODE.fd", "$EDK2_FW_BASE/AAVMF_VARS.fd",
> ],
> + 'default-ms' => [
> + "$EDK2_FW_BASE/AAVMF_CODE.fd", "$EDK2_FW_BASE/AAVMF_VARS.ms.fd",
> + ],
> },
> };
>
> @@ -83,6 +86,8 @@ my sub get_ovmf_files($$$$) {
> } else {
> # TODO: log_warn about use of legacy images for x86_64 with Promxox VE 9
> }
> + } elsif ($arch eq 'aarch64') {
> + $type = 'default-ms' if $efidisk->{'pre-enrolled-keys'};
> }
>
> my ($ovmf_code, $ovmf_vars) = $types->{$type}->@*;
next prev parent reply other threads:[~2026-07-21 14:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 13:21 [PATCH qemu-server] OVMF: use Microsoft-keyed vars for aarch64 VMs Lukas Sichert
2026-07-21 14:57 ` Fiona Ebner [this message]
2026-07-21 15:03 ` Lukas Sichert
2026-07-21 15:06 ` Fiona Ebner
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=8e68bde2-66b3-4cce-a565-22f59b38952e@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=l.sichert@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox