2017-04-14 23:54:03 +00:00
|
|
|
# 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:
|
|
|
|
|
|
2017-05-02 00:57:18 +00:00
|
|
|
* `kernel_loader` Loads elf64 kernel files to a slice of memory.
|
|
|
|
|
* `kvm_sys` low-level (mostly) auto-generated structures and constants for using KVM
|
|
|
|
|
* `kvm` unsafe, low-level wrapper code for using kvm_sys
|
2017-04-14 23:54:03 +00:00
|
|
|
* `crosvm` the top-level binary front-end for using crosvm
|
2017-05-02 00:57:18 +00:00
|
|
|
* `x86_64` Support code specific to 64 bit intel machines.
|
2017-04-14 23:54:03 +00:00
|
|
|
|
|
|
|
|
## Usage
|
|
|
|
|
|
|
|
|
|
Currently there is no front-end, so the best you can do is run `cargo test` in
|
|
|
|
|
each crate.
|
