commit | 0de3bd9f5029195b26dd05451a2467396e56e3df | [log] [tgz] |
---|---|---|
author | Tomasz Nowicki <tn@semihalf.com> | Mon Jul 25 13:43:16 2022 +0000 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri Aug 26 12:22:31 2022 +0000 |
tree | b6fa7b12224bb8fb9e2f12f830b1a02391e0dcc7 | |
parent | 8189007f766e8b9e8fe95ad732764fe1aacdc830 [diff] |
crosvm: unix: Allow to instantiate Virtio MMIO-based devices As an alternative to PCI transport, instantiate Virtio MMIO device. The caller which create Virtio device (and corresponding VirtioDeviceStub) needs to mark device as MMIO type explicitly, otherwise PCI transport is the default choice. BUG=b:189182339 TEST=boot manatee and verify that Virtio PCI devices work properly Change-Id: Id28345f5b004ebd0d8cfeb9ecd2966c3b821a4ea Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3855007 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Tested-by: Tomasz Nowicki <tnowicki@google.com> Commit-Queue: Tomasz Nowicki <tnowicki@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 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.