mirrors/crosvm
1
0
Fork 0
mirror of https://chromium.googlesource.com/crosvm/crosvm synced 2024-11-24 20:48:55 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
crosvm/hypervisor
History
Daniel Verkamp 32ed310b9e hypervisor: kvm: check CAP_KVMCLOCK_CTRL once per VM 
Retrieve the kvmclock capability once in KvmVm::new() instead of
checking it in each call to create_kvm_vcpu().

BUG=None
TEST=tools/dev_container tools/presubmit

Change-Id: I4acf3fbd68999a7b4aa517553b6684f27629e0e9
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5671241
Reviewed-by: Frederick Mayle <fmayle@google.com>
Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
2024-07-08 20:13:24 +00:00
..
hypervisor_test_macro
src hypervisor: kvm: check CAP_KVMCLOCK_CTRL once per VM 2024-07-08 20:13:24 +00:00
tests hypervisor: kvm: get vcpu mmap size at startup 2024-07-08 20:10:34 +00:00
Cargo.toml
README.md

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

  • Platforms: Linux
  • Tested upstream: yes

KVM is crosvm's preferred hypervisor for Linux.

WHPX

HAXM

Android Specific

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

Geniezone

Gunyah