[libvirt PATCH 31/33] docs: Document firmware format attribute

Andrea Bolognani abologna at redhat.com
Wed Feb 15 10:42:28 UTC 2023


Signed-off-by: Andrea Bolognani <abologna at redhat.com>
---
 docs/formatdomain.rst | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/docs/formatdomain.rst b/docs/formatdomain.rst
index 8407bab1ba..6122f30b76 100644
--- a/docs/formatdomain.rst
+++ b/docs/formatdomain.rst
@@ -257,6 +257,11 @@ 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.1.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 +281,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.1.0 (QEMU only)`
+
    It is not valid to provide this element if the loader is marked as
    stateless.
 
-- 
2.39.1



More information about the libvir-list mailing list