How to use Linux vsock for fast VM communication

Post by mananaysiempre » Sat, Nov 29, 2025, 1:22 PM UTC

Veserv wrote: post #11

rwmj wrote: post #3

Earlier quoted context omitted.

vsock is pretty widely used, and if you're using virtio-vsock it should be reasonably fast. Anyway if you want to do some quick benchmarks and have an existing Linux VM on a libvirt host: (1) 'virsh edit' the guest and check it has ' ' in the section of the XML. (2) On the host: $ nbdkit memory 1G --vsock -f (3) Inside the guest: $ nbdinfo 'nbd+vsock://2' (You should see the size being 1G) And then you can try using…

Thank you for benchmarking. 2.5x slower than what they were replacing. Demanding evidence for claims strikes again.

Careful that VSOCK is an abstraction for disparate VM-to-host transports. GP only measured on KVM so if you run e.g. ESXi you’ll need to do your own benchmarks.

Post by txdv » Sat, Nov 29, 2025, 2:44 PM UTC

dymk wrote: post #17

This is a weird article. It’s titled “how to use vsock” but 95% is how to set up Bazel, gRPC, and building a C++ project. And then 5% is a link to an off-site Twitter thread of screenshots for setting up a Linux VM image and running that in qemu. This should have been a VM with a basic server and socat’ing the vsocket. I don’t know why so much space was dedicated to unrelated topics. Also zero qualifications or bench…

> This is a weird article. It’s titled “how to use vsock” but 95% is how to set up Bazel, gRPC, and building a C++ project.

This is just what happens when you use bazel to quickly set up your project.

Re: How to use Linux vsock for fast VM communication

Re: How to use Linux vsock for fast VM communication