Comment 7 for bug 2004618

Hello Dann,

It's indeed quite a weird situation. I've looked at how different distros handled this:

Centos-stream is only shipping 4m images (no suffix), so it's not affected.

Fedora is shipping 4m images in a different folder with the exact same file names, so it's not affected.

Arch Linux provides 4m images, and advertises the 4m image and 2m image together, 4M image's name does not match the pattern but 2M's does, so while it does not use the image intended by the pkg maintainer, it uses the correct kind of image (secure boot capable, but not enforced).

Debian Bullseye/Ubuntu Jammy advertises only the 4m images, and the names do not match the pattern, so virt-install is using the incorrect kind of image by default.

I think the safest and hassle-free way forward for Focal would be:

- create /usr/share/OVMF/4M sub-folder
- create symlinks for 4M images, e.g. /usr/share/OVMF/4M/OVMF_CODE.fd -> ../OVMF_CODE_4M.fd
- update fw descriptor to refer to symlinks instead

For Jammy and any future series, I think we already caused an unintended regression between Focal->Jammy but nobody has reported it (yet). So, IMO we should be better off correcting it.