v5.0.2 (Beta)

[osy]

Highlights

• Improved graphics acceleration for Linux: Vulkan 1.3 is now supported on Linux guests with VirtIO Venus drivers in Mesa. OpenGL 4.1 is supported with the new Apple Core OpenGL backend (macOS only).

Known Issues

• (macOS) Apple CoreGL backend does not support Vulkan.
• KosmicKrisp is provided as a WIP but the current upstream build is incomplete so MoltenVK is the recommended driver
• Linux desktop rendering in Vulkan does not work due to lack of support for indirect draws for geometry shaders. Please configure your guest to use the older VirGL Gallium driver.

Changes (v5.0.2)

• Environment variables are now logged when debug log is enabled
• Fixed a regression in GL acceleration where desktop might not render correctly (Black screen in KDE/Plasma Wayland #7626)
• Added geometry shaders support to MoltenVK to enable DXVK (thanks @Anducalliew433) (Support DXVK #7575)
• (iOS) Fixed an issue where EAGL backend boots into a black screen (Enabling GPU acceleration with the renderer backend set to OpenGL (with Vulkan disabled) when starting Ubuntu 20.04 results in a black screen and prevents normal display. #7587)
• (iOS) Fixed a crash on iOS 15 due to incompatible symbols (Crash on iOS 15 when trying to start with Metal rendering enabled #7593)
• (iOS) Fixed verbose logging for graphics backend
• (iOS) Fixed a crash when GL is enabled due to missing support for glDrawElementsInstancedBaseVertex (iOS 15: No provider of glDrawElementsInstancedBaseVertex found #7596)
• (macOS) Fixed an issue when after resizing a window if the guest outputs a different resolution size, the wrong texture resolution is used leading to misaligned cursor and warped graphics (Full screen scaling of guest seems incorrect #5781)
• (macOS) Fixed an issue where the window resizes to 0x0 when native scaling is enabled

Changes (v5.0.1)

• CocoaSpice: Reworked Metal renderer to be faster and have lower latency
• Fixed an issue where a BIOS file with a comma in the filename will fail to load
• Default FPS will now be the maximum refresh rate of the display on macOS and iPadOS (iPhone with ProMotion will still have 60Hz as the default rate but can be overridden to 120Hz through settings)
• (macOS) Fixed issue causing HV_UNSUPPORTED on startup with Vulkan enabled (5.0.0. beta wont start any VMs: HV_UNSUPPORTED #7579)
• (iOS) Fixed resolution issue on external displays (iPad Pro External Monitor Display Issue with Windows 11 Virtual Machine #6040)
• (iOS) Pinch to zoom will turn off automatically updating zoom from the guest (until reset with the resize button)
• (iOS) Fixed external display menu not updating
• (iOS) Fixed incorrect scale on external displays and connecting an external display will now automatically scale to fit
• (iOS) Fixed an issue where powering off the VM will show the home screen but not terminate UTM in the background

Changes (v5.0.0)

• Add Venus support for Vulkan (Explore Venus + MoltenVK for GPU acceleration #4551)
• Add Apple Core OpenGL support for OpenGL 4.1 (OpenGL 3.3 with GPU acceleration? #4285) (thanks @startergo)

Issues

Please check the full list on Github and help report any bug you find that is not listed.

Installation

• iOS
• macOS

File	Description	Installation	JIT	Hypervisor	USB
UTM.deb	Jailbroken iOS version	Open in Cydia, dpkg, or Sileo	Yes	Yes(1)	Yes
UTM.dmg	macOS version	Mounting and copying UTM.app to /Applications	Yes	Yes	Yes
UTM.ipa	Non-jailbroken iOS version (sideloading)	AltStore, etc (see guide)	Yes(2)	No	No
UTM-HV.ipa	Non-jailbroken iOS version (TrollStore)	TrollStore	Yes	Yes(1)	Yes
UTM-SE.ipa	Non-jailbroken iOS version (sideloading)	AltStore, enterprise signing, etc	No	No	No
UTM-Remote.ipa	Remote client	Any	No	No	No

1. Hypervisor on iOS requires an M1 iPad or newer.
2. Enabling JIT may require a separate JIT enabler such as Jitterbug or Jitstreamer.

---

This discussion was created from the release v5.0.2 (Beta).

[startergo]

Angle-->Metal is still quirky, better than before.

The other 2 display renderers are OK in Wayland.

[osy]

I see that too but it's the same as 4.7.4 so I didn't bother looking more into it.

[startergo]

I Have the same exact glitch on my windows Qemu binary with Intel(R) Iris(R) Xe Graphics running in gl=es mode. Also same OpenGL2.1 cap.

qemu-system-x86_64.exe: warning: Ignoring request for interrupt vector 0
gl_version 30 - es profile enabled
host GL strings: vendor=Google Inc. (Intel) renderer=ANGLE (Intel, Intel(R) Iris(R) Xe Graphics (0x00009A49) Direct3D11 vs_5_0 ps_5_0, D3D11-32.0.101.7085) version=OpenGL ES 3.0 (ANGLE 2.1.27286 git hash: cbc4f074126e) glsl=OpenGL ES GLSL ES 3.00 (ANGLE 2.1.27286 git hash: cbc4f074126e)
host GL mode: gles=1 use_gles=1 use_core_profile=1 gl_ver=30
host GL features: gles31_compat=0 texture_storage=1 storage_multisample=0 gles_khr_robustness=1
GLSL feature level 130

Intel UHD Graphics 630 (i7-9750H, 2019) graphics has no such glitch. The same machine has T2000 discrete hybrid graphics, but it is not used in Qemu.
https://github.com/startergo/qemu-virgl-winhost/actions/runs/24616780073

gl=on mode is running perfectly with 4.3 OpenGL Desktop

[taoeffect]

Hi, for Fedora, how do we do this?

Linux desktop rendering in Vulkan does not work due to lack of support for indirect draws for geometry shaders. Please configure your guest to use the older VirGL Gallium driver.

[taoeffect]

Sorry for the confusion. I'm doing a few things at once:

• I'm testing out the latest version of UTM to see if I can use it
• I'm checking to see if it's possible to run Zed under it (which requires Vulkan) (GPU)
• I'm checking to see if it has graphics hardware acceleration of any kind (GPU)
• I'm checking to see if it's usable performance wise (CPU)

UTM has a very large number of options. This makes trying it out difficult, because you have to go through a combination of checkboxes and the various combinations quickly explodes. This is made all the worse if you're like me, and don't know what you're doing.

I've discovered that I can get graphics working reasonably by using the Use Apple Virtualization checkbox.

Without it, it seems impossible to run Fedora under QEMU, but perhaps I just haven't figured out the magic combination of options to select.

The only way I seem to be able to get graphics working is with Use Apple Virtualization, but then the problem becomes the maxed-out constant CPU usage, so I was inquiring about that too.

[taoeffect]

FYI, this is what I get when trying to boot it without using Apple Virtualization (both with OpenGL accel on and off):

Note: the difference is that without OpenGL acceleration the Grub screen renders fast. With it, it renders at a snail's pace (close to unusable).

So my only hope seems to be to use the experimental Apple Virtualization, but that has the maxed-out CPU issue.

[osy]

Other than grub issue (which will be fixed next version), what other differences have you observed compared to v4.7.5? It's still unclear to me what you're reporting is specific to this beta release.

[taoeffect]

The last time I tried UTM was a long time ago. I didn't try v4.7.5, so I don't know the answer to your question. I was hoping I could use this to run Fedora is all.

[osy]

I see, the purpose of the beta is to test new features so I thought you were talking about something new that broke

[yusefnapora]

Hi, I've been playing about a bit with the 5.0.2 beta and wanted to report that I was able to use the Apple Core GL backend, which glxinfo reported as supporting GL 4.1, and which generally seemed to work quite well. I also tried both of the Vulkan backends, but although vulkaninfo in the guest OS (Fedora Kinoite 43) reported that I was using virgl and Vulkan 1.3, trying to run vkcube will lock up the VM.

I may well be doing something wrong with regard to testing the vulkan support - I'm not sure how to configure the guest to use the gallium driver. Is there a "known good" guest OS and config that I could try out?

On a slightly related note, I've been trying to build UTM and its dependencies from source and I noticed that building mesa fails with the current LLVM shipped by homebrew (22.1.2). I manually applied this header reordering commit and this one for LLVM 22 compat and was able to build it.

[sambow23]

Testing commit c245141 , I get an ERROR_OUT_OF_HOST_MEMORY error on both X11 and Wayland

[osy]

How are you testing it? Can you provide the exact guest version + link to iso?

[sambow23]

I am testing on a MacBook Neo running macOS 26.4.1 with the Universal action build from the commit. I tested both Fedora 44 and NixOS on X11 (xfce4) and Wayland (gnome). My test was running vkcube and vulkaninfo --summary which is from the vulkan-tools package on both distros

https://download.fedoraproject.org/pub/fedora/linux/releases/44/Workstation/aarch64/iso/Fedora-Workstation-Live-44-1.7.aarch64.iso

https://channels.nixos.org/nixos-25.11/latest-nixos-graphical-aarch64-linux.iso

[osy]

5c2ba3f should fix it

[sambow23]

Yep it did! Thank you for your hard work! 🙏