[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 03:26:51 UTC 2023
Christian wrote in this bug here that the edk2 fix was preferable, and that setting ICH9-LPC.disable_s3=1 by default may break more things than it fixes:
https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1903681
It's also notable that bug was raised in 2020 on focal's release so it
has been raised (and fixed) earlier than now 3 years local.
According to the above bug, the current version of the file
OVMF_CODE.ms.fd is just plainly broken in all cases. So if this patch
-only- effects OVMF_CODE.ms.fd and we can confirm that the file is not
usable in any situation, the SRU may be more acceptable.
The question remains whether we can safely SRU this change.
My suggestion is that:
(1) We know focal-yoga is broken, but we need to determine whether focal-ussuri (the openstack version that ships with focal) works. If it does work, we could consider a backport of edk2 from jammy into the openstack cloud-archive for yoga. The SRU still needs to be understood thoroughly to be safe but we potentially only affect openstack users, rather than all Ubuntu users.
(2) If focal-ussuri is broken, we probably need to look at actually
accepting this change but need some people with much more detailed
knowledge to help understand if it will be OK and help understand,
detail and test the risk of the 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