mirrors/crosvm
1
0
Fork 0
mirror of https://chromium.googlesource.com/crosvm/crosvm synced 2024-11-24 20:48:55 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
crosvm/hypervisor
History
Oystein Eftevaag 78e2d51d4f Added test to verify nonsupport of MONITOR and related instructions 
Bug: 347004003
Change-Id: Idd62a6a9e16f6b5f19c1521fe9b35795c1f60e56
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5639273
Reviewed-by: Judson Powers <judsonp@google.com>
Commit-Queue: Oystein Eftevaag <oysteine@chromium.org>
Reviewed-by: Noah Gold <nkgold@google.com>
2024-08-22 20:08:38 +00:00
..
hypervisor_test_macro hypervisor: convenient macro to generate an array from inline assemblies 2024-05-21 19:31:17 +00:00
src hyp: Rename ProtectionType::loads_firmware() 2024-08-21 10:06:42 +00:00
tests Added test to verify nonsupport of MONITOR and related instructions 2024-08-22 20:08:38 +00:00
Cargo.toml hypervisor: TLB flush test 2024-07-10 20:42:34 +00:00
README.md

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