Re: [libvirt-users] libvirtError: block copy still active: disk not ready for pivot yet

2017-01-05 Thread Kashyap Chamarthy
On Wed, Jan 04, 2017 at 07:16:03PM +0200, Ala Hino wrote: > I understand that libvirt provides async events that are triggered once the > block job reaches ready state and successfully pivots as it is reported by > qemu. > Whats the event that is triggered and what's the handler that we have to > i

Re: [libvirt-users] libvirtError: block copy still active: disk not ready for pivot yet

2017-01-04 Thread Ala Hino
I understand that libvirt provides async events that are triggered once the block job reaches ready state and successfully pivots as it is reported by qemu. Whats the event that is triggered and what's the handler that we have to implement? To be more specific, I am looking for the onEVENT callback

Re: [libvirt-users] libvirtError: block copy still active: disk not ready for pivot yet

2017-01-03 Thread Kashyap Chamarthy
On Wed, Dec 28, 2016 at 01:26:12PM +0200, Ala Hino wrote: > Hi guys, > > When performing live merge, in few cases, we see the following exception: [...] > libvirtError: block copy still active: disk 'vdb' not ready for pivot yet You can see if the block operation is still in progress or not by

[libvirt-users] libvirtError: block copy still active: disk not ready for pivot yet

2016-12-28 Thread Ala Hino
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() F