Virtual Machines will not start after last tumbleweed upgrade

English Virtualization
,
1

After the last Tumbleweed upgrade to today’s 20250328 none of my qemu Virtual Machines boot anymore.

When I start them up they hung up in a perpetual black screen and working 100% of the CPU, but absolutely nothing else happens. No console, no image, no error message. I usually manage the VMs with virt-man, but I also tried virt-viewer and qemu cli but nothing happened…

Anyone else with the same issue?

1 Like
2

Yes, same. No idea why.

1 Like
3

Good to know it’s not JUST me. I saw another thread pop up later today.

1 Like
4

I have the same issue with my Win11 installation, the TW installation runs fine. The issue is with the update of qemu-ovmf-x86_64 to version 202502. Reverting back to the previous version fixes the issue. There is probably a re-install needed with the latest update.

4 Likes
5 
zypper in -f https://download.opensuse.org/history/20250326/tumbleweed/repo/oss/noarch/qemu-ovmf-x86_64-202411-1.2.noarch.rpm

zypper al qemu-ovmf-x86_64

I see this bug report: https://bugzilla.opensuse.org/show_bug.cgi?id=1240300

5 Likes
6

I was able to rescue my Win11 installation by changing the following lines in etc/libvirt/win11.xml
from

    <loader readonly='yes' secure='yes' type='pflash'>/usr/share/qemu/ovmf-x86_64-smm-ms-code.bin</loader>
    <nvram template='/usr/share/qemu/ovmf-x86_64-smm-ms-vars.bin'>/var/lib/libvirt/qemu/nvram/win11_VARS.fd</nvram>

to

    <loader readonly='yes' type='pflash' format='raw'>/usr/share/qemu/ovmf-x86_64-ms-4m-code.bin</loader>
    <nvram template='/usr/share/qemu/ovmf-x86_64-ms-4m-vars.bin' templateFormat='raw' format='raw'>/var/lib/libvirt/qemu/nvram/win11_VARS.fd</nvram>

Now, it works with the update of qemu-ovmf-x86_64.
My TW installation is based on a bios installation and not an UEFI installation and that is probably the reason why it has not been affected.

1 Like
7

I did the same and I can confirm that after reverting to tumbleweed 20250325 and ovmf 202411-1.2 the VMs work normally again.

I set “qemu-ovmf-x86_64 = 202411-1.2” on hold, upgraded TW again to 20250328 and still everything works fine!

So, now just wait for a fix.

1 Like
8

Same problem here.
For me switching the KVM Chipset from Q35 to i440FX also works as a workaround even with the latest ovmf version and UEFI boot. Alternatively, switching to BIOS boot instead of UEFI also works for me. Only the combination Q35 Chipset + UEFI boot, which unfortunately is the default, is broken for me.

9

This information belongs to the bug report.

10

I just added it to the bug report.

1 Like
11

Thank you, I have chosen another OMVF, the issue has been resolved

12

I can confirm that QEMU/KVM is not working on Tumbleweed 20250329.
Should I wait for update of qemu-ovmf-x86_64 202502-1.1?

13

You can choose one of the intermediate solutions from the thread or bugreport. Or you can wait for a fix. It is up to you…

14

Another thing that works is:

  1. Open YaST Filesystem Snapshots.
  2. Create a new snapshot of the current system state (in case you mess up).
  3. Find the snapshot that changed a bunch of files matching the pattern /usr/share/qemu/ovmf-x86_64-*.bin. For me this snapshot was dated 2025-03-28.
  4. Select that snapshot and press “Show changes”.
  5. Browse to the above files in the list of changes and select them.
  6. Select those files and click “Restore selected”.
  7. Optionally, take another snapshot.

After this my Windows 11 VM boots again. The files won’t match the contents of the package version that the package manager thinks is installed, so there’s some inconsistency, but I don’t think it will matter because these files should be overwritten again with new versions when an updated (hopefully fixed) package is released. And if they get overwritten again with broken versions you can just repeat the above process.

1 Like
15

Thank you snepo. This is the best solution for me. It was so easy. VM works again.

1 Like
16

Hi All, for those that waited, a fix is on the way… https://build.opensuse.org/requests/1267013/changes

2 Likes
17

This is still not working for me. Should I be patient or is the fix complete and I need to be trouble shooting for a different cause?

18

@rgietzen It looks like it’s still in staging, next snapshot, keep an eye out for the 2.1 version…
https://build.opensuse.org/projects/openSUSE:Factory/packages/ovmf/repositories/standard/binaries

1 Like
19

It looks like the 2.1 updates are out. I’ve installed them, restarted and verified, but I cannot get into my Virtualbox Windows account. Should I start a new topic? Or can someone help me troubleshoot here?

20

@rgietzen Your using the qemu backend, if not that’s likely a different issue specific to virtualbox.