I upgraded ipfire from core 191 to 192, and now a VM that used to run fine will no longer start. I’m getting the following error in virt-manager:
ibvirt.libvirtError: operation failed: Unable to find 'efi' firmware that is compatible with the current configuration
2 other VMs that are set to boot as BIOS rather than EFI work fine. ovmf-2024.11-5-1 is installed in Pakfire. Logging into ipfire with ssh and attempting to start the VM with “virsh start” doesn’t work either - it throws the same error as virt-manager. Help please?
How did you have it working before, because the ovmf is new in CU192. It wasn’t available before.
Had you put an ovmf binary yourself into your IPFire?
It could be that the latest qemu update now requires a newer ovmf than the one we put in place. @arne_f extracted the ovmf binary from a debian system, so maybe that version of ovmf is older than the newer qemu requires.
I found the following link from Arch Linux having the same problem message. They report some fixes but at the moment I don’t know if these are fixes that you need to do on your qemu configuration or if there is some change needed in the qemu build or in the ovmf build. The later can’t be done by us yet as at the moment we have just taken an existing ovmf binary that debian built and then installed it in IPFire. https://bbs.archlinux.org/viewtopic.php?id=300862
Building ovmf ourselves is still on my list but it will still take some time for me to be able to get around to it.
It looks like the ovmf update from 2023.11 to 2024.11 removed the 2M firmware files and therefore there are only the 4M firmware files now.
The arch linux link mentions this notice in the ovmf update
The CSM support has been removed upstream in version 202402.
The 2MB firmware files have been removed in favor of the 4MB ones as the new default.
Virtual machine setups may need to be adapted!
The fix in the arch linux link looks to be that in your libvirt or qemu configuration you need to change the directrory link to use the files with 4M as the 2M files are no longer available in ovmf.
This link shows the locations of the various ovmf files that are installed with the 2024.11 version binary from debian.
I don’t remember exactly how I set it up. It appears my VM is not even using the ovmf package - it’s trying to load “/usr/share/qemu/edk2-x86_64-secure-code.fd”. So I’m at a loss as to why it’s failing.