commit | 52c8cee36acade1be0407b530f9f6a228c891192 | [log] [tgz] |
---|---|---|
author | Richard <rizhang@google.com> | Thu Jun 09 23:41:41 2022 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Jan 11 17:49:10 2023 |
tree | 3088f97dfc16b7ec36a37cbbeea9f11f5e08d57c | |
parent | 10e807c701bcd739316a1b8f97a3681bff485fcb [diff] |
devices: virtio: add pvclock device Currently only used on windows, but should be able to work on other platforms. TEST=CQ BUG=b:213149162 Change-Id: Ie2f518b0a5dc7f1b5650b15c76c0fbcfd5eadea6 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4018114 Reviewed-by: Noah Gold <nkgold@google.com> Commit-Queue: Colin Downs-Razouk <colindr@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.