search for: 10809

...ommand> must be +given to specify which NBD server to forward to: =over 4 @@ -71,7 +72,22 @@ This option implies C<shared=true>. =item B<port=>PORT Connect to the NBD server at the remote C<HOST> using a TCP socket. -The optional port parameter overrides the default port (10809). +The optional port parameter overrides the default port (10809), and +may be a 16-bit number or a non-numeric string to look up the +well-known port for a service name. + +=item B<vhost-cid=>CID + +=item B<port=>PORT + +Connect to the NBD server at the given vsock C<CID> (for ex...

...config key and may be omitted in most cases. See L<nbdkit(1)/Magic parameters>. @@ -47,8 +47,10 @@ Connect to the NBD server at the given remote C<HOST> using a TCP socket. =item B<port=>PORT -When B<hostname> is supplied, use B<PORT> instead of the default port -10809. +When B<hostname> or B<vsock_cid> is supplied, use B<PORT> instead of +the default port 10809. For TCP, the port may be a 16-bit number or a +non-numeric string used to look up the well-known port for a service +name; for VSOCK, the port must be a 32-bit number. =item B<exp...

...ch NBD server to forward to: > > =over 4 > > @@ -71,7 +72,22 @@ This option implies C<shared=true>. > =item B<port=>PORT > > Connect to the NBD server at the remote C<HOST> using a TCP socket. > -The optional port parameter overrides the default port (10809). > +The optional port parameter overrides the default port (10809), and > +may be a 16-bit number or a non-numeric string to look up the > +well-known port for a service name. > + > +=item B<vhost-cid=>CID > + > +=item B<port=>PORT > + > +Connect to the NBD s...

...13017 1502 0 10:12 ? 00:00:08 sshd: root at pts/2 root 15622 1502 0 10:45 ? 00:00:00 sshd: root root 16033 1502 1 10:47 ? 00:00:00 sshd: root at pts/3 root 16099 16038 3 10:48 pts/3 00:00:00 grep ssh [root at inet07 ~]# ps -ef | grep 10810 root 10810 10809 0 10:00 pts/1 00:00:00 -bash root 13015 10810 0 10:12 pts/1 00:00:08 ssh inet07 -t -Y tmux || /bin/bash root 16113 16038 0 10:48 pts/3 00:00:00 grep 10810 [root at inet07 ~]# ps -ef | grep 10809 root 10809 1 0 10:00 ? 00:00:03 tmux root 10810 10809 0 10:00 p...

Hello, I would like to switch this dataframe: > k country 1960 1961 1962 1963 99 ARG 7493 7733 7581 7108 246 AUS 10484 10342 10809 11357 295 AUT 7438 7808 7938 8212 393 BDI 587 502 555 608 442 BEL 8223 8638 9021 9311 in this structure: year ARG AUS AUT BDI BEL 1960 7493 10484 7438 587 8223 1961 7733 10342 7808 502 8638 1962 7581 10809 7938 555 9021 1963 7108 11357 8212 608 9311 I'm trying the...

On 10/18/19 10:39 AM, Richard W.M. Jones wrote: > This adds a new API for connecting to AF_VSOCK protocol > (https://wiki.qemu.org/Features/VirtioVsock). > > For example: > > nbd_connect_vsock (nbd, 2, 10809); > > There is no test of this feature because it only works between guest > and host. You cannot start a server and client on the host and talk > between them, which is what we'd need to write a sane test. > --- > @@ -357,6 +366,23 @@ main (int argc, char *argv[]) >...

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 'print(h.get_size())' 1073741824 $ ./run nbdfuse mp --vsock 2 10809 & $ ll mp/ total 0 -rw-rw-rw-. 1 rjones rjones 1073741824 Oct 18 16:23 nbd $ dd if=/dev/rand...

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 'print(h.get_size())' 1073741824 $ ./run nbdfuse mp --vsock 2 10809 & $ ll mp/ total 0 -rw-rw-rw-. 1 rjones rjones 1073741824 Oct 18 16:23 nbd $ dd if=/dev/rand...

...uot;virsh create" return successfully, but meet error messages while the guest OS booting up. Version: libvirt-client-1.1.1-29.el7.x86_64 qemu-kvm-1.5.3-60.el7.x86_64 kernel-3.10.0-121.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1. start nbd server on the server host. #nbd-server 10809 /var/lib/libvirt/images/r7g-qcow2.img 2. create a domain with xml as bellow. # virsh create r7g-nbd.xml Domain r7g-qcow2 created from r7g-nbd.xml # virsh dumpxml r7g-qcow2| grep disk -A 7 <disk type='network' device='disk'> <driver name='qemu' type=...

...on SIGINT depends on what the client has done: if the client is currently silent with regards to issuing transmission-phase transactions, nbdkit hangs for 5 seconds, then forcibly tears down the connection: term1$ ./nbdkit -f -v -n file file=TODO ... nbdkit: debug: bound to IP address <any>:10809 (2 socket(s)) term2$ qemu-io -f raw nbd://localhost:10809/ -r qemu-io> term1$ ^C nbdkit: debug: waiting for running threads to complete nbdkit: debug: waited 5s for running threads to complete nbdkit: debug: /home/eblake/nbdkit/plugins/file/.libs/nbdkit-file-plugin.so: unload term2$ qemu-io&g...

...irst patch (reject nbd:unix:/path but still accept nbd:/path), or squash the two in order to go with the second (reject both abbreviated forms, and require scheme://...). Either way, though, nbdkit -U - --run '$nbd' will now error out rather than inadvertently connect over TCP to localhost:10809 instead of the intended Unix connection (and in the meantime, you want to use --run '$unixsocket', or maybe we should teach nbdkit to support --run '$uri'). Eric Blake (2): uri: Reject nbd:unix:/path/to/socket as invalid URI uri: Reject nbd:unix:/path/to/socket as invalid URI...

...var/lib/mock build directory. This is because the build machines have only SD-cards as local disk and SD is both slow and unreliable. The builders (NBD clients) are set up with an /etc/rc.d/rc.local file which runs these commands on boot: modprobe nbd nbd-client -b 512 nbd.server.example.com 10809 /dev/nbd0 mount /dev/nbd0 /var/lib/mock The /var/lib/mock directory is essentially temporary and doesn't need to persist across boots or even mounts. Ideally every time the client connects over NBD we'd get a fresh ext4 filesystem. Also note as there are multiple clients they must all...

...Sheldon, Big Bang Theory ===================================================================== Release Announcements --------------------- This is the latest stable release of Samba 4.1. Changes since 4.1.12: --------------------- o Michael Adam <obnox at samba.org> * BUG 10809: s3:smbd:open_file: Use a more natural check. o Jeremy Allison <jra at samba.org> * BUG 10717: s3: winbindd: Old NT Domain code sets struct winbind_domain->alt_name to be NULL. Ensure this is safe with modern AD-DCs. * BUG 10779: pthreadpool: Slightly serialize jobs...

...Sheldon, Big Bang Theory ===================================================================== Release Announcements --------------------- This is the latest stable release of Samba 4.1. Changes since 4.1.12: --------------------- o Michael Adam <obnox at samba.org> * BUG 10809: s3:smbd:open_file: Use a more natural check. o Jeremy Allison <jra at samba.org> * BUG 10717: s3: winbindd: Old NT Domain code sets struct winbind_domain->alt_name to be NULL. Ensure this is safe with modern AD-DCs. * BUG 10779: pthreadpool: Slightly serialize jobs...

...b/nbdkit/plugins/nbdkit-file-plugin.so nbdkit: debug: registered plugin /usr/local/lib/nbdkit/plugins/nbdkit-file-plugin.so (name file) nbdkit: debug: file: load nbdkit: debug: file: config key=file, value=/tmp/disk nbdkit: debug: file: config_complete nbdkit: debug: bound to IP address <any>:10809 (2 socket(s)) nbdkit: debug: forked into background (new pid = 32524) 3. Try to read the file via nbd: # qemu-img info nbd://localhost/raw qemu-img: Could not open 'nbd://localhost/raw': Could not read L1 table: Invalid argument Logs from nbdkit: nbdkit: debug: file: open readonly=0 nbdk...

...+------------- > 1 file changed, 109 insertions(+), 83 deletions(-) > > + > +=item [B<uri=>]URI > + > +When C<uri> is supplied, decode C<URI> to determine the address to > +connect to. A URI can specify a TCP connection (such as > +C<nbd://localhost:10809/export>) or a Unix socket (such as > +C<nbd+unix:///export?socket=/path/to/sock>). Remember you may need to > +quote the parameter to protect it from the shell. > + > +C<uri=> is a magic config key and may be omitted in most > +cases. See L<nbdkit(1)/Magic paramet...

...> protocol from a > >+virtual machine to an NBD server, usually running on the host. The > >+C<cid> and C<port> parameters specify the server address. Usually > >+C<cid> should be C<2> (to connect to the host), and C<port> might be > >+C<10809> or another port number assigned to you by the host > >+administrator. This call returns when the connection has been made."; > > You mentioned that right now, nbdkit has to be server on host, and > libnbd is client on guest. But if we can let nbdkit specify a cid, > do...

...ated at the Unix socket C<SOCKNAME>. -This parameter is required. +=item B<hostname=>HOST + +Connect to the NBD server at the given remote C<HOST> using a TCP socket. + +=item B<port=>PORT + +When B<hostname> is supplied, use B<PORT> instead of the default port +10809. + +Either B<socket> or B<hostname> must be provided. The server can speak +either new or old style protocol. =item B<export=>NAME @@ -66,6 +76,18 @@ the same task as the deprecated C<qemu-nbd -P 1 -f qcow2 nbdkit --exit-with-parent --filter=partition nbd socket=$sock pa...

...RY_PATH=vddk/vmware-vix-disklib-distrib/lib64 \ ./nbdkit vddk file="[datastore1] Fedora 28/Fedora 28.vmdk" \ libdir=vddk/vmware-vix-disklib-distrib \ server=vmware user=root password=- \ thumbprint=xx vm=moref=3 \ -fv -r -p 10809 single-link=true & $ qemu-img convert nbd:localhost:10809 /var/tmp/out $ LD_LIBRARY_PATH=vddk/vmware-vix-disklib-distrib/lib64 \ ./nbdkit vddk file="[datastore1] Fedora 28/Fedora 28.vmdk" \ libdir=vddk/vmware-vix-disklib-distrib \ server=vmware user=...

...+ nbdkit --vsock [--port PORT] memory 1G + +The optional I<-p>/I<--port> argument is used to change the +C<AF_VSOCK> port number. These port numbers exist in a different +address space from TCP/IP port numbers. Also unlike TCP, the port +numbers are 32 bit. The default is port 10809, same as for TCP. + +The guest that wishes to access nbdkit must be configured for +virtio-vsock. On the qemu command line use: + + qemu ... -device vhost-vsock-pci,id=vhost-vsock-pci0 + +For libvirt add this element to the C<<< <devices> >>> section: + + <vsock/> + +...