[Bug 2022312] Re: Adding IA32 to X64 pkg, because secure boot is not working on Focal
Trent Lloyd
2022312 at bugs.launchpad.net
Tue Jun 13 08:57:50 UTC 2023
I cannot find any mention in any openstack repo of that suspend-to-mem
property. Not sure if I'm missing something but perhaps OpenStack
actually doesn't currently support this option?
I am surprised by that given how many people seem to have run into this
issue. Has everyone else just fixed their edk2 build?
Secure Boot was definitely working at some point, maybe bionic? It's not
clear to me what changed to break this in focal. Was it a change in edk2
itself or?
Is there any possibility it's safe to SRU this edk2 change?
--
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/2022312
Title:
Adding IA32 to X64 pkg, because secure boot is not working on Focal
Status in edk2 package in Ubuntu:
Fix Released
Status in nova package in Ubuntu:
Invalid
Status in edk2 source package in Focal:
Won't Fix
Status in nova source package in Focal:
Incomplete
Status in edk2 source package in Jammy:
Fix Released
Status in nova source package in Jammy:
Invalid
Bug description:
[Impact]
In Focal, secureboot is not working ( black screen right after
instance is started )
[Test Case]
1. In focal, create instance, and enable secureboot
2. start instance.
3. you just can see only blackscreen.
[Where problems could occur]
Secureboot may have issue.
[Others]
For Jammy, it is ok
instance xml
- https://pastebin.ubuntu.com/p/MnK6nx3vwy/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/2022312/+subscriptions
More information about the Ubuntu-openstack-bugs
mailing list