No description
Find a file
Zach Reizner 1f77a0daa6 sys_util: use libc's openlog to connect to syslog
By using libc's openlog, we can ensure that the internal state of the
libc syslogger is consistent with the syslog module. Minijail will be
able to print to stderr and the syslog in the same way the logging
macros in crosvm do. The FD the syslog module uses is shared with libc
and via `syslog::get_fds`, jailed processes can inherit the needed FDs
to continue logging.

Now that `sys_log::init()` must be called in single threaded process,
this moves its tests to the list of the serially run ones in
build_test.py.

TEST=./build_test
BUG=None

Change-Id: I8dbc8ebf9d97ef670185259eceac5f6d3d6824ea
Reviewed-on: https://chromium-review.googlesource.com/649951
Commit-Ready: Zach Reizner <zachr@chromium.org>
Tested-by: Zach Reizner <zachr@chromium.org>
Reviewed-by: Jason Clinton <jclinton@chromium.org>
Reviewed-by: Dylan Reid <dgreid@chromium.org>
2017-09-06 14:31:06 -07:00
data_model data_model: add copy functions for copying slices in VolatileSlice's 2017-09-01 14:41:52 -07:00
io_jail io_jail: implement Display for Error 2017-09-06 14:31:06 -07:00
kernel_loader kernel_loader: Fix clippy warnings. 2017-06-30 22:24:49 -07:00
kvm fix armv7a and aarch64 build errors and warnings 2017-09-01 12:39:18 -07:00
kvm_sys fix compiler errors and warnings 2017-08-30 13:04:16 -07:00
net_sys net_sys: add crate for tap interface ioctl bindings 2017-07-13 22:03:30 -07:00
net_util fix armv7a and aarch64 build errors and warnings 2017-09-01 12:39:18 -07:00
seccomp/x86_64 sys_util: use libc's openlog to connect to syslog 2017-09-06 14:31:06 -07:00
src sys_util: use libc's openlog to connect to syslog 2017-09-06 14:31:06 -07:00
sys_util sys_util: use libc's openlog to connect to syslog 2017-09-06 14:31:06 -07:00
syscall_defines fix armv7a and aarch64 build errors and warnings 2017-09-01 12:39:18 -07:00
vhost Refactor VhostNet into separate vhost and net pieces 2017-08-28 21:15:36 -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
build_test add build_test script to automate crosvm test running 2017-09-01 12:39:19 -07:00
build_test.py sys_util: use libc's openlog to connect to syslog 2017-09-06 14:31:06 -07:00
Cargo.toml crosvm: argument parsing without clap 2017-09-02 00:18:25 -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.