commit | b5e861fc69f35f9dd01207ab31d58606e5d5737d | [log] [tgz] |
---|---|---|
author | Alexandre Courbot <acourbot@chromium.org> | Wed Aug 03 12:23:20 2022 +0900 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Aug 12 18:05:03 2022 +0000 |
tree | 56e4b2f44a70f74b818fc04023e4942377c2c3fe | |
parent | 96e98ef88299570f66f207d70bb7b29e0cdeb4b5 [diff] |
crosvm: rename DevicesSubcommand to DeviceSubcommand DevicesSubcommand was for the `device` command, so rename it to avoid confusion with the `devices` one. BUG=b:217480043 TEST=cargo build Change-Id: I4c321ff61a71d0ca731b23951d583beb9ce5d46c Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3827603 Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Tested-by: Alexandre Courbot <acourbot@chromium.org> Auto-Submit: Alexandre Courbot <acourbot@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.