commit | d1656dbb4be8dc91c21af00151f446449c79683e | [log] [tgz] |
---|---|---|
author | Dmitrii Merkurev <dimorinny@google.com> | Thu Feb 29 00:10:58 2024 +0000 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Feb 29 00:28:26 2024 +0000 |
tree | a242f547468d4adee57f9e645399f4d04d4b46e0 | |
parent | bff79c00ecb5864ef6d7fe30c56fac4b63902e56 [diff] |
crosvm: support passing pci address for virtio-block devices BUG=b:218364216 BUG=b:322862402 TEST=cuttlefish virtio-block devices assigned on the proper address TEST=cargo test Change-Id: I81a865d3fe7485ff12c96f485077decbfce89e17 Signed-off-by: Dmitrii Merkurev <dimorinny@google.com> Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5331680 Reviewed-by: 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 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.