You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This crate implements the vfio-user protocol which allows the running of devices in a separate process. It is to VFIO what vhost-user is to virtio.
Why is this crate relevant to the rust-vmm project?
This crate is currently part of Cloud Hypervisor and is mature. It could be used for other VMMs that want to move device emulation to another process to enhance security. Currently only the client support is available but support for writing vfio-user devices can be added.
The text was updated successfully, but these errors were encountered:
@andreeaflorescu I'd rather not put it in there since it's really unrelated to vfio use cases. I also don't really want to burden the CODEOWNERS for that repository for something that is only related by name (well, it does share some of the datastructures from vfio-bindings but I think that's more for convenience.) Also I think there is probably scope for there to be potentially multiple crates in the same vfio_user workspace as there is both client and server support plus also potentially a test device.
Crate Name
vfio_user
Short Description
This crate implements the vfio-user protocol which allows the running of devices in a separate process. It is to VFIO what vhost-user is to virtio.
Why is this crate relevant to the rust-vmm project?
This crate is currently part of Cloud Hypervisor and is mature. It could be used for other VMMs that want to move device emulation to another process to enhance security. Currently only the client support is available but support for writing vfio-user devices can be added.
The text was updated successfully, but these errors were encountered: