commit | d220083da9df25de3e8a6df8544854ce4c5f8ad0 | [log] [tgz] |
---|---|---|
author | Kameron Lutes <kalutes@google.com> | Wed Jun 22 05:15:10 2022 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jun 24 04:55:42 2022 |
tree | 3fd51016ed3d1326a4d68956cea29cf305e6e68d | |
parent | 8297d745c6f08a2a6afd40452c5d12c6545cad6a [diff] |
crosvm: Add documentation for crosvm_control Adds documentation and best practices for the crosvm_control library. BUG=b:188858559 TEST=cq Change-Id: I8b03b9b78e72e0d47489d145476e33aa4310fef2 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3717537 Reviewed-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Kameron Lutes <kalutes@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.