commit | 4bb58649839f21d089485996e51fd5cbf2c0a539 | [log] [tgz] |
---|---|---|
author | Jiyong Park <jiyong@google.com> | Wed Oct 23 17:24:03 2024 +0900 |
committer | Jiyong Park <jiyong@google.com> | Thu Oct 24 10:40:50 2024 +0900 |
tree | 470c7d07127a6e4c0a2aa8aa2bcc95c5cb15a4b8 | |
parent | 1fbb3b79859b162a478827854e7b31a5620efdb7 [diff] |
Add --name option to the run command It is used to optionally set the name of the VM. It can be useful when there are multiple crosvm processes running and we want to distinguish them. This is especially a must in Android which uses process name for the resource attribution purpose. BUG=b/375094126 TEST=tools/dev_container tools/presubmit Test: ditto Change-Id: Id4af3b8f2b216ad3239a4467a0c30a4630d44a73 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5955889 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Jiyong Park <jiyong@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.