commit | c101f207daa722f6d53295d340e8e336c76e7f92 | [log] [tgz] |
---|---|---|
author | Keiichi Watanabe <keiichiw@chromium.org> | Thu May 19 18:29:15 2022 +0900 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Jun 03 03:11:22 2022 +0000 |
tree | 67372a5da8c05f0ab631e8f0974db0b878d767c9 | |
parent | 3f7932c6b1ea8d8fcfc341aba9cdd34986eb5447 [diff] |
docs: Add a page about block device BUG=b:233174191 TEST=mdbook build Change-Id: I5a52dff7caa7cd151d1ad382be1bd81cb13e1369 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3659817 Reviewed-by: Alexandre Courbot <acourbot@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Keiichi Watanabe <keiichiw@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.