On Wed, Aug 17, 2022 at 01:53:32PM -0400, Michael S. Tsirkin wrote:

On Tue, Aug 16, 2022 at 11:08:26AM +0000, Bobby Eshleman wrote:

quoted

On Wed, Aug 17, 2022 at 01:02:52PM -0400, Michael S. Tsirkin wrote:

quoted

On Tue, Aug 16, 2022 at 09:42:51AM +0000, Bobby Eshleman wrote:

quoted

quoted

The basic question to answer then is this: with a net device qdisc
etc in the picture, how is this different from virtio net then?
Why do you still want to use vsock?

When using virtio-net, users looking for inter-VM communication are
required to setup bridges, TAPs, allocate IP addresses or setup DNS,
etc... and then finally when you have a network, you can open a socket
on an IP address and port. This is the configuration that vsock avoids.
For vsock, we just need a CID and a port, but no network configuration.

Surely when you mention DNS you are going overboard? vsock doesn't
remove the need for DNS as much as it does not support it.

Oops, s/DNS/dhcp.

That too.

Sure, setting up dhcp would be overboard for just inter-VM comms.

It is fair to mention that vsock CIDs also need to be managed /
allocated somehow.