mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2024-11-25 05:03:05 +00:00
No description
a00753ba37
Signed-off-by: Stephen Barber <smbarber@chromium.org> BUG=none TEST=run and kill block device process Change-Id: I1a4e98cb1985bfeb2303428f95f3bae27dccf803 Reviewed-on: https://chromium-review.googlesource.com/576463 Commit-Ready: Stephen Barber <smbarber@chromium.org> Tested-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Dylan Reid <dgreid@chromium.org> |
||
---|---|---|
data_model | ||
io_jail | ||
kernel_loader | ||
kvm | ||
kvm_sys | ||
net_sys | ||
net_util | ||
src | ||
sys_util | ||
syscall_defines | ||
virtio_sys | ||
x86_64 | ||
.gitignore | ||
block_device.policy | ||
Cargo.toml | ||
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:
kernel_loader
Loads elf64 kernel files to a slice of memory.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 crosvmx86_64
Support code specific to 64 bit intel machines.
Usage
Currently there is no front-end, so the best you can do is run cargo test
in
each crate.