commit | eb1c95693f1382bff51f6c3743952ecfaae4275d | [log] [tgz] |
---|---|---|
author | Elliot Berman <quic_eberman@quicinc.com> | Tue Mar 14 09:56:52 2023 -0700 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Apr 05 18:32:18 2023 +0000 |
tree | efe7e226d28b57111790a098412407a1e0edc908 | |
parent | c01aa9507a01d2d1a02c744be24eb63273e22fef [diff] |
hypervisor: aarch64: Add init_vm Gunyah initializes at VM level, not the vCPU level as KVM. Add VM-generic initialization which happens after build_vm, but before the VM starts to run. BUG=b:232360323 Change-Id: Iea38cf63eca9b525e613450fd7bca2d422923063 Signed-off-by: Elliot Berman <quic_eberman@quicinc.com> Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4400669 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.