commit | d4bfea4bb995533cc2516dc1e73a2d299a6a7357 | [log] [tgz] |
---|---|---|
author | Andrew Walbran <qwandor@google.com> | Wed May 04 15:19:20 2022 +0100 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri May 06 12:09:40 2022 +0000 |
tree | 8be3f004706186cd4f39901a7f665975eee79d01 | |
parent | 5807bd9d8054403662478e8688355eee5c225a64 [diff] |
Document memory layout. Change-Id: I3ddd6b355a77527063886065ab2c576364709fc0 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3627453 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Auto-Submit: Andrew Walbran <qwandor@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Andrew Walbran <qwandor@google.com>
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.