External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2025-02-01 17:35:17 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Document firmware format attribute

Browse Source 
Signed-off-by: Andrea Bolognani <abologna@redhat.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
This commit is contained in:
Andrea Bolognani 2023-02-14 17:38:10 +01:00
parent 44fb7659cc
commit a50fb7dada
1 changed files with 10 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
docs/formatdomain.rst
View File

@ -257,6 +257,12 @@ harddisk, cdrom, network) determining where to obtain/find the boot image.
any config changes on shutdown. The ``stateless`` flag (:since:`Since 8.6.0`)
can be used to control this behaviour, when set to ``yes`` NVRAM will never
be created.
When firmware autoselection is enabled, the ``format`` attribute can be
used to tell libvirt to only consider firmware builds that are in a
specific format. Supported values are ``raw`` and ``qcow2``.
:since:`Since 9.2.0 (QEMU only)`
``nvram``
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
@ -276,6 +282,10 @@ harddisk, cdrom, network) determining where to obtain/find the boot image.
**Note:** ``network`` backed NVRAM the variables are not instantiated from
the ``template`` and it's user's responsibility to provide a valid NVRAM image.
This element supports a ``format`` attribute, which has the same semantics
as the attribute of the same name for the ``<loader>`` element.
:since:`Since 9.2.0 (QEMU only)`
It is not valid to provide this element if the loader is marked as
stateless.