commit | 18d435aa17186dd30385d231cc855d06d30d520e | [log] [tgz] |
---|---|---|
author | Elie Kheirallah <khei@google.com> | Wed Jul 27 00:18:49 2022 +0000 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jul 27 20:54:20 2022 +0000 |
tree | 068387a4c63dd71f49f5822cfdc9e771fd231bc2 | |
parent | 11812a5bf92a9cd98c6ff2a9adf6a577f2ded091 [diff] |
Updating documentation for building crosvm. Updating set_test_target to test_target. Highlighting part that mentions running instructions inside the container. Bug=b:240336174 Test=None Change-Id: I61efe14de02fe0fd98bd677a1cd8198b9085c6c7 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3788728 Reviewed-by: Dennis Kempin <denniskempin@google.com> Tested-by: Elie Kheirallah <khei@google.com> Commit-Queue: Elie Kheirallah <khei@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.