commit | 34df9a13cb3261e88f13f3cbbf5450c6902a1787 | [log] [tgz] |
---|---|---|
author | Daniel Verkamp <dverkamp@chromium.org> | Thu Jan 06 15:19:54 2022 -0800 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Jan 07 15:52:04 2022 +0000 |
tree | 0e5b14d898aaaad0db20cdbee30e851ab780b97a | |
parent | e2ff2c41a07ccb048bed42e3843c1b1bdd7115ec [diff] |
Remove empty OWNERS files These directories can just inherit the top-level crosvm OWNERS now. BUG=None TEST=None Change-Id: Iea439e92aac4a03fcf821e4ce715266161209809 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3370743 Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Keiichi Watanabe <keiichiw@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.