Apple Silicon virtualisation is built into macOS via Virtio drivers, delivering near-native CPU/GPU performance but with hard limits on App Store apps and iCloud access.
Key Takeaways
Apple baked Virtio driver support into macOS (Monterey+) because Apple Silicon hardware has no PC-standard components third-party hypervisors could map to.
CPU single-core VM scores hit 93% of host; GPU Metal scores reach 92% of host via the Apple Paravirtual device.
App Store apps that check credentials fail entirely in VMs – Apple’s authorisation model blocks it and there is no workaround in sight.
iCloud and iCloud Drive only work when both host and guest run macOS 15 Sequoia or later; VMs upgraded from earlier macOS still cannot access iCloud.
macOS licences allow max two concurrent VMs, restricted to dev, testing, macOS Server, or personal non-commercial use – enforced by the OS itself.
Hacker News Comment Review
Consensus is that macOS VM performance is genuinely near-native thanks to the hypervisor, but the iCloud and App Store gaps make VMs impractical for everyday app testing workflows.
UTM confusion surfaced: the article implies UTM is a software emulator, but commenters note UTM supports both emulation and Virtualisation.framework modes – Windows ARM can run with full hypervisor acceleration via the latter.
One commenter flagged additional practical upsides not in the article: fast enough launch times for serverless use cases, and Apple’s open-source container support is built on the same Virtualisation framework, making it more sandboxed than Docker.
Notable Comments
@w10-1: notes snapshot restore works for macOS guests but not Linux, and that Virtualization-backed containers are a more secure alternative to Docker.
@PlunderBunny: raises the UTM ambiguity – the article groups UTM with emulators, but UTM can use the Apple hypervisor for Windows ARM, not just software emulation.
