[Pkg-libvirt-maintainers] Bug#764834: libvirt-daemon-system: nvramoptions

Christoph Anton Mitterer calestyo at scientia.net
Sat Oct 11 14:53:19 UTC 2014


Package: libvirt-daemon-system
Version: 1.2.9-2
Severity: normal


Hi.

As of now qemu.conf supports NVRAM options:
# Location of master nvram file
#
# When a domain is configured to use UEFI instead of standard
# BIOS it may use a separate storage for UEFI variables. If
# that's the case libvirt creates the variable store per domain
# using this master file as image. Each UEFI firmware can,
# 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.
#nvram = [ "/usr/share/OVMF/OVMF_CODE.fd:/usr/share/OVMF/OVMF_VARS.fd" ]


1) The locations of the respective Debian package’s file (ovmf)
seems to be different:
$ dpkg -L ovmf 
/usr/share/ovmf/OVMF.fd


2) With respect to the OVMF_VARS.fd I'm a bit unsure whether I
understand it correctly.
Is this just a "template" for the UEFI variables (i.e. how
the ones for a new VM are initialised)? Or is it the storage
for the variables from the VMs?
Anyway,... in the first case it seems this file should rather
go to /etc/libvirt/, and in the second case it seems it should
go to /var/lib/libvirt/

Cheers,
Chris.



More information about the Pkg-libvirt-maintainers mailing list