crosvm/hypervisor
Kaiyi Li 39ed318f8f hypervisor: fix compile error with whpx feature enabled
BUG=b:354901961
TEST=cargo nextest run -E 'binary(hypervisor_virtualization) & package(hypervisor)' --features=all-msvc64,whpx --workspace --no-capture --retries=0

Change-Id: I054183f0e938dc90026c1d2dd364d4ddb7c1437d
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5835881
Reviewed-by: Judson Powers <judsonp@google.com>
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
2024-09-05 22:41:27 +00:00
..
hypervisor_test_macro hypervisor: convenient macro to generate an array from inline assemblies 2024-05-21 19:31:17 +00:00
src kvm: add mut to mutable binding 2024-09-05 21:11:59 +00:00
tests hypervisor: fix compile error with whpx feature enabled 2024-09-05 22:41:27 +00:00
Cargo.toml hypervisor: TLB flush test 2024-07-10 20:42:34 +00:00
README.md

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