Virtualizing iOS on Apple Silicon

Original Article ↗ Hacker News Discussion ↗

Virtualizing iOS directly on Apple Silicon Macs is emerging as a way to run the real operating system and unmodified apps, contrasting with Apple’s existing Xcode simulator that recompiles binaries and only mimics iOS behavior. Commenters explore the technical hurdles of virtualization and emulation across architectures, the limits imposed by Apple’s security and platform policies, and the niche filled by commercial services like Corellium’s iOS cloud VMs. The conversation widens into long‑running frustrations about Apple’s separation of macOS and iPadOS, with many arguing that hardware capable of full desktop workloads is artificially constrained by software.

Virtualization vs. Emulation (ARM and x86)

  • Several comments clarify that “virtualization” needs matching CPU architectures; ARM iOS/macOS can’t be virtualized on x86-64, only emulated.
  • QEMU-based ARM emulation on x86 is described as extremely slow for general use, OK only for simple testing.
  • Emulation of full OS instruction sets with MMUs is seen as inherently hard to make fast; user‑space‑only translation (like Apple’s Rosetta or Windows’ x86-on-ARM) can be nearly transparent.
  • Paging and memory model differences (e.g., x86 4K pages vs Apple 16K pages) are cited as major performance obstacles.

Why This iOS Virtualization Matters Beyond Apple’s Simulator

  • The Xcode iOS Simulator runs a recompiled, Mac-native build of the app against Mac-based frameworks that mimic iOS, not real iOS.
  • It cannot run arbitrary App Store binaries, nor does it reveal real iOS internals; digging down eventually reaches macOS.
  • A true virtualized/emulated iOS instance would run “real” iOS images and binaries and be useful for deeper OS probing and security research.

iOS vs. macOS: Similarities, Differences, and Convergence

  • Both use the XNU kernel and share low-level components; Apple Silicon Macs and iDevices have very similar boot chains.
  • Key differences:
    • macOS supports disk-backed swap; iOS traditionally relies on memory compression and strict termination of apps on pressure (though iPadOS added limited swap).
    • iOS apps are always sandboxed; macOS apps are mostly not.
    • Large divergence in user-space frameworks and UI stacks; macOS is more permissive and complex.
  • iOS apps can run on macOS via Mac Catalyst or the “iOS apps on Apple Silicon” layer, but this involves a user-space shim and can be fragile.

Desire for macOS or VMs on iPad

  • Many commenters want macOS (or at least real VMs) on iPad Pro hardware for development, 3D, and pro workflows, arguing the chips are capable.
  • Others note UX, input, memory, and security complications, plus the large engineering effort to make macOS apps usable on a touch-first tablet.
  • Comparisons are made to Windows tablets, Android/ChromeOS VMs, and past features like Samsung DeX and Continuum, which saw limited mainstream adoption.

Commercial iOS Virtualization (Corellium)

  • Corellium is cited as the only public “complete” iOS cloud VM solution, with high per-user pricing aimed at security research and enterprise.
  • Some speculate that local iOS virtualization on Apple Silicon Macs could undercut demand for such services, though enterprise pricing and deals remain opaque.

Related Low-Level and QEMU Efforts

  • Other projects have partially booted newer iOS versions or even SpringBoard under QEMU, but some code is private.
  • Jailbroken devices have demonstrated hardware-accelerated VMs.
  • Apple’s own Hypervisor framework and tools like UTM show what’s possible on ARM Macs and, in limited form, iPads.