commit | 1407290307d56ab9a2805ef20002356857941846 | [log] [tgz] |
---|---|---|
author | Daniel Verkamp <dverkamp@chromium.org> | Tue Aug 02 17:19:07 2022 -0700 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Aug 24 19:36:10 2022 +0000 |
tree | 56691c0734a4a07ae3b4f649a5da89bd269bc545 | |
parent | 956dbba2b595368004d069a9e35639356dda2da1 [diff] |
devices: snd: improve open error message Include the path when opening the sound backend device fails. Change-Id: I37ce06c973588bea4676741f8fab17de11a2a7cb Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3806076 Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Tested-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Alexandre Courbot <acourbot@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.