Cloud Hypervisor

Cloud Hypervisor is a free, open-source Virtual Machine Monitor written in Rust for modern cloud workloads. It runs Linux and Windows guests on Linux hosts using x86-64 or AArch64 architectures, with minimal hardware emulation. Operators can manage VM lifecycles through a REST API or command-line interface, with an optional D-Bus API. The project supports snapshots, nested virtualization, paravirtualized devices, and physical device passthrough. It also supports live migration between hosts without interrupting VMs, and migration data can be encrypted with mutual TLS. The maker says direct kernel boot reaches userspace in less than 100 ms. Cloud Hypervisor is supported by Kata Containers for running secure containerized workloads. Linux hosts need kernel 4.11 or later for the required KVM functionality; kernel 5.6 is recommended for adequate performance. Packages for some popular Linux distributions are available through the Open Build Service. The project is governed openly as part of the Linux Foundation and directs users to GitHub discussions or Slack for help, GitHub issues for bug reports, and a mailing list for broader discussion.

Cloud Hypervisor offers VM lifecycle controls, migration, and device options for Linux-hosted workloads. Its documented kernel requirements and supported host architectures help define where it fits.

Cloud Hypervisor suits operators building or running virtualized cloud workloads on Linux hosts with x86-64 or AArch64 architectures. It may also suit teams using Kata Containers for secure containerized workloads.

Cloud Hypervisor is a free, open-source virtual machine monitor built in Rust for modern cloud workloads. It fits technically capable teams running Linux hosts that need programmable VM operations rather than a desktop-oriented interface. The combination of migration, passthrough and low licensing cost is compelling, but host requirements and a self-managed operating model make it a specialist choice.

Overview

Cloud Hypervisor keeps hardware emulation deliberately minimal and focuses on cloud-style virtualization. It supports modern Linux and Windows guests on x86-64 and AArch64 hosts, so it can cover mixed guest estates while remaining tied to Linux-based infrastructure. The project is governed openly under the Linux Foundation and supported by multiple organizations, which is useful for teams that prefer a public project structure over a proprietary appliance.

This is not a packaged desktop environment or a hosted service. You provide the Linux hosts, KVM-capable kernel, deployment automation and operational support. Packages for some popular Linux distributions are available through the Open Build Service, while help is directed to GitHub discussions or Slack, bug reports to GitHub issues, and broader topics to a mailing list.

Key features

VM lifecycle control is available through a REST API and command-line interface, with an optional D-Bus API. That gives platform engineers a practical split between automated provisioning and local administration, without forcing every workflow through one management layer. The maker says direct kernel boot reaches userspace in less than 100 ms, a useful target for services where launch latency matters; real startup behavior will still depend on the host and guest workload.

Device support covers paravirtualized devices and physical device passthrough. Paravirtualization helps keep a lightweight device model, while passthrough is valuable when a workload needs direct access to host hardware. VM snapshots and nested virtualization are also supported, extending the design beyond a single-purpose boot runner.

Live migration moves VMs between hosts without interruption, which is significant for maintenance and capacity work where stopping a service is unacceptable. In the v53.0 release, migration data can be encrypted with mutual TLS, an important control when VM state crosses host boundaries. Cloud Hypervisor is also supported by Kata Containers for secure containerized workloads, giving container platforms another isolation option.

The project cites its Rust implementation and minimal emulated-device surface as defenses against common virtualization security issues. Those are sensible architectural choices, but they do not replace hardening, patching and review of the surrounding host and guest stack.

Pricing

There is no paid tier, seat charge, usage quota or free-trial period to weigh against the free plan. That makes Cloud Hypervisor suitable for experiments, internal platforms and production deployments that can fund their own operations rather than software licenses. The trade-off is that support is community-oriented through the project channels, not a bundled commercial service.

Platforms

Cloud Hypervisor is offered for API, Linux and self-hosted use. Linux is the host platform, with a documented minimum host kernel of 4.11 for required KVM functionality and 5.6 recommended for adequate performance. Hosts can be x86-64 or AArch64, and guests can be modern Linux or Windows systems. Organizations on older kernels, non-Linux hosts or unsupported host setups should treat that requirement as a hard compatibility check before committing.

Who it's for

Choose Cloud Hypervisor when you operate Linux infrastructure and want an open VMM that can be embedded in an orchestrated control plane. It is a strong fit for cloud platforms, infrastructure teams and Kata Containers deployments that value API access, migration, passthrough and snapshots without license fees.

It is less suitable for newcomers seeking a guided desktop manager, for teams unwilling to maintain hosts and automation, or for environments that cannot meet the kernel and KVM baseline. Its strengths reward engineering ownership; they do not eliminate that ownership.

Pros and cons

Pros

• Free and open source: the VMM has no commercial tier or stated usage cap, so licensing does not scale with VM count.
• Multiple control paths: REST, CLI and optional D-Bus interfaces support both automation and direct operations.
• Operational mobility: live migration without interruption, with mutual-TLS encryption for migration data in v53.0.
• Flexible device model: paravirtualized devices and physical passthrough cover efficiency and hardware-access scenarios.
• Broad guest and host architecture support: modern Linux and Windows guests run on x86-64 and AArch64 Linux hosts.

Cons

• Linux-host dependent: the 4.11 kernel minimum and 5.6 recommendation rule out older or non-Linux host environments.
• Self-managed operations: deployment, security and lifecycle work remain with your team rather than a commercial service.
• Community-led support: assistance is routed through project forums, Slack, issues and a mailing list.

Alternatives

Proxmox VE is the better pick when you want a freemium virtualization platform with web access and broader platform coverage, plus an optional Premium subscription priced at €1,100 a year per occupied physical CPU socket.

crosvm is another free, open-source option for teams that need Android, Linux, Windows and self-hosted platform coverage under a BSD-3-Clause license.

UTM suits Mac users who want a graphical application: its open-source GitHub version is free, while the Mac App Store edition costs $9.99 as a one-time purchase.

Firecracker is a free Apache 2.0-licensed VMM for API-driven Linux and self-hosted environments.

GNOME Boxes is a free Linux desktop application for users who prefer a simpler local interface.

Harvester is a free, fully open-source platform with API, web and self-hosted Linux coverage.

KVM is the free open-source Linux virtualization component integrated into mainline Linux and used with mainline QEMU userspace.

Multipass is a free option for launching prototype clouds locally across Linux, macOS and Windows, with host requirements varying by operating system.

For broader comparisons, see Hypervisor Software and Virtual machine software.

Verdict

Cloud Hypervisor is a strong recommendation for infrastructure teams that want a no-license-fee, API-controlled VMM with live migration, snapshots, passthrough and modern architecture support. Choose it for Linux-hosted cloud or container platforms where your engineers can own the host stack. Look elsewhere if you need a desktop-first experience, non-Linux hosts, or commercial operational support built into the product.