| commit | 61d39ff5a1670b1cb3e060f09bea821f86ca3f9e | [log] [tgz] |
|---|---|---|
| author | Frederick Mayle <fmayle@google.com> | Tue Aug 12 14:11:47 2025 -0700 |
| committer | Frederick Mayle <fmayle@google.com> | Tue Aug 12 14:14:06 2025 -0700 |
| tree | 532eefa3977ec0bee5c09535e724f02afd55d72e | |
| parent | 551c236eb31a2e950e9a8e3eed66db45428ecf22 [diff] |
Revert^4 "ANDROID: arch: fdt: put pvmfw region in /memory node" Revert submission 35017243-revert-34991149-b437198712-JYMYGRVUYU Reason for revert: fixing it Reverted changes: /q/submissionid:35017243-revert-34991149-b437198712-JYMYGRVUYU Bug: 437457525 Change-Id: Ia8b6fb74dabbf7f4030c3caf4a532a5484ecfdd3
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.