On Tue, 2022-03-29 at 16:50 +0200, Johannes Berg wrote:
Or perhaps you are implying that hw/virtio/vhost-user-i2c* in QEMU are not strictly needed?
I _thought_ that was the case, but honestly, that was just from reading about it, not looking at the code. Thinking about it though, I don't need special glue in UML, just passing the device ID on the command line? So not sure what they need the glue for. Looking at the code, it's not really much though? Not sure, I guess you need somebody more familiar with qemu here, sorry.
So here https://www.qemu.org/docs/master/system/devices/vhost-user.html#vhost-user-d...
the docs say:
These are simple stub devices that ensure the VirtIO device is visible to the guest. The code is mostly boilerplate although each device has a chardev option which specifies the ID of the --chardev device that connects via a socket to the vhost-user daemon.
So maybe if the ID were specified via the command line too, you could have a generic vhost-user stub in qemu?
johannes