On Fri, Dec 23, 2016 at 10:20:03AM +0100, Alexandre DERUMIER wrote:
> Hi wolfgang,
>
> I have done more test with drive mirror and nbd target.
>
> It seem that the hang occur only if the target ip is unreacheable (no network
> reponse)
>
> # drive_mirror -n drive-scsi0
Hi wolfgang,
I have done more test with drive mirror and nbd target.
It seem that the hang occur only if the target ip is unreacheable (no network
reponse)
# drive_mirror -n drive-scsi0 nbd://66.66.66.66/target
ERROR: VM 183 qmp command 'human-monitor-command' failed - got timeout
If the ip
>>Doesn't the job show up in query-block-jobs before the connection
>>finishes? If so then we could just assume if it's still at 0% after a
>>timeout the connection doesn't work? The question is though, what is a
>>good timeout?
the problem is that the qemu monitor is totally hanging...
>>Or we
applied
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
See commit message.
jlavoy (1):
Boost LVM Migration Speed. This speeds up host to host LVM migration
to be more in line with what you see using qcows or raw files.
PVE/Storage.pm | 8
1 file changed, 4 insertions(+), 4 deletions(-)
--
2.10.2
Boost LVM Migration Speed. This speeds up host to
host LVM migration to be more in line with what you see using qcows or raw
files.
Signed-off-by: jlavoy
---
PVE/Storage.pm | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/PVE/Storage.pm