mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2025-01-30 13:44:47 +00:00
No description
42b3e8da55
The compiler was complaining about std::fmt::Debug being an unused import. Remove the import. BUG=none TEST=build_test and see no warnings about unused imports Change-Id: I5e606982dffee575b3048b6c45cb5222e63ae3dc Signed-off-by: Chirantan Ekbote <chirantan@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/669305 Reviewed-by: Jason Clinton <jclinton@chromium.org> Reviewed-by: Stephen Barber <smbarber@chromium.org> Reviewed-by: Dylan Reid <dgreid@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> |
||
---|---|---|
data_model | ||
io_jail | ||
kernel_loader | ||
kvm | ||
kvm_sys | ||
net_sys | ||
net_util | ||
seccomp/x86_64 | ||
src | ||
sys_util | ||
syscall_defines | ||
vhost | ||
virtio_sys | ||
x86_64 | ||
.gitignore | ||
build_test | ||
build_test.py | ||
Cargo.toml | ||
LICENSE | ||
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 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.
Usage
Currently there is no front-end, so the best you can do is run cargo test
in
each crate.