crosvm/hypervisor
Kim Mankyum ad53afb1e8 crosvm: Rename /dev/hvm to /dev/halla
Halla's kernel dev node name has changed.

Change-Id: Ia7bd28c07a4d62089eeaf691d205595b487cd307
Signed-off-by: Kim Mankyum <mankyum.kim@samsung.com>
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/7206166
Reviewed-by: Frederick Mayle <fmayle@google.com>
Reviewed-by: Will Deacon <willdeacon@google.com>
Commit-Queue: Frederick Mayle <fmayle@google.com>
Reviewed-by: Jiyong Park <jiyong@google.com>
2025-12-01 12:23:51 -08:00
..
hypervisor_test_macro Automatic clippy fix for Rust 1.88 2025-11-17 10:25:21 -08:00
src crosvm: Rename /dev/hvm to /dev/halla 2025-12-01 12:23:51 -08:00
tests Automatic clippy fix for Rust 1.88 2025-11-17 10:25:21 -08:00
Cargo.toml aarch64: remove support for 32-bit host userspace 2025-11-13 14:37:26 -08:00
README.md crosvm: Initialize Halla hypervisor 2025-08-28 14:33:13 -07:00

Hypervisor Support

Multiple hypervisor backends are supported. See Advanced Usage for overriding the default backend.

Hypervisors added to crosvm must meet the following requirements:

  • Hypervisor code must be buildable in crosvm upstream.
    • Within reason, crosvm maintainers will ensure the hypervisor's code continues to build.
  • Hypervisors are not required to be tested upstream.
    • We can't require testing upstream because some hypervisors require specialized hardware.
    • When not tested upstream, the hypervisor's maintainers are expected to test it downstream. If a change to crosvm breaks something downstream, then the hypervisor's maintainers are expected to supply the fix and can't expect a revert of the culprit change to be accepted upstream.

KVM

  • Platforms: Linux
  • Tested upstream: yes

KVM is crosvm's preferred hypervisor for Linux.

WHPX

HAXM

Android Specific

The hypervisors in this section are used as backends of the Android Virtualization Framework.

Geniezone

Gunyah

Halla