commit | a24a752708585f98d950a764af917471350290ea | [log] [tgz] |
---|---|---|
author | Andrew Walbran <qwandor@google.com> | Wed Feb 09 18:23:00 2022 +0000 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Feb 10 10:04:55 2022 +0000 |
tree | a8ff677a09b0b6a004599d18a1556171535dad2b | |
parent | 67d4219489a3914acf0b9796d8f7bbc368cc835d [diff] |
Disable RNG device for protected VMs. They can't trust the host to provide entropy, so there's no point providing it. BUG=b:217506382 TEST=tools/dev_container tools/run_tests TEST=tools/dev_container tools/run_tests --target=vm:aarch64 Change-Id: I5355e846191d34e10c0c5c3cf0b2afaa3c779313 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3450875 Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Andrew Walbran <qwandor@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 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.