ACRN Hypervisor vs crosvm
ACRN Hypervisor
projectacrn.orgcrosvm
chromium.googlesource.comSide by side
| Figure | ACRN Hypervisor | crosvm |
|---|---|---|
| Price from | Free | Free |
| Free plan | Yes | Yes |
| Free trial | — | — |
| Open source | — | Yes |
| Windows | — | Yes |
| Linux | Yes | Yes |
| Android | — | Yes |
| API | — | Yes |
| Self-hosted | Yes | Yes |
| Plans published | 1 | 1 |
| Spec score · Hypervisor Software | 8.0 (#13) | 9.0 (#1) |
| License | The source code is provided under the BSD 3-Clause license. | crosvm is released under the BSD-3-Clause license. |
| Support | The project offers community support through mailing lists and IRC channels, and holds monthly technical community meetings. | The project points users to a public issue tracker and Matrix chat, and provides announcements and a developer mailing list. |
Plans
In their own words
ACRN Hypervisor
ACRN Hypervisor is a free, open-source Type 1 hypervisor stack for embedded IoT development. It runs directly on Intel x86 bare-metal hardware and supports Linux, Windows and RTOS guests such as Zephyr; the project also lists VxWorks, Xenomai, Celadon and Android. CPU, I/O and networking virtualization are included, with I/O mediators for sharing graphics and audio across virtual machines. Resource partitioning is designed for safety-critical and non-safety-critical domains to coexist on one system-on-chip. The ACRN Device Model provides virtual device emulation. The project describes a codebase under 40K lines and reports low latency, fast boot times and responsive hardware communication. ACRN uses the BSD 3-Clause license, offers a command-line management interface and supports nested virtualization. Source code is maintained in a public GitHub repository with online documentation. Community help is available through mailing lists, IRC channels and monthly technical meetings.
crosvm
crosvm is a free, open-source virtual machine monitor written in Rust for running Linux and Android guest systems in sandboxed environments. Developed for ChromeOS, it is also used in TerminalApp on Android, Cuttlefish, and Windows. Each virtual device runs in its own Minijail sandbox by default, with syscall policies, namespaces, seccomp filters, and dropped capabilities contributing to isolation. Supported CPU architectures are x86_64, aarch64, and riscv64. The project lists KVM, Gunyah, GenieZone, and Halla for Linux or Android, and WHPX and HAXM for Windows. Virtio devices cover networking, storage, GPU, audio, filesystems, console, RNG, ballooning, vsock, TPM, and video. Block storage supports raw, qcow2, zstd, and Android sparse formats. Linux hosts need kernel 4.14 or newer with KVM support; some devices have additional host requirements. The project documents obtaining crosvm from its source repository and building it with Cargo. SCSI, video, shared host directories via virtio-pmem, and snapshotting are marked experimental or highly experimental.