On Wed, Feb 18, 2026 at 01:06:01PM +0100, Andrea Bolognani via Devel wrote:
> Signed-off-by: Andrea Bolognani <[email protected]>
> ---
>  NEWS.rst | 16 ++++++++++++++++
>  1 file changed, 16 insertions(+)

Reviewed-by: Daniel P. Berrangé <[email protected]>

> diff --git a/NEWS.rst b/NEWS.rst
> index 7a80116de3..de54203dfc 100644
> --- a/NEWS.rst
> +++ b/NEWS.rst
> @@ -24,6 +24,22 @@ v12.1.0 (unreleased)
>      example Secure Boot support, is available for the selected architecture 
> and
>      machine type.
>  
> +  * qemu: Add support for uefi-vars device and firmware builds using it
> +
> +    This is particularly noteworthy for people running aarch64 VMs, as it 
> makes
> +    it finally possible to use Secure Boot on the architecture.

"running aarch64 VMs with the 'virt' machine type, ...'


> +
> +    In most cases, no special steps are needed to take advantage of this:
> +    assuming that you have installed a recent version of QEMU, as well as a
> +    build of edk2 that includes the necessary binaries, you can just `enable
> +    Secure Boot <kbase/secureboot.html>`__ as you normally would.
> +
> +    To explicitly request that the uefi-vars device is used even for 
> scenarios
> +    where that would normally not be the case, it's enough to add an empty
> +    ``<varstore/>`` element in the domain XML. More details are available in
> +    the `guest firmware configuration <formatdomain.html#guest-firmware>`__
> +    section of the documentation.
> +
>  * **Improvements**
>  
>  * **Bug fixes**
> -- 
> 2.53.0
> 

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 :|

Reply via email to