Displaying 3 results from an estimated 3 matches for "block_job_ready".
2017 Jan 04
1
Re: libvirtError: block copy still active: disk not ready for pivot yet
...bugs.]
>
> > I am trying to understand what this exception indicates in order to
> handle
> > it appropriately when thrown by libvirt.
>
> Here's the commit that adds the above error message. In short: Until
> the 'query-block-jobs' QMP command emits the flag BLOCK_JOB_READY, the
> copy / mirror block operation is truly not complete.
>
>
> commit eae59247c59aa02147b2b4a50177e8e877fdb218
> Author: Peter Krempa <pkrempa@redhat.com>
> Date: Wed Jul 15 15:11:02 2015 +0200
>
> qemu: Update state of block job to READY only...
2016 Dec 28
2
libvirtError: block copy still active: disk not ready for pivot yet
Hi guys,
When performing live merge, in few cases, we see the following exception:
Traceback (most recent call last):
File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 736, in wrapper
return f(*a, **kw)
File "/usr/share/vdsm/virt/vm.py", line 5278, in run
self.tryPivot()
File "/usr/share/vdsm/virt/vm.py", line 5247, in tryPivot
ret =
2017 Jan 03
0
Re: libvirtError: block copy still active: disk not ready for pivot yet
...[I see, that the above are oVirt bugs.]
> I am trying to understand what this exception indicates in order to handle
> it appropriately when thrown by libvirt.
Here's the commit that adds the above error message. In short: Until
the 'query-block-jobs' QMP command emits the flag BLOCK_JOB_READY, the
copy / mirror block operation is truly not complete.
commit eae59247c59aa02147b2b4a50177e8e877fdb218
Author: Peter Krempa <pkrempa at redhat.com>
Date: Wed Jul 15 15:11:02 2015 +0200
qemu: Update state of block job to READY only if it actually is ready...