commit | 970b00fa4d0f29975f116b13ca33fe2be53a801d | [log] [tgz] |
---|---|---|
author | Dennis Kempin <denniskempin@google.com> | Wed Mar 30 15:38:51 2022 -0700 |
committer | Dennis Kempin <denniskempin@google.com> | Mon Apr 18 19:05:49 2022 +0000 |
tree | 387f8dce6af22847a908a8b6763272d931f1b8cd | |
parent | aac461e25e80ddbcf3db2d9791887f56b3991eb2 [diff] |
Add documentation for ChromeOS workflows This change consolidates some of the spread out information about what ChromeOS developers need to know about crosvms differences to other ChromeOS projects. I created a new directory since I would expect a similar guide for AOSP eventually. This also adds more documentation on some of the process changes suggested in go/crosvm-merge-improvements to improve the stability of the merge process. BUG=b:227475914 TEST=None Change-Id: I08111ecd5a937fde22c7d97f342c1cf02f49b02e Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3561886 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Tested-by: kokoro <noreply+kokoro@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.