commit | d0b91ab0bef734cdcb14d660151a9ce008b65fce | [log] [tgz] |
---|---|---|
author | Noah Gold <nkgold@google.com> | Wed May 18 21:41:33 2022 -0700 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri May 20 04:24:43 2022 +0000 |
tree | 91e63037a91f264b1f916f12750898097e9b4f29 | |
parent | 6c291239afdfa788aac5023ad7add76328dcaa48 [diff] |
vm_memory: upstream Windows support Note that in tests, memory addresses were adjusted so that they work with mmap allocation on Windows (the previous addresses/sizes were too small; see `dwAllocationGranularity` at https://docs.microsoft.com/en-us/windows/win32/api/sysinfoapi/ns-sysinfoapi-system_info). TEST=builds BUG=b:213153154 Change-Id: I8ccecbf34b9f9799194447e04d69eb2ee3bf69b4 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3652703 Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Noah Gold <nkgold@google.com> 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 Chrome OS 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 Chrome OS devices.