commit | f2c9d99b8fe0a71c70df4339e00425464db81739 | [log] [tgz] |
---|---|---|
author | Maciek Swiech <drmasquatch@google.com> | Thu Mar 02 15:03:10 2023 -0700 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Mar 03 22:17:28 2023 +0000 |
tree | 23dab2e962c39512979215a774075ca0041dc78a | |
parent | 9625125386cab45f29168829c2db9b90dfbd0259 [diff] |
tools/examples: remove --disable-sandbox from example most features (especially for a simple run) should work without requiring the sandbox to be disabled so we can remove that option from the example command to run crosvm. BUG=none TEST=run the example Change-Id: I7455062b9745fe520dccf2b54d55ec78109ff9a3 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4303079 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Auto-Submit: Maciek Swiech <drmasquatch@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 ChromeOS 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 ChromeOS devices.