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

History

Daniel Verkamp 7bfa80063b hypervisor: remove kvm crate dependency Duplicate the KvmCap enum and KvmCpuId type alias that were imported from the top-level `kvm` crate in order to drop the hypervisor -> kvm dependency. The `kvm` crate is otherwise only used by the plugin feature, so this removes it from the build in the usual non-plugin case. BUG=None TEST=tools/dev_container tools/presubmit Change-Id: If710c547619f7c2bbff7e0a6eeca7a6aaf19e63c Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5517747 Reviewed-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>		2024-05-07 19:55:57 +00:00
..
src	hypervisor: remove kvm crate dependency	2024-05-07 19:55:57 +00:00
tests	hypervisor: remove kvm crate dependency	2024-05-07 19:55:57 +00:00
Cargo.toml	hypervisor: remove kvm crate dependency	2024-05-07 19:55:57 +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.