External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-12-22 05:35:25 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: formatdomain: Clarify that NVRAM template is also being autoselected

Browse Source 
The NVRAM template file may be autoselected same as the loader/firmware
image. Add a hint that this can occur and also that it doesn't
necessarily need to be from the 'qemu.conf' configured files.

Signed-off-by: Peter Krempa <pkrempa@redhat.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
Reviewed-by: Ján Tomko <jtomko@redhat.com>
This commit is contained in:
Peter Krempa 2024-08-22 17:20:32 +02:00
parent a448d4a18a
commit f90567f3a8
1 changed files with 8 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
docs/formatdomain.rst
View File

@ -268,12 +268,14 @@ harddisk, cdrom, network) determining where to obtain/find the boot image.
Some UEFI firmwares may want to use a non-volatile memory to store some
variables. In the host, this is represented as a file and the absolute path
to the file is stored in this element. Moreover, when the domain is started
up libvirt copies so called master NVRAM store file defined in ``qemu.conf``.
If needed, the ``template`` attribute can be used to per domain override map
of master NVRAM stores from the config file. Note, that for transient domains
if the NVRAM file has been created by libvirt it is left behind and it is
management application's responsibility to save and remove file (if needed to
be persistent). :since:`Since 1.2.8`
up libvirt copies so called master NVRAM store file either selected by the
firmware autoselection process or defined in ``qemu.conf``.
If needed, the ``template`` attribute can be used to override the
automatically chosen NVRAM template.
Note, that for transient domains if the NVRAM file has been created by
libvirt it is left behind and it is management application's responsibility
to save and remove file (if needed to be persistent). :since:`Since 1.2.8`
:since:`Since 8.5.0`, it's possible for the element to have ``type`` attribute
(accepts values ``file``, ``block`` and ``network``) in that case the NVRAM