On a Mac M3, the system does not start after upgrading from Fedora 40 to 41 on UTM

Ask Fedora
1

I experienced this after upgrading Fedora 40 to 41 running on a UTM virtual machine. What is the reason for this and how can it be fixed?

2

You’re probably going to have to post some logs from the boot process, so we have something to work with. As there is no indication at all what the issue is, you’re going to have to post the entire bootlog from journalctl onto a suitable pastebin.

What does “UTM” mean?

Edit: it’s some Mac software it seems.

3

Synchronous Exception at 0x0000000XXXXXX blocking boot of both Fedora 41.
UTM is a virtual machine specifically designed for Mac.https://mac.getutm.app/

4

Try unplugging any external USB devices - CD drive, external hard drive, etc.

5

Until now, it was not necessary to do this, what is the reason that it has become necessary now on the F41? I had to disable them on the virtual machine.

6

I would imagine it’s to do with the UUID of the device within the VM getting in the way of the boot process for grub, potentially shifting devices around.

I can’t really be specific because I don’t use a Mac, I don’t have UTM and we have no boot logs to look at from a failed and a successful boot so we can’t see what the difference is.

7

Are you using Apple Virtualization or QEMU as a backend?

I am using UTM with Apple Virtualization on both an M1 Mac as well as on Intel Mac with no upgrade issues from F40 to F41 (Workstation edition).

However, given that for aarch64 systems we can boot directly from the downloaded raw images, I sometimes prefer taking the latest release and just restoring the /home folder, than system upgrading.

8

I’m using QEMU virtualization on an M+ Mac within UTM. I also read about this on GITHUB, the solution for me was to disable the CD ROM drive on the virtual machine.
Thanks for the idea, I haven’t tried raw yet. Apart from that, I also have a full Fedora installation on an external USB drive on my Intel machine, which I also use for testing purposes.

9

I read exactly this on github, that this phenomenon has been observed since the last grub update.

10

I can only recommend Apple Virtualization as backend for UTM. I am using it on both an M1 Mac and a 2019 Intel MBP. It provides Retina display support without affecting performance, while QEMU seems to be struggling with high resolutions.

There is no suspend functionality of the VM, this is probably one of the reasons they say it’s still experimental.

11

I didn’t think to use Apple virtualization, but it’s worth a try. Thanks.

1 Like