commit | cd0e7edcc75f3caf94f6df17b08d762c96f02901 | [log] [tgz] |
---|---|---|
author | Kameron Lutes <kalutes@google.com> | Mon Apr 04 22:25:53 2022 +0000 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Apr 06 23:58:34 2022 +0000 |
tree | 8096a60c0b68b7c356c17840d6b105ab63e12123 | |
parent | 7b7a20620f900bf7ce1addf1f473c3331452ff7e [diff] |
Docs: Fix kernel config build steps ChromeOS moved to using split config, so update the build steps for a custom kernel to reflect the new procedure. BUG=b:228107412 TEST=Follow the custom kernel rootfs steps with the new config steps Change-Id: Ib8f7d8748897fb6b907d0da4c25e2cccba1c5954 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3570172 Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Kameron Lutes <kalutes@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.