commit | 90f281c1fff2fd17e3450ccc154813e226e97593 | [log] [tgz] |
---|---|---|
author | Junichi Uekawa <uekawa@google.com> | Thu May 12 11:18:16 2022 +0900 |
committer | Chromeos LUCI <chromeos-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sat May 14 12:21:02 2022 +0000 |
tree | 2cab0103860fd4aac6c1b3ce77c2908e27d2a508 | |
parent | cc3fcb8e9d070ae505bd24c1f66988b24dd73ba9 [diff] |
crosvm: Use /dev/zero instead of /dev/mem /dev/mem doesn't exist inside the dev_container and test failed because /dev/mem is not there. We don't actually care about what file it is here although it is typically /dev/mem, so use /dev/zero instead. BUG=None TEST=DOCKER=podman ./tools/dev_container cargo build --features=direct Change-Id: Ic07ed6c3bf222c24eea1387028afbeb52e5c8563 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3643357 Commit-Queue: Junichi Uekawa <uekawa@chromium.org> Tested-by: kokoro <noreply+kokoro@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.