commit | 48e123b8225d39673e409455e07d3860a250d007 | [log] [tgz] |
---|---|---|
author | Daniel Verkamp <dverkamp@chromium.org> | Thu May 16 18:03:40 2024 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri May 17 19:06:52 2024 |
tree | 32a73c9efb3d19d3d0103a0238256b50623fdab2 | |
parent | 7794aae9ef368e15251eadea44f33433e203df0d [diff] |
cmdline: add helper to generate /dev/vdX and /dev/sdX The new function also handles more than 26 block devices rather than erroring out (or silently generating incorrect names) in this case. BUG=None TEST=cargo test TEST=crosvm run with `--block ...,root=true` Change-Id: I025cc33251d40a37907891a5121f9c03a36a2f7b Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5545758 Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Richard Zhang <rizhang@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.