From: Pavel Hrdina Date: Tue, 16 Mar 2021 12:05:08 +0000 (+0100) Subject: docs: improve description of secure attribute for loader element X-Git-Tag: v7.2.0-rc1~81 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=f47d06260b9698f705ab2c079c573f89f832e376;p=thirdparty%2Flibvirt.git docs: improve description of secure attribute for loader element 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 Reviewed-by: Kashyap Chamarthy Reviewed-by: Michal Privoznik --- diff --git a/docs/formatdomain.rst b/docs/formatdomain.rst index a2ea2690a5..70709ef946 100644 --- a/docs/formatdomain.rst +++ b/docs/formatdomain.rst @@ -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 path points to an UEFI image, ``type`` should be ``pflash``. Moreover, some 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`` 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