No description
Find a file
Stephen Barber a00753ba37 crosvm: clean up waiting for children
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>
2017-07-18 23:48:37 -07:00
data_model data_model: add volatile_memory module for volatile access 2017-06-27 10:55:45 -07:00
io_jail io_jail: add bind mount 2017-06-30 22:24:50 -07:00
kernel_loader kernel_loader: Fix clippy warnings. 2017-06-30 22:24:49 -07:00
kvm sys_util: add ioctl module 2017-07-13 22:03:30 -07:00
kvm_sys sys_util: add ioctl module 2017-07-13 22:03:30 -07:00
net_sys net_sys: add crate for tap interface ioctl bindings 2017-07-13 22:03:30 -07:00
net_util net_util: add crate for creating/configuring tap interfaces 2017-07-13 22:03:30 -07:00
src crosvm: clean up waiting for children 2017-07-18 23:48:37 -07:00
sys_util sys_util: add ioctl module 2017-07-13 22:03:30 -07:00
syscall_defines syscall_defines: Add linux syscall defines. 2017-05-29 21:49:05 -07:00
virtio_sys virtio_sys: add crate for virtio/vhost ioctl bindings 2017-07-13 22:03:31 -07:00
x86_64 Limit types that can be read from guest memory 2017-06-27 00:20:33 -07:00
.gitignore gitignore: Remove Cargo.lock 2017-06-17 01:12:44 -07:00
block_device.policy crosvm: Put block device process in a minijail 2017-07-06 21:13:55 -07:00
Cargo.toml crosvm: use sys_util::clone_process to create proxy device 2017-07-13 11:44:36 -07:00
LICENSE add LICENSE and README 2017-04-17 14:06:21 -07:00
README.md crosvm: Add crosvm main program 2017-07-05 21:54:52 -07: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:

  • 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
  • crosvm the top-level binary front-end for using crosvm
  • x86_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.