mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2025-01-30 04:19:20 +00:00
No description
56077cf863
Problems that were fixed:
- gcc crate deprecated compile_library
- `cargo test -p kvm` had a compile error
- `cargo test -p kvm_sys` failed to link with libc
- main.rs failed to include `getpid` and had dead code
- fork.rs had a warning in `cargo test -p sys_util`
- unused const in serial.rs
BUG=None
TEST=sudo cargo test -p data_model -p io_jail -p kernel_loader -p kvm \
-p kvm_sys -p net_sys -p net_util -p syscall_defines -p sys_util \
-p virtio_sys -p vhost -p x86_64 -p crosvm
Change-Id: Iaf0389013fbcdfbfaa7cf37ea1a1fc045f480ada
Reviewed-on: https://chromium-review.googlesource.com/642509
Commit-Ready: Zach Reizner <zachr@chromium.org>
Tested-by: Zach Reizner <zachr@chromium.org>
Reviewed-by: Jason Clinton <jclinton@chromium.org>
Reviewed-by: Stephen Barber <smbarber@chromium.org>
|
||
|---|---|---|
| data_model | ||
| io_jail | ||
| kernel_loader | ||
| kvm | ||
| kvm_sys | ||
| net_sys | ||
| net_util | ||
| seccomp/x86_64 | ||
| src | ||
| sys_util | ||
| syscall_defines | ||
| vhost | ||
| virtio_sys | ||
| x86_64 | ||
| .gitignore | ||
| 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_loaderLoads elf64 kernel files to a slice of memory.kvm_syslow-level (mostly) auto-generated structures and constants for using KVMkvmunsafe, low-level wrapper code for using kvm_syscrosvmthe top-level binary front-end for using crosvmx86_64Support 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.