search for: a497

...m:kvm, not exporting anything. 1. User starts transfer session via oVirt API with protocol="nbd" (if not specified, use "https" for backward compatibility) 2. oVirt selects a host for the transfer and configures an export in that host - for example: [bbff5ab7-2e8e-45b8-a497-423c2d2b3ff1] exportname = /path/to/image trim = yes timeout = 300 nbd-server supports reloading configuration via SIGHUP. Looks like it should work for adding export dynamically: https://github.com/NetworkBlockDevice/nbd/blob/cb6e816c4d2c536cfff5ba9859f210aabe39539b/nbd-server.c#L3007 I could fi...

On Tue, Apr 10, 2018 at 03:25:47PM +0000, Nir Soffer wrote: > On Tue, Apr 10, 2018 at 5:50 PM Richard W.M. Jones <rjones@redhat.com> > wrote: > > > On Tue, Apr 10, 2018 at 02:07:33PM +0000, Nir Soffer wrote: > > > This makes sense if the device is backed by a block device on oVirt side, > > > and the NBD support efficient zeroing. But in this case the device

...; 1. User starts transfer session via oVirt API with protocol="nbd" > (if not specified, use "https" for backward compatibility) > > 2. oVirt selects a host for the transfer and configures an export > in that host - for example: > > [bbff5ab7-2e8e-45b8-a497-423c2d2b3ff1] > exportname = /path/to/image > trim = yes > timeout = 300 > > nbd-server supports reloading configuration via SIGHUP. > Looks like it should work for adding export dynamically: > https://github.com/NetworkBlockDevice/nbd/blob/cb6e816c4d2c536cfff5ba9859f210aabe39...

> FYI, > > I finally succeeded too upload one of the 3 drivers that had problems. > > I didi it with another user (not? with administrator) which is member > of domain admins. > > I deleted it and tried so many times again to upload it anf it failed > with the same error. > > So we're in a process where sometimes it's working sometimes not and > you