macOS Virtualization Framework Error — VM Creation and Boot Failures on Apple Silicon
Warningsystem
Overview
Fix macOS Virtualization Framework errors when creating or running virtual machines on Apple Silicon Macs including Linux VMs, container runtimes, and dev environments.
Key Details
- The macOS Virtualization Framework provides native VM support on Apple Silicon without third-party hypervisors
- It powers Docker Desktop, UTM, Parallels, and other VM tools on Apple Silicon Macs
- VMs can run ARM64 Linux distributions and (with Parallels) ARM Windows 11
- The framework requires macOS Monterey 12+ and Apple Silicon (M1/M2/M3/M4 series)
- Common tools using this framework: Docker Desktop, Lima, UTM, Parallels Desktop, OrbStack
Common Causes
- Insufficient available RAM or disk space to allocate to the virtual machine
- Trying to run x86_64 VM images on Apple Silicon without emulation (requires ARM64 images)
- Docker Desktop or OrbStack VM corrupted requiring recreation of the Linux VM
- SIP (System Integrity Protection) or entitlement restrictions blocking VM creation
Steps
- 1Ensure sufficient resources: at least 4GB RAM and 20GB disk free for the VM
- 2Use ARM64/aarch64 Linux images — not x86_64 — for native performance on Apple Silicon
- 3For Docker Desktop: Preferences > Resources > reduce memory allocation, then restart Docker
- 4Reset the VM: Docker Desktop > Troubleshoot > Clean/Purge data to recreate the Linux VM
- 5Update macOS and the VM application to the latest versions for framework compatibility fixes
Tags
virtualizationapple-siliconvmdockerframework
Related Items
More in System
windows-C000021A-status-system-process-terminatedWindows Error 0xC000021A — STATUS SYSTEM PROCESS TERMINATED
Criticalwindows-C0000225-boot-configuration-errorWindows Error 0xC0000225 — Boot Configuration Error
Criticalwindows-C000000F-boot-selection-failedWindows Error 0xC000000F — Boot Selection Failed
Criticalwindows-80004005-unspecified-errorWindows Error 0x80004005 — Unspecified Error
Warningwindows-80070570-file-or-directory-corruptedWindows Error 0x80070570 — File or Directory Corrupted
Errorwindows-system-0xc0000185Windows Error 0xC0000185 — Boot Device Inaccessible
CriticalFrequently Asked Questions
Not natively. The Virtualization Framework runs ARM64 VMs. For x86_64, use UTM with QEMU emulation (very slow) or run ARM64 Linux distributions which have excellent package availability.