-
Notifications
You must be signed in to change notification settings - Fork 271
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.
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
"secure boot" not getting enabled for Chipset/Firmware Type "Q35 Chipset with UEFI SecureBoot" #912
Conversation
5a8d2c4
to
c8f24cf
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See inline comments
c8f24cf
to
8af62e3
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@smelamud can you please review?
This change seems to be an addition to #887. That PR puts a new condition here: |
8af62e3
to
b41022a
Compare
b41022a
to
3d9d578
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving as patch is already out in OLVM ovirt-engine-4.5.5-1.21.el8
, tested by Oracle's QE and shipped to Oracle's customers.
3d9d578
to
40806ed
Compare
…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]>
40806ed
to
84a331b
Compare
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]