mirror of
https://gitlab.com/libvirt/libvirt.git
synced 2024-12-22 21:55:25 +00:00
conf: Don't explicitly set the secure-boot feature
Now that we're adding information obtained from the firmware descriptor to the domain XML, this will happen automatically whenever a firmware that has the enrolled-keys feature ends up being selected. Signed-off-by: Andrea Bolognani <abologna@redhat.com> Reviewed-by: Michal Privoznik <mprivozn@redhat.com>
This commit is contained in:
parent
24ad99d76d
commit
6d0d416f41
@ -101,12 +101,6 @@ virDomainDefPostParseOs(virDomainDef *def)
|
||||
_("firmware feature 'enrolled-keys' cannot be enabled when firmware feature 'secure-boot' is disabled"));
|
||||
return -1;
|
||||
}
|
||||
|
||||
/* For all non-broken firmware builds, enrolled-keys implies
|
||||
* secure-boot, and having the Secure Boot keys in the NVRAM file
|
||||
* when the firmware doesn't support the Secure Boot feature doesn't
|
||||
* make sense anyway. Reflect this fact explicitly in the XML */
|
||||
def->os.firmwareFeatures[VIR_DOMAIN_OS_DEF_FIRMWARE_FEATURE_SECURE_BOOT] = VIR_TRISTATE_BOOL_YES;
|
||||
}
|
||||
|
||||
if (!def->os.loader)
|
||||
|
Loading…
Reference in New Issue
Block a user