On Wed, Feb 18, 2026 at 01:05:38PM +0100, Andrea Bolognani via Devel wrote: > This test case demonstrates how to automatically configure an > aarch64 guest so that Secure Boot support is available and only > signed operating systems are allowed to boot. > > It currently fails because there is no firmware descriptor that > describes a suitable firmware build yet. That will change in a > future commit. > > In addition to the latest version, the test case is also executed > against QEMU 8.2.0 specifically. This version of the test case is > intended to fail, because the uefi-vars device that we need to > support Secure Boot on aarch64 was not yet available in that > version of QEMU. The exact error message will change down the > line. > > Signed-off-by: Andrea Bolognani <[email protected]> > --- > ...fi-enrolled-keys-aarch64.aarch64-8.2.0.err | 1 + > ...fi-enrolled-keys-aarch64.aarch64-8.2.0.xml | 30 +++++++++++++++++++ > ...i-enrolled-keys-aarch64.aarch64-latest.err | 1 + > ...i-enrolled-keys-aarch64.aarch64-latest.xml | 30 +++++++++++++++++++ > ...irmware-auto-efi-enrolled-keys-aarch64.xml | 20 +++++++++++++ > tests/qemuxmlconftest.c | 2 ++ > 6 files changed, 84 insertions(+) > create mode 100644 > tests/qemuxmlconfdata/firmware-auto-efi-enrolled-keys-aarch64.aarch64-8.2.0.err > create mode 100644 > tests/qemuxmlconfdata/firmware-auto-efi-enrolled-keys-aarch64.aarch64-8.2.0.xml > create mode 100644 > tests/qemuxmlconfdata/firmware-auto-efi-enrolled-keys-aarch64.aarch64-latest.err > create mode 100644 > tests/qemuxmlconfdata/firmware-auto-efi-enrolled-keys-aarch64.aarch64-latest.xml > create mode 100644 > tests/qemuxmlconfdata/firmware-auto-efi-enrolled-keys-aarch64.xml
Reviewed-by: Daniel P. Berrangé <[email protected]> With regards, Daniel -- |: https://berrange.com ~~ https://hachyderm.io/@berrange :| |: https://libvirt.org ~~ https://entangle-photo.org :| |: https://pixelfed.art/berrange ~~ https://fstop138.berrange.com :|
