You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
EMU exited from an error: GL_ARB_clear_texture #5749
After i upgraded macos ventura to macos Sonoma 14.0 after booting the kali linux and showing this error message EMU exited from an error: GL_ARB_clear_texture
Configuration
UTM Version: 4.3.5
macOS Version: Sonoma 14.0
Mac Chip (Intel, M1, ...): M2
Reacted by 3uzbcqje, Reinis Adovičs / kroko, Jerry Jones, Ilia Dmitriev, Suraj, Denis Yurashku, Arif Badar, Ivin Alex, Luke Chambers, Juan Pablo and 14 more
Behavior: After running apt get update and installing all updates, Kali 2023 boots to login, but after entering login creds and hitting enter, VM crashes, and UTM dialog appears with message "QEMU exited from an error: GL_ARB_clear_texture"
Configuration
UTM Version: 4.3.5
macOS Version: Ventura 13.6
Mac Chip (Intel, M1, ...): M1 (13 inch M1 Macbook Pro 2020)
Debug Log attached, but it does not appear to give much helpful information
That's my suspicion as well. Kali VM runs okay after initial install until I apt update. After rebooting after apt update it exhibits this behavior. Seems like something is up with a package in Kali.
Just to chime in. I'm also seeing this error with Arch Linux on Sonoma.
Using KDE Plasma X11 session, it crashes as soon as I adjust display resolution.
Using KDE Plasma Wayland session, changing resolution works fine, but it crashes when I launch Vivaldi browser?! (Edit: Firefox as well.)
Anyway here's my debug.log
Problem looks to be this:
2023-10-03 21:19:40,346 DEBUG (null)-/Users/runner/Library/Developer/Xcode/DerivedData/UTM-gnwjeapbifchcjczzvitjgckdhnq/SourcePackages/checkouts/CocoaSpice/Sources/CocoaSpice/CSDisplay.m:207 [CocoaSpice] cs_gl_draw
No provider of glClearTexSubImageEXT found. Requires one of:
GL_EXT_clear_texture
Desktop OpenGL 4.4
GL_ARB_clear_texture
As a workaround, I've changed my Display from "virtio-gpu-gl-pci" to "virtio-gpu-pci"... I'm functional, but getting GPU acceleration back would be nice...
Reacted by Partha Guha Roy, Ralph Plawetzki, David Boyd and Ben Davis
Thanks, I think I'm hitting multiple issues - but the UI not working is the first one, I can still SSH in at that point, and use the Qemu console, recently I noticed that at some point after that the Qemu console stops responding and I can't SSH in any more, at all so it probably is frozen.
Anyway, will jump off this now, cheers for the clarification.
It would be great if there was a way to debug further and see the difference is when X is used vs Wayland. It may be down to IntelliJ rendering differently when on X vs Wayland, and then one of those is hitting this black screen bug.
I guess the black screen is somewhere between Qemu, and ANGLE ?
@tpasternak Xwayland support with virgl has always been busted, it's not new with this ticket. I say Xwayland because the only programs I see that exhibit this behaviour are ones that are native X apps; native Wayland apps seem to work fine.
In case it wasn't clear to anyone else, you can disable GPU acceleration by switching the Emulated Display Card from virtio-gpu-gl-pci to virtio-ramfb. The actual checkbox for "GPU Acceleration Supported" can't be unchecked so you need to change the selected device.
I was trying to run Fedora 39 Silverblue.
Reacted by Bart Louwers and Zimmermann "Hirasawa" Travis
After i upgraded macos ventura to macos Sonoma 14.0 after booting the kali linux and showing this error message EMU exited from an error: GL_ARB_clear_texture
Activity
zuzzurro commentedon Sep 28, 2023
Same here, but only after also upgrading to Fedora 39 beta (I'm pretty sure I used Fedora 38 after the Sonoma upgrade).
osy commentedon Sep 29, 2023
Can either or both of your provide a debug.log?
azagulyaev commentedon Sep 29, 2023
Maybe this can help:
Once I try to change the Display resolution, I got in my debug log:
2023-09-29 23:50:18.984 UTM[34759:2987438] Debug JSON recieved <- { data = { offset = 1; "qom-path" = "/machine/unattached/device[7]"; }; event = "RTC_CHANGE"; timestamp = { microseconds = 984191; seconds = 1696020618; }; } 2023-09-29 23:50:22.600 UTM[34759:2988263] Debug JSON send -> { execute = "query-mice"; } 2023-09-29 23:50:22.603 UTM[34759:2988264] Debug JSON recieved <- { return = ( { absolute = 0; current = 0; index = 2; name = "QEMU HID Mouse"; }, { absolute = 1; current = 1; index = 1; name = "QEMU HID Tablet"; } ); } 2023-09-29 23:50:22.605 UTM[34759:2988263] found index:1 absolute:1 2023-09-29 23:50:22.605 UTM[34759:2988263] Debug JSON send -> { arguments = { "command-line" = "mouse_set 1"; }; execute = "human-monitor-command"; } 2023-09-29 23:50:22.606 UTM[34759:2988264] Debug JSON recieved <- { return = ""; } ** Message: 23:50:43.337: main channel: closed 2023-09-29 23:50:43.338 UTM[34759:2987438] Failed to connect to SPICE: (null) 2023-09-29 23:50:43.338 UTM[34759:2987438] Stop operation timeout or force quit 2023-09-29 23:50:43.338 UTM[34759:2988263] Debug JSON send -> { execute = quit; } 2023-09-29 23:50:43.338 UTM[34759:2987438] Exit operation timeout or force quit 2023-09-29 23:50:43.338 UTM[34759:2988263] RPC: Error Domain=com.utmapp.utm Code=-1 "Port is not connected." UserInfo={NSLocalizedDescription=Port is not connected.}osy commentedon Sep 29, 2023
I don't know how that's related to the issue reported here at all?
azagulyaev commentedon Sep 29, 2023
Issue named appears at the screen and VM stops working
osy commentedon Sep 29, 2023
I see, please post the entire debug.log
eccramer commentedon Sep 30, 2023
I am having this problem as well.
Behavior: After running
apt get updateand installing all updates, Kali 2023 boots to login, but after entering login creds and hitting enter, VM crashes, and UTM dialog appears with message "QEMU exited from an error: GL_ARB_clear_texture"Configuration
Debug Log attached, but it does not appear to give much helpful information
debug.log
osy commentedon Sep 30, 2023
I think this is a driver issue on Kali's side. As a workaround you can disable GPU acceleration while this is getting figured out.
eccramer commentedon Sep 30, 2023
That's my suspicion as well. Kali VM runs okay after initial install until I apt update. After rebooting after apt update it exhibits this behavior. Seems like something is up with a package in Kali.
eccramer commentedon Oct 1, 2023
I was able to
sudo apt updatewithout breaking UTM by running the following commandI'll have to unhold those packages later, but for now this provides a working and fairly up-to-date Kali install in UTM.
wzxu commentedon Oct 3, 2023
Just to chime in. I'm also seeing this error with Arch Linux on Sonoma.
Using KDE Plasma X11 session, it crashes as soon as I adjust display resolution.
Using KDE Plasma Wayland session, changing resolution works fine, but it crashes when I launch Vivaldi browser?! (Edit: Firefox as well.)
Anyway here's my debug.log
Problem looks to be this:
3uzbcqje commentedon Oct 4, 2023
I just had this issue when I upgraded some packages in Arch Linux on UTM. I'm pretty sure it was one of these bad boys:
As a workaround, I've changed my Display from "virtio-gpu-gl-pci" to "virtio-gpu-pci"... I'm functional, but getting GPU acceleration back would be nice...
24 remaining items
cky commentedon Jan 7, 2024
@stuaxo If it's a freeze, then this isn't the issue. This issue results in an outright crash of the QEMU instance, not merely a freeze.
cky commentedon Jan 7, 2024
@tpasternak Are you using Wayland mode or X mode? I am using IntelliJ on Fedora 39 just fine.
stuaxo commentedon Jan 8, 2024
Thanks, I think I'm hitting multiple issues - but the UI not working is the first one, I can still SSH in at that point, and use the Qemu console, recently I noticed that at some point after that the Qemu console stops responding and I can't SSH in any more, at all so it probably is frozen.
Anyway, will jump off this now, cheers for the clarification.
tpasternak commentedon Jan 9, 2024
@cky the default one, in general it works, but some apps (IntelliJ) don't
cky commentedon Jan 10, 2024
@tpasternak I use Xorg mode. Maybe you can get IntelliJ to work for you in Xorg mode too?
tpasternak commentedon Jan 11, 2024
so maybe it's a wayland-only problem, but still
stuaxo commentedon Jan 11, 2024
It would be great if there was a way to debug further and see the difference is when X is used vs Wayland. It may be down to IntelliJ rendering differently when on X vs Wayland, and then one of those is hitting this black screen bug.
I guess the black screen is somewhere between Qemu, and ANGLE ?
tpasternak commentedon Jan 11, 2024
But without gpu acceleration it works ok
cky commentedon Jan 11, 2024
@tpasternak Xwayland support with virgl has always been busted, it's not new with this ticket. I say Xwayland because the only programs I see that exhibit this behaviour are ones that are native X apps; native Wayland apps seem to work fine.
tpasternak commentedon Jan 11, 2024
ok, thank you!
ajs1998 commentedon Mar 12, 2024
In case it wasn't clear to anyone else, you can disable GPU acceleration by switching the Emulated Display Card from
virtio-gpu-gl-pcitovirtio-ramfb. The actual checkbox for "GPU Acceleration Supported" can't be unchecked so you need to change the selected device.I was trying to run Fedora 39 Silverblue.
ivanfilhoz commentedon Mar 29, 2024
As per @tpasternak's comment, Fedora 39 works fine with mesa-libGL 23.3:
virtio-ramfb.23.3.x) is installed by running:virtio-gpu-gl-pci.stuaxo commentedon Apr 4, 2024
Hopefully someone will come on here and update whether this works on Ubuntu (e.g. with the oibaf PPA) as well.
mvysny commentedon Jan 15, 2025
Intellij can now run in pure Wayland mode: https://blog.jetbrains.com/platform/2024/07/wayland-support-preview-in-2024-2/ . That means that Intellij now works correctly in Ubuntu 24.04+ with virtio-gpu-gl-pci. Xwayland is still busted though: #6968
tamyr3195-create commentedon Dec 29, 2025