|author||Dmitry Torokhov <firstname.lastname@example.org>||Sat Jun 18 01:31:35 2022|
|committer||Chromeos LUCI <email@example.com>||Sat Jul 02 19:33:21 2022|
devices: vvu: do not try to change driver for VVU devices It is not the task of crosvm, which is usually unprivileged process, to mess up with the system configuration, so it should simply expect that VVU devices are already bound to vfio-pci driver and stop trying to do it itself. BUG=b:196186396 TEST=Boot redrix-manatee, start crostini. Change-Id: Icb777cf66fd54bd74d656821fb76587c7ee70ca3 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3712552 Commit-Queue: Dmitry Torokhov <firstname.lastname@example.org> Tested-by: kokoro <email@example.com> Reviewed-by: Keiichi Watanabe <firstname.lastname@example.org> Reviewed-by: David Stevens <email@example.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 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.