commit | f3df5127f3aef4d0a114c5d0bd3c389a03e0e974 | [log] [tgz] |
---|---|---|
author | Daniel Verkamp <dverkamp@chromium.org> | Wed Nov 17 14:11:18 2021 -0800 |
committer | Commit Bot <commit-bot@chromium.org> | Wed Nov 17 23:01:34 2021 +0000 |
tree | 5ab4272351bd7f7ea004ab5a055ddab05beef812 | |
parent | 9e37f056117c61cbb4f48e5ae4377b076e61a71e [diff] |
third_party/vmm_vhost: switch to our vm_memory crate This won't actually build as-is if the vhost-kern feature was enabled, but since we don't use that feature currently, this unblocks building crosvm without the rust-vmm vm-memory crate. BUG=b:205511695 TEST=emerge-hatch -C vm-memory && emerge-hatch crosvm Change-Id: I614616b38e796e28f13f0bb867e97c3be532305b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3290311 Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Tested-by: kokoro <noreply+kokoro@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.