Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rancher Desktop no longer works on openSUSE Tumbleweed #7463

Open
jandubois opened this issue Sep 12, 2024 · 1 comment
Open

Rancher Desktop no longer works on openSUSE Tumbleweed #7463

jandubois opened this issue Sep 12, 2024 · 1 comment
Labels
Milestone

Comments

@jandubois
Copy link
Member

It is broken by an update to qemu-ovmf-x86_64 (see https://bugzilla.suse.com/show_bug.cgi?id=1230291).

Workarounds:

  • Install an older version of qemu-ovmf-x86_64 if you can still find one
  • Use the AppImage release of Rancher Desktop which comes bundled with its own copy of QEMU
  • Wait for the qemu-ovmf-x86_64 package to be fixed by openSUSE

There 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.

@jandubois jandubois added kind/bug Something isn't working platform/linux labels Sep 12, 2024
@jandubois jandubois modified the milestones: 1.17, 1.16 Sep 12, 2024
@jandubois jandubois modified the milestones: 1.16, 1.17 Sep 19, 2024
@mook-as mook-as changed the title Rancher Desktop no longer works on openSUSE Rancher Desktop no longer works on openSUSE Tumbleweed Sep 20, 2024
@mook-as
Copy link
Contributor

mook-as commented Sep 20, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants