It seems that Win10 guest VMs are now choking after Microsoft did …something to reject the current OVMF firmware.

This entire discussion, pretty much, is way over my head:

https://github.com/tianocore/edk2/discussions/3221

As best as I can make things out:

There is an alternative OVMF firware called "4M" firmware that works.

The edk2-ovmf package contains files named OVMF_CODE.secboot.fd and OVMF_VARS.secboot.fd which are blacklisted by Microsoft.

Debian and other distributions apparently ship "OVMF_CODE_4M" and "OVMF_VARS_4M" firmware which is still good. People have reported success extracting those images and repointing their qemu VM configuration to them.

I don't grasp the underlying issue well enough to be able to file something intelligent in Bugzilla, in order to update Fedora packaging. I'm hoping that someone else here has enough domain knowledge to create a bug that points the ed2k packagers in the right direction. I tried looking at the SRPM, and I did not see anything in there that I could understand.

Attachment: pgprUVl9CKPaN.pgp
Description: PGP signature

_______________________________________________
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
Fedora Code of Conduct: 
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: 
https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to