commit | 4aa35862129f4c6155f837b266e0404504c98f95 | [log] [tgz] |
---|---|---|
author | Richard Zhang <rizhang@google.com> | Tue Jun 20 23:53:07 2023 +0000 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Jun 27 01:02:30 2023 +0000 |
tree | 1cddfb5f0d6d224571f34b57a217c1802b6bd523 | |
parent | ce238917cfbbcc476f2dbf3c98a9c403ee49b8b0 [diff] |
vhost-user block: Start non-queue workers with queue handlers, instead of on initialization. This will make this device consistent with the non-vhost user block devices. BUG=b:287515956 TEST=e2e_test snapshot_vhost_user_root passes. presubmits Change-Id: I3b7fc97947fff8a29b17e93a7f406c2873d709a9 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4630193 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Frederick Mayle <fmayle@google.com> Commit-Queue: 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.