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
69 commits 607 branches 2 tags 228 MiB
Rust 95.6%
Python 1.9%
C 1.7%
Shell 0.5%
Find a file
Zach Reizner 648a58d248 crosvm: mmio register and queue check fixes 
According to the Virtio specification, all MMIO register access must be
32-bit wide and aligned. However, this restriction is not true in
general for the config space. This change relaxes the restriction for
accesses to config space.

This change also checks that each queue is valid before activating a
device.

TEST=crosvm run
BUG=None

Change-Id: I10228d99992576837ff505aad56fefbc4d8eff78
Reviewed-on: https://chromium-review.googlesource.com/578314
Commit-Ready: Zach Reizner <zachr@chromium.org>
Tested-by: Zach Reizner <zachr@chromium.org>
Reviewed-by: Dylan Reid <dgreid@chromium.org>
2017-07-20 00:37:00 -07:00
data_model
io_jail
kernel_loader
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: mmio register and queue check fixes 2017-07-20 00:37:00 -07:00
sys_util sys_util: add get_host_address for GuestMemory 2017-07-19 16:26:59 -07:00
syscall_defines
virtio_sys virtio_sys: add crate for virtio/vhost ioctl bindings 2017-07-13 22:03:31 -07:00
x86_64
.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

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.