Displaying 3 results from an estimated 3 matches for "bbff5ab7".
2018 Apr 12
2
Re: [Qemu-block] v2v: -o rhv-upload: Long time spent zeroing the disk
..., running
as vdsm: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#L3...
2018 Apr 10
2
Re: [Qemu-block] v2v: -o rhv-upload: Long time spent zeroing the disk
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
2018 Apr 12
0
Re: [Qemu-block] v2v: -o rhv-upload: Long time spent zeroing the disk
...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/cb6e816c4d2c536cfff5b...