commit | a364040b4b0fff718d9ac1cc3254994f80825ed5 | [log] [tgz] |
---|---|---|
author | Daniel Verkamp <dverkamp@chromium.org> | Wed Oct 19 14:47:16 2022 -0700 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Oct 20 21:10:14 2022 +0000 |
tree | 6e6148e29c5e3aba42da540a8c0604bda8d98840 | |
parent | 28d0f6785825a72abdabd9690094002604baf51d [diff] |
base: fix WaitContext doc tests BUG=b:231344063 TEST=cargo test -p base -- --test-threads=1 Change-Id: Icf4dc6228eadb41aacbb49844089b1cadb6c5b5e Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3966481 Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Frederick Mayle <fmayle@google.com> Reviewed-by: Noah Gold <nkgold@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.