gillesgoetsch/OmacVM

One command builds the VM, in its own app OmacVM.app, UTM, VMware Fusion or Parallels Desktop. Then your Mac's Wi-Fi, Bluetooth, sound, keys, trackpad, displays, Night Shift and wallpaper all work in Omarchy.

With Omanotch: Omarchy's real bar beside the MacBook's notch, where the VM leaves a black strip.

curl -fsSL https://raw.githubusercontent.com/gillesgoetsch/omacvm/main/install.sh | bash

Using a coding agent? Copy the prompt for it.

See the full compatibility list per app below, or every feature in detail.

Type omacvm in Omarchy (or pick it in the Omarchy menu): every feature with its live status, on or off with space, plus updates and "report a problem".

OmacVM.app is the recommended way: free, open source, and the only one with hardware video and the full GPU. UTM is the free classic. VMware Fusion is free. Parallels is the most polished, but paid.

¹ after one setting in Parallels · ² when the pointer crosses the VM's edge · ³ a Graphics setting per VM (OpenGL, Vulkan, Automatic = Vulkan on macOS 26+, OpenGL before); Vulkan adds Vulkan apps next to OpenGL: on KosmicKrisp on macOS 26 or newer, on MoltenVK before; Vulkan windows reach the screen by a copy on the Mac, faster than the VM's software copy; OpenGL and browser speed are the same either way, and Vulkan gives Chromium WebGPU; OpenCL and WebGPU in Firefox opt-in (numbers) · ⁴ with the VM in full screen on that display

Power: the whole Mac from its battery's telemetry on a MacBook Air M2 8 GB, each VM 4 CPUs and 4 GB alone in native full screen, brightness 50 %; OmacVM.app played the video on the Mac's media engine. How it was measured.

Full comparison with benchmarks: docs/compare.md.

The command at the top puts OmacVM in ~/.omacvm (it follows the releases: omacvm update takes it to the newest), adds the omacvm command and starts it. Run omacvm any time after that: with no VM yet it builds one; otherwise it asks what you want to do (build another VM, switch features, update, check). Prefer git? git clone https://github.com/gillesgoetsch/omacvm and run ./install.sh in it. Using a coding agent? Copy the prompt. Only OmacVM.app? Its window's "omacvm in Terminal" Install adds the command.

• An Apple Silicon Mac, M1 or newer, with macOS 15 for OmacVM.app or macOS 14 for the others. (On an M1 or M2, Asahi Linux can also run Omarchy natively.)
• About 30 GB of free disk space on the drive the VM goes to, and a decent connection.
• One of the apps: OmacVM.app (omacvm downloads it), UTM 5 (beta), VMware Fusion 13 or Parallels Desktop 19, or newer. How to get each: docs/routes/.
• For UTM, Fusion and Parallels: Xcode Command Line Tools and Homebrew with zstd and e2fsprogs. OmacVM.app needs neither: it brings what it runs on the Mac. (install.sh asks for the Command Line Tools once, for git.)

omacvm checks all of this first, and installs what is missing or waits for you.

omacvm            # or: omacvm build

It asks a few questions (the app, build or download, CPUs and memory, features, your user and password), shows a summary and builds. A build takes 30 to 70 minutes: OmacVM.app 10 to 30, VMware Fusion about 15 more. A prebuilt VM is ready a few minutes after a 3.5 to 6 GB download. A VM window opens on the way: that is the temporary installer, leave it alone.

For scripts: --vm-type app|utm|fusion|parallels, --prebuilt, --vm-dir PATH (Parallels and Fusion), --FEATURE or --no-FEATURE, --yes. omacvm build --help lists them all; every step in detail: docs/guide.md.

When it is done, allow the macOS prompts for OmacVM Bridge and OmacVM Gestures (which ones). On Parallels, change one setting so Cmd reaches Omarchy.

omacvm features                 # switch features on or off
omacvm update                   # the newest OmacVM, on the Mac and in every running VM
omacvm check                    # what works and what to fix; it changes nothing
omacvm vms                      # your VMs and their OmacVM version
omacvm report                   # report a problem: shows what goes into the GitHub issue first
omacvm resources --vm NAME      # change its CPUs and memory
omacvm graphics --vm NAME       # OmacVM.app: OpenGL, Vulkan or Automatic

In Omarchy, omacvm (also in the Omarchy menu and the bar; from the Mac, OmacVM.app's Features… or omacvm features --in-vm) opens the control centre: every feature with its status, on or off with space, repair, updates, and "report a problem" without personal data.

OmacVM.app looks for a new version once a week (Check Now in its window asks at once; Go Back in its menu; off in its settings or the control centre). u in the control centre updates everything: OmacVM.app on the Mac first (the VM restarts once, after one confirm), then the VM. It shows each step while it runs; R restarts the VM at the end for kernel, memory and keyboard changes.

Add --vm NAME for a VM other than the default. Have an Omarchy VM from omarchy-mac already? omacvm apply --vm NAME adds OmacVM to it.

Put the VM in full screen for the gestures. ⌃⌥ Esc moves the monitor under the pointer one Space over to macOS, with macOS's own animation; the VM stays full screen in its Space. Press it there again to go back into the VM; twice quickly opens Mission Control (more). Everything else: docs/guide.md.

OmacVM installs omarchy-mac, the Arch Linux ARM port of Omarchy, onto the VM's own disk: a full Omarchy with omarchy update, not a demo. Small helpers on the Mac pass its hardware to the VM over the VM's private network, with a secret token: OmacVM Bridge, OmacVM Gestures and Omanotch.

More: docs/how-it-works.md, the whole build in AGENTS.md, everything else in docs/.

Start with omacvm check: it names what is wrong and what to do. Still stuck? omacvm report (or ! in the control centre) collects the checks, versions and logs without your names, addresses, Wi-Fi names or tokens, shows you the text, then opens a pre-filled GitHub issue.

• The Mac's menu bar stays over the full-screen VM: System Settings › Menu Bar › Automatically hide and show the menu bar: In Full Screen Only.
• Gestures do nothing: the VM must be full screen and in front; if ⌃⌥ Esc left you in the VM without the trackpad, press it again. omacvm check says when the helpers miss a permission.
• "answers with another SSH host key" after a rebuild: omacvm apply --vm NAME --reset-host-key.

More: docs/troubleshooting.md.

omacvm uninstall            # --purge also removes the bridge token and settings

Then delete the VM in its app, and remove the OmacVM apps from System Settings › Privacy & Security › Location Services if still listed. The omacvm command itself stays: rm -rf ~/.omacvm "$(command -v omacvm)" removes it. OmacVM.app stays too: drag it to the Bin (its VMs stay in ~/OmacVM, older ones in ~/Library/Application Support/OmacVM/VMs, until you delete them).

OmacVM 2.7.0 and older: don't use --purge if you have OmacVM.app VMs. It deletes them with the settings. Fixed in 2.7.1: run omacvm update first.

Omarchy (MIT) and DHH for making this!

omarchy-mac and try-omarchy by the Omarchy team. try-omarchy (MIT) gives the camera bridge, the Mac's battery in the VM and OmacVM.app's pieces. Also Arch Linux ARM; omarchy-parallels by Vincenzo Palazzo (MIT), whose image builder is the temporary installer; and omarchy-arm-utm, whose UTM findings shaped the UTM route and whose Wayland SPICE agent (MIT) is the base of omacvm-vdagent. The bar widgets are clones of Omarchy's own.

OmacVM is a community project, not affiliated with the Omarchy team, Parallels, UTM, VMware (Broadcom) or Apple.

Want to help? Start with CONTRIBUTING.md.

MIT, see LICENSE. Code reused from others: THIRD_PARTY_NOTICES.md.