You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like using /usr/share/qemu/ovmf-x86_64-4m.bin instead of /usr/share/qemu/ovmf-x86_64-4m-code.bin works (drop the -code part). Reading the readme, I think this is because the -code firmware doesn't include efivars and needs to be paired with -drive if=pflash,format=raw,unit=1,file=ovmf-x86_64-vars.bin (where it points at a file that can be modified)? I'm very unclear about this point, and it might be good to ask people who know about this stuff. But it seems like adding that (pointing to /usr/share/qemu/ovmf-x86_64-4m-vars.bin) allows the system to boot.
I think we can set the firmware if needed to use that? Not sure if it makes more sense to use the single file, or get lima to also use -vars…
It is broken by an update to
qemu-ovmf-x86_64
(see https://bugzilla.suse.com/show_bug.cgi?id=1230291).Workarounds:
qemu-ovmf-x86_64
if you can still find oneqemu-ovmf-x86_64
package to be fixed by openSUSEThere is no action item in this bug for the Rancher Desktop team; it has to be fixed upstream. This issue is purely about tracking the problem.
The text was updated successfully, but these errors were encountered: