Upgrading a CentOS Stream 9 guest VM triggers the qemu shim bug
michel-slm opened this issue · comments
BEFORE SUBMITTING YOUR ISSUE, PLEASE LOOK AT THE PINNED ISSUES AND USE THE SEARCH FUNCTION TO MAKE SURE IT IS NOT ALREADY REPORTED. ALWAYS COMMENT ON AN EXISTING ISSUE INSTEAD OF MAKING A NEW ONE.
Describe the issue
I have a CentOS Stream 9 VM that was last updated in May. If I do dnf upgrade and reboot, the system is unbootable - it crashes before reaching GRUB
The behavior matches lima-vm/lima#1645 and https://gitlab.com/qemu-project/qemu/-/issues/1990
The bizarre thing is excluding kernel packages from the update does not fix the behavior - and the shim was not updated either.
Configuration
- UTM Version: 4.5.2 (need to retry on 4.5.3)
- macOS Version: 14.5
- Mac Chip (Intel, M1, ...): M3 Pro
Crash log
N/A
Debug log
For all issues related to running a VM, including crashes, you should attach a debug log. (This is unavailable for macOS-on-macOS VMs. Attach an excerpt of your system log instead.)
To get the Debug log: open UTM, and open the settings for the VM you wish to launch. Near the top of the QEMU page is Debug Log. Turn it on and save the VM. After you experience the issue, open the VM settings again and select Export Log... and attach it here.
Will attach once I repro
Upload VM
If your issue is related to a specific VM, please upload the config.plist from your VM's .utm directory. To get this, right-click the VM in UTM and choose "Show in Finder". Then right-click the selected file in Finder and choose "Show Package Contents". The config.plist file is now visible. Right-click it and choose "Compress". Attach the resulting config.plist.zip file here.
You can upload the entire .utm if needed, but note this includes your VM's drive image and may contain personal data. Since Github has an attachment size limit, you may want to upload to another service such as Google Drive. Link it here.
I'm also hitting this with a fedora VM, same behavior on 39 and 40, or rather I think it's the same issue --
in my case, even booting grubx64.efi directly doesn't work, as the grubx64.efi that gets built by fedora's mojo when installing updates fails with the Synchronous Exception error.
My workaround is to use a copy of grubx64.efi from the cd, placing it at /boot/efi/efi/fedora/works.efi and adding that as a boot entry in the ovmf boot manager
Not sure if this is related, I just installed Rocky Linux 9.4 from DVD ISO, ran sudo yum -y updated and rebooted the vm. The VM couldn't start up after that. Keep getting error Synchronous Exception at <some address>
Fixed switching to Apple Virtualization from QEMU.