To verify it, just install 10.13.6 with IOIIIO's guide, then compile Shaneee's High Sierra Kernel with this minimal OPEMU patch which I've commented all other instruments emulation besides sysenter/sysexit, you'll still get wine/32bit macOS app running, but if you comment opemu_sysenter call which emulates sysenter/sysexit, you'll get illegal instruments. Then why when opening wine/32bit app on kernels that without OPEMU, we got illegal instrument error? That's because AMD lacks sysenter/sysexit in 64-bit compatible mode, only the two instrument which commonly used for implementing syscall in 32bit OS, any other i386 instrument working natively, at least on zen2. AMD CPU does not totally unable to run ANY 32bit code in previous kernel-patched macOS.It's somewhat tricky - beware address space, stack and data segments, return addresses, so first make sure your test program works on a proper mac.ĭoubt that what crossover19 needs is OPEMU. Try to build yourself a C program that builds as a 64 bit C program but calls 32 bit bytecode via a 32 bit code segment entry and see if you can get this working on AMD. If you have some custom kernel modifications or modules that's the first place to look. What is probably a problem is system calls and signal delivery to a process/thread that currently has %cs pointing to a 32 bit code segment. If I understand the screenshots right and taskmgr is at least starting up, and if that cmd is running in 32 bit code, the important thing is working. LDT entries aren't CPU specific (unlike HW Hypervisors, and the Apple hypervisor API that is very intel specific), so in theory this should work. The other way around the permission is to disable system integrity protection. That's what the special permission is needed for, although it seems 10.15.4 removed that requirement.

The 32 bit execution magic works by creating 32 bit LDT entries via i386_set_ldt. I'm afraid I can't spend a lot of time though because we don't support hackintoshes.įor some technical detail see.

I am currently waiting for a compile to finish so I am dropping a few quick notes. A guy on our IRC channel brought my attention to this bug.

Crossover emulator mac