Ubuntu 24.04 and virt-manager

[Jeffrey Walton]

On Mon, Sep 8, 2025 at 7:38 AM Jerry Geis <jerry.geis at gmail.com> wrote:

> I have virtual machines that are UEFI...However - I want to define a new
> VM with virt-manager and I am not getting the UEFI options or secure boot
> options.
> OVMF is installed
>
> apt list --installed | grep ovmf
> ovmf/noble-updates,now 2024.02-2ubuntu0.4 all
>
> Thoughts?
>

In the old days, you needed to enable nvram in /etc/libvirt/qemu.conf.  I
don't know what needs to be done nowadays:

$ grep -A 6 -i nvram /etc/libvirt/qemu.conf
# Location of master nvram file
#
# This configuration option is obsolete. Libvirt will follow the
# QEMU firmware metadata specification to automatically locate
# firmware images. See docs/interop/firmware.json in the QEMU
# source tree. These metadata files are distributed alongside any
# firmware images intended for use with QEMU.
--
# however, have different variables store. Therefore the nvram is
# a list of strings when a single item is in form of:
#   ${PATH_TO_UEFI_FW}:${PATH_TO_UEFI_VARS}.
# Later, when libvirt creates per domain variable store, this list is
# searched for the master image. The UEFI firmware can be called
# differently for different guest architectures. For instance, it's OVMF
# for x86_64 and i686, but it's AAVMF for aarch64. The libvirt default
--
#nvram = [
#   "/usr/share/OVMF/OVMF_CODE.fd:/usr/share/OVMF/OVMF_VARS.fd",
#   "/usr/share/OVMF/OVMF_CODE.secboot.fd:/usr/share/OVMF/OVMF_VARS.fd",
#   "/usr/share/AAVMF/AAVMF_CODE.fd:/usr/share/AAVMF/AAVMF_VARS.fd",
#   "/usr/share/AAVMF/AAVMF32_CODE.fd:/usr/share/AAVMF/AAVMF32_VARS.fd",
#   "/usr/share/OVMF/OVMF_CODE.ms.fd:/usr/share/OVMF/OVMF_VARS.ms.fd"
#]

Jeff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20250908/071ed960/attachment.html>