| commit | 9195ec9b239f4fd70c64531e6c4fa00774c49c5f | [log] [tgz] |
|---|---|---|
| author | Dylan Reid <dgreid@chromium.org> | Thu May 04 20:52:16 2017 |
| committer | chrome-bot <chrome-bot@chromium.org> | Thu May 18 02:06:31 2017 |
| tree | fb27becb53d5b8b65928f96bad1187114a71992b | |
| parent | 67030be903bb02e51c7690fa6beb8ce57f0b9fa3 [diff] |
kernel_loader: Add loading of 64 bit elf x86 vmlinux Change-Id: I2db4beb983e302216949e5de8b250932aa4810b8 Reviewed-on: https://chromium-review.googlesource.com/485019 Commit-Ready: Zach Reizner <zachr@chromium.org> Tested-by: Zach Reizner <zachr@chromium.org> Tested-by: Dylan Reid <dgreid@chromium.org> Reviewed-by: Zach Reizner <zachr@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:
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 crosvmCurrently there is no front-end, so the best you can do is run cargo test in each crate.