|author||Dylan Reid <email@example.com>||Fri Jun 16 17:45:36 2017|
|committer||chrome-bot <firstname.lastname@example.org>||Sat Jun 17 08:12:44 2017|
gitignore: Remove Cargo.lock Cargo.lock will need to be checked in to ensure reproducible builds. However continue to ignore Cargo.lock in subdirectories as the main Cargo.lock shouls dictate the versions of everything. Change-Id: I448527b3c23bb9de939682ec1a78fd06a2530857 Signed-off-by: Dylan Reid <email@example.com> Reviewed-on: https://chromium-review.googlesource.com/538067 Reviewed-by: Zach Reizner <firstname.lastname@example.org>
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.
The crosvm source code is organized into crates, each with their own unit tests. These crates are:
kvm-syslow-level (mostly) auto-generated structures and constants for using KVM
kvmunsafe, low-level wrapper code for using kvm-sys
crosvmthe top-level binary front-end for using crosvm
Currently there is no front-end, so the best you can do is run
cargo test in each crate.