mirrors/crosvm
1
0
Fork 0
mirror of https://chromium.googlesource.com/crosvm/crosvm synced 2024-12-28 06:27:13 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
No description
49 commits 607 branches 2 tags 228 MiB
Rust 95.6%
Python 1.9%
C 1.7%
Shell 0.5%
Find a file
Zach Reizner f2164a18bf crosvm: fix serial device panic on write to read-only registers 
There were a few cases of a write into the serial device that would
panic because the registers were read-only. This change simply ignores
those writes instead of raising a panic.

This is also the first bug that was found by cargo-fuzz! Wohoo!

TEST=None
BUG=None

Change-Id: I8b6805617ac3dcfddd0555c1bb394a7bc1a7cf6d
Reviewed-on: https://chromium-review.googlesource.com/518445
Commit-Ready: Zach Reizner <zachr@chromium.org>
Tested-by: Zach Reizner <zachr@chromium.org>
Reviewed-by: Dylan Reid <dgreid@chromium.org>
2017-07-05 21:54:53 -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 guest_memory 2017-05-25 22:51:14 -07:00
kvm_sys kvm-sys: rename to kvm_sys 2017-05-02 05:20:27 -07:00
src crosvm: fix serial device panic on write to read-only registers 2017-07-05 21:54:53 -07:00
sys_util sys_util: add syslog module for logging to syslog 2017-07-05 21:54:50 -07:00
syscall_defines syscall_defines: Add linux syscall defines. 2017-05-29 21:49:05 -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
Cargo.toml crosvm: Add crosvm main program 2017-07-05 21:54:52 -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

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.