commit | 341a4a6f4fbd430f2041a61eceeab0de8dc863fb | [log] [tgz] |
---|---|---|
author | Frederick Mayle <fmayle@google.com> | Mon Mar 13 19:14:09 2023 -0700 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Mar 14 18:22:46 2023 +0000 |
tree | 48eb43231d8faaa2c9c46967dd0cc22e6e215075 | |
parent | 050bc6355678e4fecc411d78ebba28766f20b50f [diff] |
hypervisor: add contact for windows hypervisors Change-Id: I9288e2cf73996dd7c02e0e870a9c9265acba1dfd Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4335694 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Frederick Mayle <fmayle@google.com> Auto-Submit: Frederick Mayle <fmayle@google.com>
crosvm is a virtual machine monitor (VMM) based on Linux’s KVM hypervisor, with a focus on simplicity, security, and speed. crosvm is intended to run Linux guests, originally as a security boundary for running native applications on the ChromeOS platform. Compared to QEMU, crosvm doesn’t emulate architectures or real hardware, instead concentrating on paravirtualized devices, such as the virtio standard.
crosvm is currently used to run Linux/Android guests on ChromeOS devices.