search for: connect_socket

...#39; to let the nbdkit pass-through wrapper convert vsock from guest into TCP or Unix socket on the host to other host clients that don't know how to do vsock. > @@ -2793,6 +2836,8 @@ let first_version = [ > "aio_connect_systemd_socket_activation", (1, 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 additio...

...erator @@ -96,6 +96,7 @@ type external_event = | CmdConnectTCP (* [nbd_aio_connect_tcp] *) | CmdConnectCommand (* [nbd_aio_connect_command] *) | CmdConnectSA (* [nbd_aio_connect_systemd_socket_activation]*) + | CmdConnectSocket (* [nbd_aio_connect_socket] *) | CmdIssue (* issuing an NBD command *) type location = string * int (* source location: file, line number *) @@ -170,7 +171,8 @@ let rec state_machine = [ CmdConnectUnix, "CONNECT_UNIX.START"; CmdConnectTCP...

For commands with long names and/or short descriptors, you can end up going over 72 characters in the first line of the man page (causing podwrapper to complain). Wrap these lines. --- generator/generator | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/generator/generator b/generator/generator index 7d3f656..ad1cb6b 100755 --- a/generator/generator +++ b/generator/generator

...uest into > TCP or Unix socket on the host to other host clients that don't know > how to do vsock. I'm afraid I don't understand this. > >@@ -2793,6 +2836,8 @@ let first_version = [ > > "aio_connect_systemd_socket_activation", (1, 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&q...

...s, and in OCaml they are also integers but with a > different type. > --- > generator/generator | 72 ++++++++++++++++++++++++++++++++++++--------- > lib/connect.c | 47 +++++++++++++++++++++++++++++ > 2 files changed, 105 insertions(+), 14 deletions(-) > > + "connect_socket", { > + default_call with > + args = [ Fd "sock" ]; ret = RErr; > + permitted_states = [ Created ]; > + shortdesc = "connect directly to a connected socket"; > + longdesc = "\ > +Pass a connected socket (file descriptor) which libnbd wi...

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

...Connect to an NBD server on a Unix domain socket. See also L<nbd_connect_unix(3)>. +=item B<--vsock> CID PORT + +Select vsock mode. Connect to an NBD server on a C<AF_VSOCK> socket. +See also L<nbd_connect_vsock(3)>. + =back =head1 NOTES @@ -294,6 +301,7 @@ L<nbd_connect_socket(3)>, L<nbd_connect_systemd_socket_activation(3)>, L<nbd_connect_tcp(3)>, L<nbd_connect_unix(3)>, +L<nbd_connect_vsock(3)>, L<libguestfs(3)>, L<guestfish(1)>, L<guestmount(1)>, diff --git a/generator/generator b/generator/generator index 54a8eb7..89...