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

History

Frederick Mayle 6cc983d3f5 hypervisor: kvm: verify get_all_msrs gets all the MSRs `get_msrs` truncates the vector on partial success. Haven't seen this fail. Adding the check as a precaution. Change-Id: I7c3a4c2408daa9d7a00257ae758da45011a40311 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4515456 Reviewed-by: Elie Kheirallah <khei@google.com> Commit-Queue: Frederick Mayle <fmayle@google.com> Reviewed-by: Noah Gold <nkgold@google.com>		2023-05-10 18:38:24 +00:00
..
src	hypervisor: kvm: verify get_all_msrs gets all the MSRs	2023-05-10 18:38:24 +00:00
tests	hypervisor: kvm: check for KVM_SET_MSRS failures	2023-05-03 20:52:05 +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.