External/libvirt
1
0
Fork 0
mirror of https://gitlab.com/libvirt/libvirt.git synced 2024-10-05 13:55:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: improve description of secure attribute for loader element

Browse Source 
The original text was not explaining what this attribute actually
controls and could have been interpreted as a control switch for the
Secure boot feature in firmwares.

Signed-off-by: Pavel Hrdina <phrdina@redhat.com>
Reviewed-by: Kashyap Chamarthy <kchamart@redhat.com>
Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
This commit is contained in:
Pavel Hrdina 2021-03-16 13:05:08 +01:00
parent 25d3b41e5e
commit f47d06260b
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/formatdomain.rst
View File

@ -167,7 +167,9 @@ harddisk, cdrom, network) determining where to obtain/find the boot image.
in the guest memory the file should be mapped. For instance, if the loader in the guest memory the file should be mapped. For instance, if the loader
path points to an UEFI image, ``type`` should be ``pflash``. Moreover, some path points to an UEFI image, ``type`` should be ``pflash``. Moreover, some
firmwares may implement the Secure boot feature. Attribute ``secure`` can be firmwares may implement the Secure boot feature. Attribute ``secure`` can be
used then to control it. :since:`Since 2.1.0` used to tell the hypervisor that the firmware is capable of Secure Boot feature.
It cannot be used to enable or disable the feature itself in the firmware.
:since:`Since 2.1.0`
``nvram`` ``nvram``
Some UEFI firmwares may want to use a non-volatile memory to store some 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 variables. In the host, this is represented as a file and the absolute path