commit | e0410eb46d8edcec856c493e6cfdc426900907bb | [log] [tgz] |
---|---|---|
author | Daniel Verkamp <dverkamp@chromium.org> | Thu May 16 17:43:58 2024 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri May 17 19:15:04 2024 |
tree | 9db2a70487f9256e9ebd493779c6c96bece62097 | |
parent | 48e123b8225d39673e409455e07d3860a250d007 [diff] |
cmdline: refactor root= option handling Combine the root= kernel parameter handling for virtio-blk and SCSI devices into an iterator chain to simplify checking for duplicate root options and allow easier extensibility. BUG=None TEST=tools/dev_container tools/presubmit Change-Id: I2f3d8982325a6377efe27eb55a86d5367ff6aa81 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5545759 Reviewed-by: Richard Zhang <rizhang@google.com> Commit-Queue: Daniel Verkamp <dverkamp@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 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.