crosvm/hypervisor
Noah Gold 7c24ffe4f9 hypervisor: add xsaves test
BUG=b:333888472
TEST=presubmit

Change-Id: I5bb81c9c5504e6ed90c050616bac5ecca3fb1a2a
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5665734
Commit-Queue: Noah Gold <nkgold@google.com>
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2024-06-28 23:11:30 +00:00
..
hypervisor_test_macro
src
tests hypervisor: add xsaves test 2024-06-28 23:11:30 +00:00
Cargo.toml
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