mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2025-01-28 19:29:20 +00:00
No description
71501e0937
This will be used to create temporary directories that are lifetime managed for running jails. Change-Id: I35dfeae76a211c820db090b65baf72277d9e2d8a Signed-off-by: Dylan Reid <dgreid@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/520706 Reviewed-by: Zach Reizner <zachr@chromium.org> |
||
---|---|---|
io_jail | ||
kernel_loader | ||
kvm | ||
kvm_sys | ||
src/hw | ||
sys_util | ||
syscall_defines | ||
x86_64 | ||
.gitignore | ||
LICENSE | ||
README.md |
Chrome OS KVM
This component, known as crosvm, runs untrusted operating systems along with virtualized devices. No actual hardware is emulated. This only runs VMs through the Linux's KVM interface. What makes crosvm unique is a focus on safety within the programming language and a sandbox around the virtual devices to protect the kernel from attack in case of an exploit in the devices.
Overview
The crosvm source code is organized into crates, each with their own unit tests. These crates are:
kvm-sys
low-level (mostly) auto-generated structures and constants for using KVMkvm
unsafe, low-level wrapper code for using kvm-syscrosvm
the top-level binary front-end for using crosvm
Usage
Currently there is no front-end, so the best you can do is run cargo test
in
each crate.