No description
Find a file
Stephen Barber 2cfc2056aa crosvm: add vhost_net virtio device
vhost_net is an in-kernel implementation of a virtio_net device. This device
implementation is responsible only for negotiating features and setting up
vhost_net to point to the virtqueues in the guest.

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

BUG=chromium:738639
TEST=boot with networking enabled and ping host

Change-Id: I9192765b9348528a8a7a7f273e9522c2373d22fb
Reviewed-on: https://chromium-review.googlesource.com/538106
Commit-Ready: Stephen Barber <smbarber@chromium.org>
Tested-by: Stephen Barber <smbarber@chromium.org>
Reviewed-by: Zach Reizner <zachr@chromium.org>
2017-07-20 03:05:17 -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: add vhost_net virtio device 2017-07-20 03:05:17 -07:00
sys_util sys_util: add get_host_address for GuestMemory 2017-07-19 16:26:59 -07:00
syscall_defines
vhost vhost: add crate for interacting with vhost net 2017-07-20 03:05:17 -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: add vhost_net virtio device 2017-07-20 03:05:17 -07:00
LICENSE
net_device.policy crosvm: add vhost_net virtio device 2017-07-20 03:05:17 -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.