mirror of https://chromium.googlesource.com/crosvm/crosvm synced 2024-11-24 20:48:55 +00:00

History

Noah Gold 458bc9e033 hypervisor: add test for interrupt state snapshot. After running into issues with MSRs, it seemed advisable to have a smoke test for these functions too. BUG=b:269705560 TEST=unit test Change-Id: I2017dc95c19a7097a4be17099cd33ae75bf7c6f6 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4546270 Commit-Queue: Noah Gold <nkgold@google.com> Reviewed-by: Vaibhav Nagarnaik <vnagarnaik@google.com> Reviewed-by: Frederick Mayle <fmayle@google.com> Reviewed-by: Steven Moreland <smoreland@google.com>		2023-05-23 20:00:32 +00:00
..
src	hypervisor: add test for interrupt state snapshot.	2023-05-23 20:00:32 +00:00
tests	clippy: Disallow len_without_is_empty and len_zero	2023-05-22 21:27:21 +00:00
Cargo.toml	Update bitflags dependency to 2.2.1.	2023-04-27 17:22:36 +00:00
README.md	hypervisor: add contact for windows hypervisors	2023-03-14 18:22:46 +00: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

KVM is crosvm's preferred hypervisor for Linux.

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