commit | c81256f2f1eb51debd494f1dc74d2fdb2c04ea60 | [log] [tgz] |
---|---|---|
author | Frederick Mayle <fmayle@google.com> | Mon Sep 11 15:17:55 2023 -0700 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Jan 25 03:16:30 2024 +0000 |
tree | f896f80c6654925a37ee1916ba544806d61b5086 | |
parent | c16b2bf620ffd07aca84c9ecac276056d8462212 [diff] |
rutabaga_gfx: add FFI API for snapshot-restore BUG=b:266514608 Change-Id: I091ca52b5864359b0bb03f7cb3ecbfabe47f8203 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4853266 Commit-Queue: Frederick Mayle <fmayle@google.com> Auto-Submit: Frederick Mayle <fmayle@google.com> Reviewed-by: Gurchetan Singh <gurchetansingh@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
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.