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

History

Daniel Verkamp 7c126bad72 hypervisor: tests: initialize CPUID for KVM KVM was excluded from several tests; these mostly did not work because the test setup code failed to configure CPUID, so the guest vCPUs did not have any CPUID bits enabled. BUG=None TEST=cargo test -p hypervisor Change-Id: I8c42c90a3547c011ab4f62fa94b31d05b0af6d15 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5677667 Reviewed-by: Kaiyi Li <kaiyili@google.com> Reviewed-by: Noah Gold <nkgold@google.com> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>		2024-07-08 17:33:09 +00:00
..
hypervisor_test_macro
src	hypervisor: kvm, gunyah: manage vcpu fd as File	2024-07-03 17:40:07 +00:00
tests	hypervisor: tests: initialize CPUID for KVM	2024-07-08 17:33:09 +00:00
Cargo.toml	Replace memoffset with std::core::offset_of	2024-06-28 22:07:50 +00:00
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

KVM is crosvm's preferred hypervisor for Linux.

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