Skip to content

After updating QEMU to 10.0, XNU kernel of OS X 10.8 throws kernel panic (type=0 divide error)

Host environment

  • Operating system: macOS 15
  • OS/kernel version: Darwin Kernel Version 24.4.0: Fri Apr 11 18:32:43 PDT 2025; root:xnu-11417.101.15~117/RELEASE_ARM64_T8103
  • Architecture: ARM64
  • QEMU flavor: qemu-system-x86_64
  • QEMU version: QEMU emulator version 10.0.0
  • QEMU command line:
    #!/bin/zsh
    
    sudo qemu-system-x86_64 \
     -name "OS X Mountain Lion" \
     -machine q35 \
     -full-screen \
     \
     -drive if=pflash,file="Firmware.rom",readonly=true \
     -drive if=pflash,file="Settings.img" \
     \
     -hda "HD.qcow2" \
     -cdrom "Installer.dmg" \
     \
     -cpu IvyBridge,+sse4.1 \
     -m 4G \
     -smp 4 \
     \
     -device ich9-usb-uhci1 \
     -device usb-mouse \
     -device usb-kbd \
     \
     -device usb-audio,audiodev=audio \
     -device e1000,netdev=network \
     \
     -audiodev id=audio,driver=coreaudio \
     -netdev id=network,type=vmnet-shared \
     \
     -accel tcg

Emulated/Virtualized environment

  • Operating system: OS X 10.8
  • OS/kernel version: Darwin Kernel Version 12.5.0: Sun Sep 29 13:33:47 PDT 2013; root :xnu-2050.48.12~1/RELEASE_X86_64
  • Architecture: x86_64

Description of problem

Before updating to QEMU 10.0, my OS X 10.8 installation has worked pretty clear, but after QEMU update, XNU kernel now throws divide error during the boot.

Steps to reproduce

  1. Install OS X 10.8 on QEMU <10.0, for example 9.2.3.
  2. Update QEMU to 10.0 version
  3. Launch OS X

Additional information

Screenshot of the issue: Screenshot_2025-04-25_at_17.29.51

OpenCore config (not changed before update, so above suspicion): config.plist

Full OS X folder (without Installer.dmg): OS_X_10.8.zip

How I've done Installer.dmg:

  1. Go here
  2. xar -xf to .pkg
  3. Show package contents to extracted .pkg
  4. Here it is: InstallESD.dmg, which I've renamed to Installer.dmg
Edited by elyggg
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information