Skip to the content
Know your tech before you buy it. Makers: get listed from $49/mo

crosvm

chromium.googlesource.com

  • Free plan
  • Open source
  • Windows
  • Linux
  • Android
  • API
  • Self-hosted

What crosvm is

crosvm is a free, open-source virtual machine monitor written in Rust. Created for ChromeOS, it runs Linux and Android guest systems in sandboxed environments and is also used in TerminalApp on Android, Cuttlefish, and Windows. It can be managed from the command line or through the Rust crosvm_control library, which provides programmatic interaction and generates a C/C++ compatible header during the build. Supported CPU architectures are x86_64, aarch64, and riscv64. The listed hypervisors are KVM, Gunyah, GenieZone, and Halla for Linux or Android, and WHPX and HAXM for Windows. Its virtio devices include networking, block storage, GPU, audio, filesystem, console, RNG, balloon, vsock, TPM, and video. Block storage supports raw, qcow2, zstd, and Android sparse formats; virtio-GPU provides 2D and 3D acceleration through virglrenderer, gfxstream, or vulkano. Each virtual device runs in its own Minijail sandbox by default, with syscall policies, Linux namespaces, seccomp filters, and dropped capabilities used for isolation. Linux hosts require kernel 4.14 or newer with KVM support; some devices have additional host requirements. Getting crosvm involves cloning its source repository and building it with Cargo.

Who it suits

crosvm suits developers and platform teams building or running Linux and Android guest systems in sandboxed virtual machines. Linux hosts need kernel 4.14 or newer with KVM support.

Good to know, and what to watch

  • Free open-source software under BSD-3-Clause.
  • Supports x86_64, aarch64, and riscv64.
  • Each virtual device runs in its own Minijail sandbox by default.
  • Offers command-line and Rust library control.
  • Linux hosts require kernel 4.14 or newer with KVM.
  • Some devices have additional host requirements.
  • SCSI, video, shared directories, and snapshotting are experimental or highly experimental.
  • Getting it requires cloning the source and building with Cargo.

crosvm

Free

Open source

Getting started

  1. Open the crosvm source repository
  2. Clone the source repository
  3. Install the required host environment
  4. Build crosvm with Cargo
  5. Use the command-line interface or the crosvm_control library
  6. Run it on a supported host with the required kernel and KVM support

Limits to check

Linux operation requires kernel 4.14 or newer with KVM support, and some devices have extra host requirements. SCSI, video, virtio-pmem shared host directories, and snapshotting are experimental or highly experimental; live migration is unavailable.

The Club's review

crosvm is a Rust virtual machine monitor for running Linux and Android guests inside strongly isolated environments. It is aimed at developers and platform operators who need a configurable monitor across Linux, Android, or Windows hosts. The trade-off is clear: crosvm offers deep control and security-oriented isolation, but using it starts with a source build rather than a turnkey desktop installer.

Overview

crosvm was created for ChromeOS and is also used by TerminalApp on Android, Cuttlefish, and Windows. It runs guests through a command-line management interface, with a Rust control library for applications that need programmatic operation. That profile makes it a practical building block for products, test systems, and custom virtualization stacks rather than a beginner-friendly virtual machine app.

Key features

Every virtual device runs in its own Minijail sandbox by default. crosvm combines syscall security policies with Linux namespaces, seccomp filters, and dropped capabilities to narrow what a device process can do. This per-device separation is a meaningful advantage when containment is a priority, although administrators still need to configure suitable hosts and guests.

The virtio device set is broad: networking, block storage, GPU, audio, filesystem, console, random-number, balloon, vsock, TPM, and video devices are supported. Virtio-block storage accepts raw, qcow2, zstd, and Android sparse formats, which helps when images come from different toolchains. Virtio-GPU provides 2D and 3D acceleration through virglrenderer, gfxstream, or vulkano, giving graphics-capable guests several implementation paths.

The Rust crosvm_control library offers an API alongside the CLI and generates a C/C++ compatible header during the build. That is useful for embedding crosvm into Rust or native-language management software. Supported CPU architectures are x86_64, aarch64, and riscv64. Snapshots and nested virtualization are supported, while live migration is not. SCSI, video, shared host directories through virtio-pmem, and snapshotting are marked experimental or highly experimental, so they are better reserved for evaluation than assumed production foundations.

Pricing

crosvm is free and open source under the BSD-3-Clause license. The sole crosvm plan costs nothing and has no trial or subscription charge. This suits teams that can build and operate their own virtualization layer; there is no paid tier that exchanges source work for a packaged management experience.

Platforms

Host support covers Linux, Android, and Windows, with Linux and Android also listed as guest operating systems. Linux hosts require kernel 4.14 or newer with KVM support, and individual devices can impose additional host requirements. The documented acquisition path is to clone the source repository and build with Cargo; a Linux development container is also described. Hypervisor options include KVM, Gunyah, GenieZone, and Halla on Linux or Android, plus WHPX and HAXM on Windows.

Who it's for

crosvm fits engineers building ChromeOS- or Android-adjacent systems, security-conscious platform teams, and developers who need virtio devices across multiple CPU architectures. Its API and sandbox boundaries are especially relevant when the monitor becomes part of a larger product. It is a poor match for users who want a graphical desktop workflow, a prebuilt installer, or live migration between hosts.

Pros and cons

