commit | 4da1409c03ab03fe978a2089a66923d725948dd4 | [log] [tgz] |
---|---|---|
author | Daniel Verkamp <dverkamp@chromium.org> | Tue Dec 07 16:46:21 2021 -0800 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Mar 17 22:26:55 2022 +0000 |
tree | dad01d1ec4583b8caec73293f544821a7b307c8e | |
parent | 67dc513aa10e848b424b4b0d3f6a65ab0ad6e387 [diff] |
kvm_sys: regenerate x86 and aarch64 bindings BUG=b:218388029 TEST=tools/presubmit --quick Change-Id: Iac652e043575f5c16acf4da5101dd89a15220f33 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3339809 Reviewed-by: Dennis Kempin <denniskempin@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
crosvm is a virtual machine monitor (VMM) based on Linux’s KVM hypervisor, with a focus on simplicity, security, and speed. crosvm is intended to run Linux guests, originally as a security boundary for running native applications on the Chrome OS platform. Compared to QEMU, crosvm doesn’t emulate architectures or real hardware, instead concentrating on paravirtualized devices, such as the virtio standard.
crosvm is currently used to run Linux/Android guests on Chrome OS devices.