Replies: 1 comment 1 reply
-
Hello @yanjiew1! The shared memory + inter-VM interrupts are only the base mechanisms to build more complex communication on top, at the guest level, not inside bao. Including virtual networks. Currently, we are working on virtio support with backends in separate virtual machines, which will likely facilitate the construction of virtual networks and virtual switches on a service VM. Nevertheless, if your requirements are just single 1-to-1 communication over a virtual network we have already implemented such a proof-of-concept in the past based on Jailhouse's IVSHMEM-net linux drivers. You can take a look at it in this demo (although this is using a significantly older version of Bao). Let me know if this was any help. Also, if you are available to collaborate on this topic, we could share with you our current virtio support, so you could play around with virtio-net support. |
Beta Was this translation helpful? Give feedback.
-
Hello, I am a CS graduate student at National Taiwan University.
Currently, it seems that the only way for inter-VM communication is to use shared memory and inter-VM interrupts.
I would like to ask whether there are any plans to implement virtual network devices and virtual switch in bao-hypervisor.
Beta Was this translation helpful? Give feedback.
All reactions