commit | c53b40e455dc9935e4cf4ae1eefae227fe3ef8fb | [log] [tgz] |
---|---|---|
author | Christian Blichmann <cblichmann@google.com> | Wed Apr 12 16:07:05 2023 +0200 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Apr 12 16:58:51 2023 +0000 |
tree | c3e1a0f87999e9c019e15e0c9dde92f573854be1 | |
parent | bc9e3310859274d6234680d17ed6f9d3e1d0f9b7 [diff] |
Fix typos found by `common-typos` checker Change-Id: Ie539304c85d0dc54bc1e17892db8bbbfb15b69ef Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4417934 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@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.