iOS 14.2 JIT support not working on A11 devices or older

[brunocastello]

Just updated my iPad Pro 2nd gen 12.9" to iOS 14.2. Then I proceeded to re-sign the UTM.ipa with iOS App Signer, to be able to install using my own paid developer certificate. All clear, then installed the UTM.ipa through Xcode 12.1 on iPad Pro.

App was installed perfectly so I moved my old VMs inside to run. But none of my machines are loading up (MSDOS 6.22/Windows 3.1, Windows 95, macOS 9.2 and OS X 10.5 Leopard) because when I hit run, UTM crashes back to iPadOS home screen. I was able to go a bit further when I chose to bypass configuration and manually specify arguments, but then UTM would crash again complaining about error: "Could not allocate dynamic translator buffer". I hit OK, then UTM crashes again back to iPadOS home screen. Nightmare. I am unable to run any VM.

[ThatStella7922]

You said “ from previous UTM builds” but didn’t mention trying VMs created with the current build. Have you tried creating a new empty x86 VM and seeing if you can get to a bootloader prompt?

[brunocastello]

You said “ from previous UTM builds” but didn’t mention trying VMs created with the current build. Have you tried creating a new empty x86 VM and seeing if you can get to a bootloader prompt?

I get the same behavior from new VMs.

[osy]

Please post a crash log.

Could not allocate dynamic translator buffer

Does this happen always? Including with brand newly created VM?

[brunocastello]

Please post a crash log.

Could not allocate dynamic translator buffer

Does this happen always? Including with brand newly created VM?

That error only happens when I chose to use custom QEMU arguments. When I chose not to, UTM simply crashes to desktop.

[osy]

Okay please post a crash log of when you try to open a newly created VM

[brunocastello]

Here's the crash log. I am downloading Xcode 12.2 Release Candidate to try again, it was probably a codesigning error? I never had such issues with previous builds. I've renamed the file from .ips to .txt because GitHub wouldnt let me upload it.

UTM-2020-11-05-215137.txt

Edit: I'll also try out one of the pre-made linux VMs from the vm-downloads repo to test again.

[osy]

Identifier: com.swconsultores.iSH

Not sure if that may have caused any issues. Any reason why you changed the bundle Identifier?

Also can you confirm that you’re signing with a development certificate and not an enterprise or distribution certificate?

[brunocastello]

A test with the Debian ARM VM from the vm-downloads repo showed the same behavior, except that with custom QEMU arguments, I'd be stopped at a black screen with a spinning wheel.

Identifier: com.swconsultores.iSH

Not sure if that may have caused any issues. Any reason why you changed the bundle Identifier?

No, but I have used it in the past before with no issues. I have two provisioning files, I can try again to re-sign on iOS App Signer. One provisioning file has a custom bundle identifier, the other doesn't. I'll try re-signing again with the other one, but I've tried both today too. Two days ago I just used them to re-sign some apps with no issues.

Also can you confirm that you’re signing with a development certificate and not an enterprise or distribution certificate?

It's a development certificate, yes. I do not have an enterprise or distribution certificate.

I'll try again re-signing, if it fails, soon Xcode 12.2 RC download will finish so I can try again.

[brunocastello]

I mentioned a possible codesigning problem before, because there there was an warning on xcode about iOS 14.2 and Xcode 12.1, saying that I'd have to update Xcode. The warning did not stop me from sideloading the app, though. In 10 or 20 minutes after the download completes, we'll find out.

[osy]

I’ve noticed that you’re running 18B92 I hope nothing changed from 18B91 that was the RC...

[brunocastello]

I’ve noticed that you’re running 18B92 I hope nothing changed from 18B91 that was the RC...

Yes, it's the public version. I've just tried again with my normally used provisioning file (the other you mentioned was from my dad, I've used that before though without issues too), the identifier says com.utmapp.UTM, yet same issues. Xcode 12.2 RC download finished, I'll install this new Xcode version and try again. It's probably just an issue with older Xcode version not being able to recognize a new iOS version.

[osy]

Uh oh let’s hope Apple didn’t fix this

[brunocastello]

Uh oh let’s hope Apple didn’t fix this

OK, while Xcode 12.2 RC is still being extracted and installed (it's damn slow) I am thinking... Is 18B91 still being signed? If yes, I can still downgrade, I'd just need to find the IPSW file and downgrade it, maybe?