>>Also make sure you are testing with latest qemu (2.1.2).
I'll try to reproduce it today. (I never had this problem with nfs, maybe it's
related to rbd with writeback)
- Mail original -
De: "Dietmar Maurer"
À: "Alexandre DERUMIER" , pve-devel@pve.proxmox.com
Envoyé: Jeudi 2 Octobr
Also make sure you are testing with latest qemu (2.1.2).
> Maybe it could be possible to retrieve the "synced" property without event,
> with
> some hack ? (through classic qmp query)
>
___
pve-devel mailing list
pve-devel@pve.proxmox.com
http://pve.p
Maybe it could be possible to retrieve the "synced" property without event,
with some hack ? (through classic qmp query)
static void coroutine_fn mirror_run(void *opaque)
{
MirrorBlockJob *s = opaque;
BlockDriverState *bs = s->common.bs;
int64_t sector_num, end, sectors_per_chunk, len
to be more exact, the event is BLOCK_JOB_READY
qapi/block-core.json
##
# @block-job-complete:
#
# Manually trigger completion of an active background block operation. This
# is supported for drive mirroring, where it also switches the device to
# write to the target path only. The ability to c
Hi,
Bug report here:
http://forum.proxmox.com/threads/19733-storage-migration-virtio-failed?p=101317#post101317
Rbd -> rbd drive mirror.
Currently, we are using qmp block-job-complete just after drive-mirror,
but block-job-complete need to be sure that drives are correctly sync
static
