commit | 4387a66d077d094ab4fba0a4d89b020d19f4f40f | [log] [tgz] |
---|---|---|
author | Elie Kheirallah <khei@google.com> | Thu Oct 19 19:34:06 2023 +0000 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Oct 19 23:14:01 2023 +0000 |
tree | 1fa663efb478e1e5506faf7c3f9dbfe349531fdc | |
parent | afe25df1be077a951a36f0359f22ad98b9ced343 [diff] |
docs: add log levels to advanced_usage Add details on how to change log levels in crosvm. BUG=N/A TEST=mdbook build Change-Id: I2ded0d14c5df9bf2032d8e4fb0896882c754fda5 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4956179 Reviewed-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> 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 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.