crosvm: cmdline: convert bools to Option<bool> in RunCommand We recently enabled configuration files with the limitation that only one file could be specified, and configuration files cannot include further files. This limitation was due to the fact that the argh crate could not handle Option<bool> as switches, which forced us to use bool, which cannot be merged unambiguously more than once. argh 0.1.10 now allows to use Option<bool> for switches, which will allow us to lift these limitations. Start by converting all bools in RunCommand into Option<bool>, and mandating that all members of RunCommand are either Option or Vec. Following CLs will implement the features that doing so enables. BUG=b:218223240 TEST=presubmit Change-Id: Ica19c94b9509aec7145a6af954d3ebe04a73bc3d Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4414502 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Alexandre Courbot <acourbot@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.
