search for: supports_vsock

...2); > "connect_socket", (1, 2); > "aio_connect_socket", (1, 2); > + "connect_vsock", (1, 2); > + "aio_connect_vsock", (1, 2); > As this is Linux-only (and for that matter, depends on kernel vsock support), we probably need "supports_vsock" as an additional function. > +++ b/generator/states-connect.c > @@ -37,6 +37,10 @@ > #include <sys/socket.h> > #include <sys/un.h> > > +#ifdef HAVE_LINUX_VM_SOCKETS_H > +#include <linux/vm_sockets.h> > +#endif > + > /* Disable Nagle...

...t;connect_socket", (1, 2); > > "aio_connect_socket", (1, 2); > >+ "connect_vsock", (1, 2); > >+ "aio_connect_vsock", (1, 2); > > As this is Linux-only (and for that matter, depends on kernel vsock > support), we probably need "supports_vsock" as an additional > function. We could add it, but equally client code can just check AF_VSOCK the same way that libnbd does, ie with a configure test for the header and checking if AF_VSOCK is defined. > >+++ b/generator/states-connect.c > >@@ -37,6 +37,10 @@ > > #incl...

This is a series of patches to libnbd and nbdkit adding AF_VSOCK support. On the host side it allows you to start an nbdkit instance which listens on a virtio-vsock socket: $ ./nbdkit -fv --vsock memory 1G ... nbdkit: debug: bound to vsock 2:10809 On the guest side you can then use libnbd to connect to the server: $ ./run nbdsh -c 'h.connect_vsock(2, 10809)' -c