commit | e2c523666180ec56a3408357a77178f5a09f4631 | [log] [tgz] |
---|---|---|
author | Frederick Mayle <fmayle@google.com> | Mon Mar 27 15:09:30 2023 -0700 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Mar 28 20:54:02 2023 +0000 |
tree | b1729ade8fdd5868d5ba540a5d2ff7d7abbb4d4b | |
parent | e2f52863d76702ceb0477926f750186bce2477b0 [diff] |
crosvm: restore vCPUs during "cold restore" We only restored the devices before. BUG=b:269174485 Change-Id: I524c055fcdbed6c8cac4b1e3bfe280ba368c3b37 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4375647 Commit-Queue: Frederick Mayle <fmayle@google.com> Reviewed-by: Elie Kheirallah <khei@google.com> Reviewed-by: Noah Gold <nkgold@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.