mirrors/crosvm
1
0
Fork 0
mirror of https://chromium.googlesource.com/crosvm/crosvm synced 2025-02-06 02:25:23 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
No description
86 commits 607 branches 2 tags 236 MiB
Rust 95.5%
Python 2%
C 1.7%
Shell 0.5%
Find a file
Stephen Barber 5e77e88062 crosvm: add pure virtio net device 
While vhost_net can provide better performance than a userspace
virtio device, it also requires a kernel module to function. This
also prevents jailing the virtio device, since virtqueue operations
(which necessarily touch guest memory) will be running directly
in the kernel.

Add a userspace virtio net device that can be jailed and works
without vhost support in the kernel.

BUG=chromium:703920
TEST=networking works

Change-Id: I468114b48abd8e30e967ff16329a5dce6a75018f
Signed-off-by: Stephen Barber <smbarber@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/604937
Reviewed-by: Dylan Reid <dgreid@chromium.org>
Reviewed-by: Zach Reizner <zachr@chromium.org>
2017-08-16 07:48:27 -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 InvalidPath error 2017-07-26 16:46:53 -07:00
kernel_loader kernel_loader: Fix clippy warnings. 2017-06-30 22:24:49 -07:00
kvm kvm: add device memory interface to Vm 2017-08-05 22:07:53 -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: implement Read, Write, and Pollable for Tap 2017-08-09 11:47:55 -07:00
src crosvm: add pure virtio net device 2017-08-16 07:48:27 -07:00
sys_util sys_util: add read_slice_at_addr to GuestMemory 2017-08-09 11:47:55 -07:00
syscall_defines syscall_defines: Add linux syscall defines. 2017-05-29 21:49:05 -07:00
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 add LICENSE and README 2017-04-17 14:06:21 -07:00
net_device.policy crosvm: add pure virtio net device 2017-08-16 07:48:27 -07:00
README.md crosvm: Add crosvm main program 2017-07-05 21:54:52 -07:00
rng_device.policy crosvm: Add virtio random 2017-08-10 20:24:09 -07:00
vhost_net_device.policy crosvm: rename Net virtio device to VhostNet 2017-08-09 11:47:55 -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.