Hi Baruch, The virtio_console.* in uvmm translates virtio-console from the VM to L4::Vcon, such that uvmm talks L4::Vcon to wherever this goes. Virtio is not visible outside of uvmm in this case.
l4virtio/include/server/virtio-console is utility code for implementing a device/server side of virtio-console. In uvmm, connecting virtio devices, the virtio-proxy is used for any virtio device, be it console or any other protocol (like net, blk, etc.). So for your use-case, l4virtio/include/server/virtio-console seems the file you want to use. BR, Aam On Thu Dec 25, 2025 at 01:40:08 +0200, Baruch Burstein wrote: > I am looking into implementing a custom backend for a virtio console (I > hope I am using the right terminology. The frontend will be in a VM managed > by uvmm). I found 2 seemingly unrelated parts of the code named > virtio-console, one under uvmm/server/src/virtio_console.[cc|h] and one > under l4virtio/include/server/virtio-console. I am wondering why there are > 2, what the difference is and when to use each one? There generally seem to > be multiple things named virtio* in uvmm/server/src/, > uvmm/server/src/device/, as well as separate repos like the aforementioned > l4virtio or virtio-net. > Thank you in advance for helping clear this up for me _______________________________________________ l4-hackers mailing list -- [email protected] To unsubscribe send an email to [email protected]
