On 28.11.2019 14:11, Peter Krempa wrote:
> On Thu, Nov 28, 2019 at 10:51:56 +, Nikolay Shirokovskiy wrote:
>>
>>
>> On 28.11.2019 12:05, Peter Krempa wrote:
>>> On Thu, Nov 28, 2019 at 07:29:08 +, Nikolay Shirokovskiy wrote:
On 27.11.2019 17:56, Peter Krempa wrote:
> O
On Thu, Nov 28, 2019 at 10:51:56 +, Nikolay Shirokovskiy wrote:
>
>
> On 28.11.2019 12:05, Peter Krempa wrote:
> > On Thu, Nov 28, 2019 at 07:29:08 +, Nikolay Shirokovskiy wrote:
> >>
> >>
> >> On 27.11.2019 17:56, Peter Krempa wrote:
> >>> On Wed, Nov 27, 2019 at 17:19:18 +0300, Nikolay
On 28.11.2019 12:05, Peter Krempa wrote:
> On Thu, Nov 28, 2019 at 07:29:08 +, Nikolay Shirokovskiy wrote:
>>
>>
>> On 27.11.2019 17:56, Peter Krempa wrote:
>>> On Wed, Nov 27, 2019 at 17:19:18 +0300, Nikolay Shirokovskiy wrote:
Due to race qemuDomainGetBlockJobInfo can return there is
On Thu, Nov 28, 2019 at 07:29:08 +, Nikolay Shirokovskiy wrote:
>
>
> On 27.11.2019 17:56, Peter Krempa wrote:
> > On Wed, Nov 27, 2019 at 17:19:18 +0300, Nikolay Shirokovskiy wrote:
> >> Due to race qemuDomainGetBlockJobInfo can return there is
> >> no block job for disk but later call to sp
On 27.11.2019 17:56, Peter Krempa wrote:
> On Wed, Nov 27, 2019 at 17:19:18 +0300, Nikolay Shirokovskiy wrote:
>> Due to race qemuDomainGetBlockJobInfo can return there is
>> no block job for disk but later call to spawn new blockjob
>> can fail because libvirt internally still not process block
On Wed, Nov 27, 2019 at 17:19:18 +0300, Nikolay Shirokovskiy wrote:
> Due to race qemuDomainGetBlockJobInfo can return there is
> no block job for disk but later call to spawn new blockjob
> can fail because libvirt internally still not process blockjob
> finishing. Thus let's wait for blockjob fin
Due to race qemuDomainGetBlockJobInfo can return there is
no block job for disk but later call to spawn new blockjob
can fail because libvirt internally still not process blockjob
finishing. Thus let's wait for blockjob finishing if we
report there is no more blockjob.
Signed-off-by: Nikolay Shiro
