commit | 8d69b30c14726d86a6a063e0a24781bad1c5fc7c | [log] [tgz] |
---|---|---|
author | Daniel Verkamp <dverkamp@chromium.org> | Wed Nov 02 11:20:00 2022 -0700 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Nov 02 20:32:24 2022 +0000 |
tree | 245fa4cca016072531399939afb764297876d762 | |
parent | 3121cbace9e2a5c733bfc00dbaa05f72430e2e82 [diff] |
docs: update book for embedded seccomp The seccomp policy files are no longer needed at runtime since they are embedded in the crosvm binary. BUG=b:235858187 TEST=mdbook build docs/book Change-Id: Ib8220bce01a21bd3b4a1ef749468e12b18377a62 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3999176 Reviewed-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Daniel Verkamp <dverkamp@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.