Can't install Fedora 43 as a VM

Ask Fedora
1

Good evening,

I have a problem while I am trying to install Fedora 43 from a live ISO. My platform is a MacBook Pro M1 (arm64) with Parallels as hypervisor. It worked fine with Fedora 36 some time ago. Now it stucks immediately at the first boot at the steps shown in the screenshot. After around 2 or 3 minutes, the emergency mode appears. BUT it seems that my ‘real’ problem is some lines before:
virtio_gpu virtiol: probe with driver virtio_gpu failed with error -22
I don’t know so much about Linux, so I’m asking here if someone can help me. :slight_smile:

(1 of 2) Job dracut-initqueue.service/start running (40s / no limit)
(1 of 2) Job dracut-initqueue.service/start running (40s / no limit)3024×1322 421 KB

(2 of 2) Job dev-mapper-live|x2drw.device/start running (31s / 50min)
(2 of 2) Job dev-mapper-live|x2drw.device/start running (31s / 50min)3024×1322 422 KB

2

Have you tried booting the Live ISO with basic graphics mode? Select “Troubleshooting —>” from the GRUB boot menu, then select “Start Fedora Workstation-Live in basic graphics mode””

3

I was using parallels until utm worked for Fedora. See https://docs.getutm.app/
I recall parallels support for new linux kernels sometimes lagged a bit.
Utm runs f43 well for me on macOs

4

As another option, F43 has been running fine for me using VMware Fusion on Apple Silicon Macs. Latest aarch64 kernel (6.17.12) works fine.

5

Running Fedora under UTM on Macs here as well, using Apple Virtualization as hypervisor. Working great, including an M1 iMac.

6

Thank you for all the answers. After reading them all, I think that my Hypervisor (Parallels Desktop 18) might be the problem, because it seems to work with UTM or VMware.
I‘ll contact the Parallels support aswell, but maybe they’ve fixed it already with Parallels Desktop 26.

1 Like
7

Yes, I tried this way, but I got the same problem. Maybe - after reading the other answers - my hypervisor could be the problem, I think.

8

The error code from the virtual GPU driver is -22, which is EINVAL internally. Invalid argument /unsupported/invalid/etc.

As such, I’d say the issue was almost certainly the virtual GPU in Parallels 18. Upgrade if you can, and you’ll possibly find it the issue is resolved.