commit | ae01cc74ce5064883a4db08f347a9bc0a3896afa | [log] [tgz] |
---|---|---|
author | Wang Ningyuan <ningyuan@google.com> | Thu Sep 07 17:01:41 2023 +0900 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Sun Sep 10 03:26:30 2023 +0000 |
tree | 1650ecbce2957c9147b41953a83ec560fd9a2ded | |
parent | ce6ef2b36ae2057b49403cc4195f55f0c43ad0dd [diff] |
crosvm_control: Add API for add/remove tap device This CL adds the add and remove of tap device to the crosvm_control API. TEST=presubmit tests. BUG=b:294777126 Change-Id: I4d2388bf785b72388ede5245cb6ebbe1f9331b3d Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4846022 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Ningyuan Wang <ningyuan@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 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.