-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
VM with Virto-GPU-GL display crashes in iPadOS 15 #3126
Comments
I had to update to iPad 15 also and found the same thing, I got black screens. I changed mine to VGA (the generic one) and my VMs boot and I can use them. It’s a smidgin slower, but still useable. The supported virt-vga-gl, like the original poster was working great in iOS 14.2 (my last iOS update I was running to keep. JIT) |
Bump this one. Same situation, on a Ipad Pro 2021 M1 trying to run any 32/64bit distro on UTM with JIT enabled. Switching to Virtio-ramfb-GL causes the display to flash and the iPad to just reboot |
@Sinemora10, that’s unfortunate. Not sure why I’m able to run Debian x86-64 with Virtio-ramfb-GL with JIT on my iPad Pro 2021 M1 on iOS 15 and you are not. I do get that display flash like you on other GL displays but for some reason virtio-ramfb-gl still works for me. |
I had the same issue yesterday on my 2021 M1 ipad pro ios 15 where the virtio-ramfb-gl would cause a flash then a reboot and now I went to reproduce it so I can grab the logs and it somehow just started working. I can boot into kali linux and everything seems to be working fine, I havent tried any 3d apps yet though. However, it does still flash and reboot if I try to adjust the screen resolution with xrandr. UTM.wakeups_resource-2021-09-28-000802
|
Thank you very much for your feedback! Could it be DE related then? Or perhaps it's the RAM? I see you allocated 3GB while I decided for 2GB. I will create a new VM with Debian and see if it works, and change to 3GB in the existing Xubuntu VM, then report. |
Alright, so it seems it is indeed a problem somehow related to the amount of RAM allocated. I switched to 3GB in my existing VM running x86-64 Cinnamon MATE, and it worked very well. I switched back to 2GB and iPadOS crashed as expected, causing the iPad to reboot. However, now that I've switched back to 3GB I am still experiencing the same purple flash. My iPad Pro is equipped with 8 GB or RAM |
@SugarRayLua if it is not too much trouble, could you be more specific about how much ram your ipad has and how you are enabling JIT? Thank you very much |
Sure, @Sinemora10, no trouble at all: For my regular use of UTM, I’m using: When I’m trying to push 3D graphics to the limits (e.g. playing Xonotic) I need I hope that helps. Please let me know if I can provide any further info. |
Thank you @SugarRayLua this is very helpful. One further question, if I may: what resolution have you set your display to? |
Hi, @Sinemora10. I’m set to the default 1024 x 768 resolution. |
Thank you, then that's what may be causing the problem. I checked and the VM works fine on the default res, but changing to any other causes the iPad to crash and restart. Probably related to RAM or a memory leak? A regretful regression, as on 14.8 it was possible to just set the display to any resolutions of choice, including setting up a beautiful custom 2388x1668 |
Thanks for the follow-up, @Sinemora10. I never even thought about running it at such high a resolution :-). Hopefully, when the MetalAngle backend gets more developed, Osy can switch back UTM to Metal and perhaps can get some really high performance graphics. Have a good week. |
Duplicate of #2743 |
Upgraded to iPadOS 15 and found VM with Virtio-GPU-GL accelerated graphics display driver crashes during boot (after loading Linux part of boot). Virtio-GPU-GL graphics display driver worked fine with same VM in most recent version of iPadOS 14.
However, Virtio-ramfb-GL still works fine as a graphics display driver and gives similar graphics performance so maybe a minor issue.
Configuration (required)
Debug log
Crash log
microstackshots cpu usage log
wakeups log
Upload VM
[missing]
The text was updated successfully, but these errors were encountered: