Virtualization

try-omarchy2.5k★

Omarchy is Basecamp's opinionated Arch Linux desktop, and trying it on a Mac used to mean building a VM yourself and fighting the graphics stack. Try Omarchy is a signed, notarized .dmg that does the work for you: an ARM64 Arch image with Omarchy preinstalled, a QEMU runtime on Apple's Hypervisor Framework, and a small Swift launcher, all packaged as one Mac app. MIT licensed. It behaves like a Mac app rather than a VM console. Hardware-accelerated ARM64 virtualization with VirGL graphics, a resizable native window that pushes resolution and HiDPI scale changes into the guest automatically, two-way clipboard sharing for text and PNG images, Mac audio input and output selectable from inside Linux with live routing, and one optional shared folder that keeps its name across the boundary, so ~/Work on the Mac is ~/Work in Omarchy. Requirements are an Apple Silicon Mac on macOS 15 or newer and about 8GB free to start. Everything is free and there is no paid version. Solo devs curious about Omarchy, or about a tiling Wayland desktop in general, get the cheapest possible way to find out without touching their Mac install. Teams: treat this as an evaluation sandbox, not a place to do production work. Two catches. Video decoding is CPU-only right now, so playback drags at higher resolutions, and the maintainer says a better video path is still in development. And this is unofficial: not affiliated with Omarchy or Basecamp, pinned to a specific upstream revision, and you are trusting one maintainer's prebuilt image with accessibility and microphone permissions on your machine. Read what it asks for before you click allow, or build it from source.

zsvirt1.9k★

ZSvirt is a full virtualization platform: install it on bare metal and it manages VMs, virtual networks, storage, snapshots, and live migration from one web console. Same job VMware vSphere does, at GPL-3.0 and zero license cost. ZStack, an infrastructure vendor that sells a commercial product called ZSphere, took that engine and open sourced it in August 2026. This is not a Docker pull. You are standing up a hypervisor cluster: hosts, primary and backup storage, network configuration, then the management plane on top. Budget real time for a first cluster and someone who knows KVM and Linux networking for when it breaks. The VMware migration tooling is the most interesting piece, and the part most likely to surprise you on a production fleet. Homelab and solo: worth a look, though Proxmox VE has a decade of community answers behind it and ZSvirt has weeks. Small teams: only if someone owns infrastructure as an actual job. Shops reassessing VMware licensing: a legitimate evaluation candidate, and having a vendor with production customers behind the code matters here. The repo went public in August 2026 with a handful of commits. The engine has enterprise mileage; the open source project does not. Governance docs exist, a maintainer community does not yet. Lab it, do not bet the cluster your business runs on until the release cadence proves itself.

darwin-vm1.2k★

darwin-vm boots iOS and macOS inside QEMU on ordinary hardware. It emulates A14 through A19 iPhones and M1 through M5 Macs, drops you at a root shell in seconds, and lets you compile and run your own command line programs without jailbreaking anything. Be clear about the scope, because the author is. There is no screen, no WiFi, no Bluetooth, no graphics, no GUI apps, and no SpringBoard. This boots Darwin to a barebones root shell and nothing more. That is not a limitation somebody forgot to fix, it is the entire design. What it buys you is a kernel you can debug and patch, on a platform that normally makes both nearly impossible. Security researchers and anyone reverse engineering Apple internals get an iteration loop measured in seconds rather than device reflashes. It supports SPTM based kernels and MIE capable CPUs, which is where current Apple security work is happening. MIT licensed and free. The catch is the setup path. You need a Mac to prepare the firmware files, plus Python, jq, wget, and the ipsw tooling, and then QEMU build dependencies to compile. It is also a two month solo project rather than a maintained platform, so treat it as a sharp research instrument, not infrastructure.