mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2024-10-25 13:36:05 +00:00
No description
b4af07af9c
The kernel command line is dynamically built up based on what devices are added and what extra parameters are passed in my the user. The module this CL adds ensures the kernel command line that is built is a valid one. TEST=None BUG=None Change-Id: Ia2b7b9fae7eb29140ae25ab34119d050984f8ef2 Reviewed-on: https://chromium-review.googlesource.com/514689 Commit-Ready: Zach Reizner <zachr@chromium.org> Tested-by: Zach Reizner <zachr@chromium.org> Reviewed-by: Dylan Reid <dgreid@chromium.org> |
||
---|---|---|
data_model | ||
io_jail | ||
kernel_loader | ||
kvm | ||
kvm_sys | ||
src | ||
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.