Re: Solution: OVMF 4M-based VMs broken after updating to F39

2023-11-10 Thread Jonathan Billings
On Nov 10, 2023, at 17:03, Sam Varshavchik wrote: > > I had an EFI VM that was configured to use > /usr/share/edk2/ovmf-4m/OVMF_CODE.secboot.fd as its bootloader in F38. > > The edk2-ovmf package in F39 no longer installs it. This results in an error > message starting any VM that uses OVMF 4M

Solution: OVMF 4M-based VMs broken after updating to F39

2023-11-10 Thread Sam Varshavchik
I had an EFI VM that was configured to use /usr/share/edk2/ovmf-4m/OVMF_CODE.secboot.fd as its bootloader in F38. The edk2-ovmf package in F39 no longer installs it. This results in an error message starting any VM that uses OVMF 4M images. The /usr/share/edk2/ovmf-4m directory no longer exis