From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH edk2-firmware/qemu-server/manager 0/4] ovmf: support pre-enrolled-keys for ARM EFI disks
Date: Wed, 20 May 2026 16:20:31 +0200 [thread overview]
Message-ID: <20260520142044.502304-1-f.ebner@proxmox.com> (raw)
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.
pve-edk2-firmware:
Fiona Ebner (2):
d/rules: use dedicated install dir for AAVMF build
d/{rules,install}: build secureboot-enabled image for aarch64
debian/pve-edk2-firmware-aarch64.install | 4 +--
debian/rules | 39 +++++++++++++++---------
2 files changed, 27 insertions(+), 16 deletions(-)
qemu-server:
Fiona Ebner (1):
ovmf: honor pre-enrolled-keys setting for aarch64
src/PVE/QemuServer/OVMF.pm | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
manager:
Fiona Ebner (1):
ui: qemu: hardware edit: create EFI disk via asynchronous API
www/manager6/qemu/HDEfi.js | 1 +
1 file changed, 1 insertion(+)
Summary over all repositories:
4 files changed, 46 insertions(+), 16 deletions(-)
--
Generated by git-murpp 0.5.0
next reply other threads:[~2026-05-20 14:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-20 14:20 Fiona Ebner [this message]
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
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=20260520142044.502304-1-f.ebner@proxmox.com \
--to=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.