Limits

The two-macOS-VM limit: where it comes from, how the Hoy system extension enforces it, which VMs count and which do not, plus the other known limits of this release.

A Mac can run two macOS VMs at a time. The limit comes from Apple's macOS license, not from Hoy. It applies to every macOS VM on the Mac, whatever software runs it, and Hoy counts across all tools. A license key or a setting cannot raise the limit. A setting can lower it.

How it is enforced#

The Hoy system extension is an Endpoint Security extension that comes inside Hoy.app. With it on, it counts every macOS VM on the Mac, started by any tool and any user, and stops a third from booting. See Install for the two switches that turn it on.

This release requires the extension. Until it is on, hoy start refuses macOS VMs with exit code 5 and the reason limit_service_inactive, and hoy doctor shows a failing limit-service check. Linux VMs and other apps are not affected, whether the extension is on, off or missing.

When a third macOS VM is refused, hoy start exits with code 5. The message names each VM it counted: its process ID, the tool and why it counts, and ends with a command to run next:

hoy: can't start demo3: 2 macOS VMs are already running on this Mac.
Apple's macOS license allows 2 per Mac, and Hoy enforces it.
 
  running   demo   (hoy, pid 30100)
            demo2  (hoy, pid 30583)
 
Stop one first, for example:  hoy stop demo

With --json the error has the reason macos_vm_limit, the limit, the running VMs and the next command. hoy doctor and hoy health list every VM and whether it counts.

What counts#

Counts as a macOS VMDoes not count
Hoy macOS VMs, including a forkLinux VMs on Virtualization.framework: Docker Desktop, OrbStack, Colima/Lima and Rancher with vz, Podman, UTM's Apple backend
Other apps' macOS VMs on Virtualization.framework (they hold the macOS license lock that Apple's framework takes for a macOS guest)The engines of Docker Desktop, Parallels Desktop (Linux and Windows) and OrbStack
A VM run by another hypervisor engine while it runs, to be safe and whatever its guest: QEMU (also behind Colima, Lima and Podman, and UTM's QEMU backend), krunkit, VMware Fusion, Multipass. Each running VM counts as oneUTM open with no QEMU VM running
A VM whose files Hoy cannot read, such as another user's, to be safeA VM that is stopped

A stopped VM does not count. Stop one VM, or remove it with hoy rm, and the slot is free.

Make the most of two#

  • Use snapshots to go back to a clean state instead of keeping many VMs around.
  • Remove VMs you are done with. Images stay, and hoy create makes a new VM from one in seconds.

Other known limits#

  • Hosts. Apple silicon with macOS 26.x or 27.x. A newer macOS is untried.
  • Images are desktop images. There is no headless image from hoy image create yet. You make each image yourself, on the same APFS volume as the Hoy home.
  • A desktop login session. Hoy's background service runs in the logged-in user's desktop session. Running hoy image create and VMs with nobody logged in at the desktop has not been validated. See Install.
  • Graphics. Under heavy graphics load the guest's frame rate is below what Apple's Virtualization framework reaches. Headless and light desktop use is not affected.
  • GPU acceleration is experimental. hoy create --gpu-acceleration is off by default. A VM cannot be snapshotted while a program in it has a GPU renderer session open. See the CLI reference and Run local models on the GPU.
  • Apple Account, iCloud and App Store sign-in do not work in a Hoy VM. See Apple Account and iCloud.
  • Desktop console. --vnc publishes the VM's console on a Unix socket in the VM folder, not on a TCP port. Use hoy exec for shell access.
  • No microphone input in the guest yet.