mirrors/crosvm
1
0
Fork 0
mirror of https://chromium.googlesource.com/crosvm/crosvm synced 2025-01-30 04:19:20 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
No description
61 commits 607 branches 2 tags 235 MiB
Rust 95.5%
Python 2%
C 1.7%
Shell 0.5%
Find a file
Stephen Barber 8686d9ff5b crosvm: refactor mmio device setup 
In preparation for adding a net device, factor out some of the common code
for setting up an mmio device and jailing it.

Signed-off-by: Stephen Barber <smbarber@chromium.org>

BUG=none
TEST=cargo test

Change-Id: I94f02e56a2b0938d860322b731d8b17a25357128
Reviewed-on: https://chromium-review.googlesource.com/543910
Commit-Ready: Stephen Barber <smbarber@chromium.org>
Tested-by: Stephen Barber <smbarber@chromium.org>
Reviewed-by: Zach Reizner <zachr@chromium.org>
2017-07-13 22:03:30 -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
kvm_sys
src crosvm: refactor mmio device setup 2017-07-13 22:03:30 -07:00
sys_util sys_util: syslog - Scope access from within macros 2017-07-13 19:46:09 -07:00
syscall_defines
x86_64 Limit types that can be read from guest memory 2017-06-27 00:20:33 -07:00
.gitignore
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
README.md crosvm: Add crosvm main program 2017-07-05 21:54:52 -07:00

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_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.