| commit | 88f9cba448ff7f1cd61c8bf66e34772132a8663f | [log] [tgz] |
|---|---|---|
| author | Chirantan Ekbote <chirantan@chromium.org> | Mon Aug 28 09:51:18 2017 -0700 |
| committer | chrome-bot <chrome-bot@chromium.org> | Mon Sep 18 16:48:43 2017 -0700 |
| tree | be3a916b0991914a841ef51cbc487e07dacacf89 | |
| parent | 270f7b6a16a1c0475da061d5ecb344db10306a64 [diff] |
Implement virtio-vsock Implement the virtual sockets device using vhost subsystem of the host kernel to handle data transfer. BUG=chromium:708267 TEST=build and run maitred in guest VM without issue Change-Id: I35b542c0fc7e0fd9296f7ba3e1dfce60bf524d15 Signed-off-by: Chirantan Ekbote <chirantan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/638838 Reviewed-by: Stephen Barber <smbarber@chromium.org>
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.
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 KVMkvm unsafe, low-level wrapper code for using kvm_syscrosvm the top-level binary front-end for using crosvmx86_64 Support code specific to 64 bit intel machines.Currently there is no front-end, so the best you can do is run cargo test in each crate.