1# Hypervisor Support 2 3Multiple hypervisor backends are supported. See 4[Advanced Usage](running_crosvm/advanced_usage.md#hypervisor) for overriding the default backend. 5 6Hypervisors added to crosvm must meet the following requirements: 7 8- Hypervisor code must be buildable in crosvm upstream. 9 - Within reason, crosvm maintainers will ensure the hypervisor's code continues to build. 10- Hypervisors are not required to be tested upstream. 11 - We can't require testing upstream because some hypervisors require specialized hardware. 12 - When not tested upstream, the hypervisor's maintainers are expected to test it downstream. If a 13 change to crosvm breaks something downstream, then the hypervisor's maintainers are expected to 14 supply the fix and can't expect a revert of the culprit change to be accepted upstream. 15 16## KVM 17 18- Platforms: Linux 19- Tested upstream: yes 20 21KVM is crosvm's preferred hypervisor for Linux. 22 23## WHPX 24 25- Platforms: Windows 26- Tested upstream: no 27- Contacts: [email protected] 28 29## HAXM 30 31- Platforms: Windows 32- Tested upstream: no 33- Contacts: [email protected] 34 35## Android Specific 36 37The hypervisors in this section are used as backends of the 38[Android Virtualization Framework](https://source.android.com/docs/core/virtualization). 39 40### Geniezone 41 42- Platforms: Linux, aarch64 only 43- Tested upstream: no 44- Contacts: [email protected], [email protected] 45 46### Gunyah 47 48- Platforms: Linux, aarch64 only 49- Tested upstream: no 50- Contacts: [email protected], [email protected], [email protected], 51 [email protected] 52