commit | 07f769528df2c1cbcde8bc1d48e5e348eeb8f79f | [log] [tgz] |
---|---|---|
author | Daniel Verkamp <dverkamp@chromium.org> | Tue Aug 02 18:17:48 2022 -0700 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Aug 24 19:36:29 2022 +0000 |
tree | 6cca0b81485e3e7d0e9cfd7c69f7993c117ec4d4 | |
parent | 1407290307d56ab9a2805ef20002356857941846 [diff] |
devices: vhost-vsock: improve open error message Include the vhost vsock device path in the error message if opening it fails, and remove the now-redundant file exists check. BUG=None TEST=crosvm run --vhost-vsock-device /does/not/exist ... Change-Id: I1f66c03df8b7b7ad68339b1c151b19ce8fa37a5e Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3806077 Tested-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Alexandre Courbot <acourbot@chromium.org> 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 Chrome OS 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 Chrome OS devices.