"Unsuitable" seems like your characterization. It is true that users who choose to launch SecureBoot guests with QEMU directly need to know to add the "disable_s3" arg, and I agree that is not ideal. For users using higher level software (vir-install/OpenStack), they'll find that this parameter is already set for them. It is also true that SecureBoot guests will inherently not support S3 - but I haven't seen any reports of users missing that feature. That said, it is worth looking into whether we'd want to switch to an IA32X64 build for future releases. Are we losing any significant support by moving to a 32-bit PEI?
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1903681 Title: 20.04 LTS's OVMF_CODE.ms.fd does not boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/edk2/+bug/1903681/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
