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
Idan Raiter 5c0079697e hypervisor: Minimal exception injection test 
Write an invalid MSR, check GP handler runs. Initially written in real
mode but we saw Intel HAXM doesn't work, so swapped to long mode. Better
to test what we really will be doing anyway.

BUG=b:334055761
TEST=run test

Change-Id: If97b720d13eb796fd8d3b45dd4fcef25d0abf59c
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5714993
Reviewed-by: Noah Gold <nkgold@google.com>
Commit-Queue: Idan Raiter <idanr@google.com>
Reviewed-by: Oystein Eftevaag <oysteine@chromium.org>
2024-07-19 16:59:31 +00:00
..
hypervisor_test_macro
src hypervisor: aarch64: snapshot cache architecture info 2024-07-18 23:38:34 +00:00
tests hypervisor: Minimal exception injection test 2024-07-19 16:59:31 +00:00
Cargo.toml
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