Pros

  • Device-level sandboxing: Minijail, syscall policies, namespaces, seccomp, and dropped capabilities provide layered isolation by default.
  • Wide virtio coverage: Storage, networking, graphics, audio, TPM, filesystem, and other devices support varied guest designs.
  • Automation options: The Rust control library and generated C/C++ header support integration beyond shell commands.
  • Architecture and hypervisor range: x86_64, aarch64, and riscv64 support spans several Linux, Android, and Windows hypervisors.

Cons

  • Technical setup: Source cloning and Cargo compilation put build responsibility on the operator.
  • Host constraints: Linux requires a recent-enough kernel with KVM, and some devices need further host capabilities.
  • Uneven feature maturity: SCSI, video, virtio-pmem shared directories, and snapshotting carry experimental labels.
  • No live migration: Teams needing moving workloads between running hosts must choose another platform.

Alternatives

For a broader catalog, see Hypervisor Software.

Proxmox VE is a freemium Linux, Windows, web, and self-hosted option when you want a fuller management platform and are prepared for paid per-socket premium coverage.

Choose QEMU for a free, open-source monitor spanning Linux, macOS, and Windows without crosvm's ChromeOS-oriented focus.

UTM is the better choice for a packaged macOS or iOS experience, with a free open-source download and a $9.99 one-time Mac App Store edition.

Harvester suits teams seeking a free, open-source self-hosted virtualization platform with web and API access.

KVM is the direct Linux kernel virtualization foundation when you want the mainline Linux and QEMU components rather than crosvm's monitor layer.

Multipass is a free way to launch cloud-style local prototypes across Linux, macOS, and Windows.

oVirt is a free open-source community virtualization solution for Linux, self-hosted, web, and API deployments.

VMware Workstation Pro is a free alternative for 64-bit Intel or AMD Windows and Linux hosts with no subscription or license key.

Verdict

Choose crosvm if you are building or operating a security-sensitive Linux or Android virtualization stack and value per-device sandboxing, broad virtio support, and API control. Look elsewhere if you need a polished desktop workflow, packaged installation, mature experimental-device support, or live migration.

The verdict

crosvm offers a broad set of virtual devices and host options, with per-device sandboxing enabled by default. Building from source and host requirements make setup a technical task.

Questions people ask

Is crosvm free and open source?

Yes. The crosvm plan is free, and the project is open-source software under the BSD-3-Clause license.

Which host and guest platforms are supported?

Listed host platforms are Linux, Android, and Windows. Supported guest operating systems are Linux and Android.

How is crosvm managed?

It provides a command-line interface. The Rust crosvm_control library offers programmatic interaction and generates a C/C++ compatible header during the build.

What hypervisors can it use?

Linux or Android listings include KVM, Gunyah, GenieZone, and Halla. Windows listings include WHPX and HAXM.

Does crosvm support snapshots and live migration?

VM snapshots are listed, while live migration is not supported. Snapshotting is marked experimental or highly experimental in the documentation.

What the maker publishes

Additional devices
Other documented devices include console, RNG, balloon, vsock, TPM, pmem and video codecs. source
API
The Rust crosvm_control library provides programmatic interaction as an alternative to the command line and generates a C/C++ compatible header during the build. source
API compatibility
The documentation treats signature changes in crosvm_control as breaking changes for downstream projects. source
Architectures
The listed supported CPU architectures are x86_64, aarch64, and riscv64. source
Audio
virtio-snd has ChromeOS CRAS and Android AAudio backends. source
C and C++ interoperability
Building crosvm generates a crosvm_control.h header for C or C++ callers. source
CLI extensibility
Command-line options use key-value parameters and are discoverable through crosvm run --help. source
Company founding
Google says Google Inc. was officially created in August 1998. source
Company headquarters
Google lists its headquarters in Mountain View, California. source
Company legal name
Google's LinkedIn company profile identifies the maker as Google, a public software-development company. source
Company size
Google's LinkedIn profile lists company size as 10,001 or more employees. source
CPU architectures
The repository lists x86_64, aarch64 and riscv64 support. source
Documentation depth
The project book covers building, running, system requirements, devices, testing, tracing, integration, architecture, hypervisors and contribution. source
Download and build
The project documents obtaining crosvm by cloning its source repository and building it with Cargo; its Linux build guide also describes a development container. source
Experimental features
The documentation marks SCSI, video, shared host directories via virtio-pmem, and snapshotting as experimental or highly experimental. source
Filesystem devices
The project provides virtio-fs and virtio-9p filesystem devices. source
Graphics
The virtio-GPU supports 2D and 3D acceleration through virglrenderer, gfxstream, or vulkano. source
Graphics
virtio-gpu supports 2D and 3D acceleration through virglrenderer, gfxstream or vulkano. source
Hypervisor backends
Supported backends include KVM, Gunyah, GenieZone, Halla, WHPX and Intel HAXM. source
Hypervisors
The project lists KVM, Gunyah, GenieZone, and Halla for Linux or Android, plus WHPX and HAXM for Windows. source
Implementation language
The VMM is implemented in Rust. source
Independent technical history
An Android Open Source Project architecture page describes crosvm's process-per-device model, Minijail sandboxing and KVM dependence. source
Isolation
The project describes using Linux namespaces, seccomp filters, and dropped capabilities as part of its sandboxing approach. source
Known setup issue
Device jailing requires a /var/empty directory unless the pivot-root location is changed. source

Checked against the maker's pages on 15 Oct 2026.