Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

"secure boot" not getting enabled for Chipset/Firmware Type "Q35 Chipset with UEFI SecureBoot" #912

Merged
merged 1 commit into from
Oct 4, 2024
Merged

"secure boot" not getting enabled for Chipset/Firmware Type "Q35 Chipset with UEFI SecureBoot" #912

merged 1 commit into from
Oct 4, 2024

Commits on Oct 4, 2024

  1. "secure boot" not getting enabled for Chipset/Firmware Type "Q35 Chip… 

    …set with UEFI SecureBoot".

Issue:
When VM emulator is changed to Q35 Chipset with UEFI SecureBoot from Q35 Chipset with UEFI, the NVRAM file needs to be rewritten.

Fix:
On VM update remove the previous NVRAM file.

Signed-off-by: Saksham Srivastava <[email protected]>
    @saksham-oracle @sandrobonazzola
    saksham-oracle authored and sandrobonazzola committed Oct 4, 2024
    Configuration menu
    Copy the full SHA
    84a331b View commit details
    Browse the repository at this point in the history