Displaying 9 results from an estimated 9 matches for "remotedispatchdomainblockjobabort".
2017 Oct 22
3
virsh does no longer respond to commands
...ort got stuck. Now we are unable to do basic
operations on the virtual machine like if it was frozen and when issuing
another command we see the following:
$ virsh shutdown $domain
error: Failed to shutdown domain $domain
error: Timed out during operation: cannot acquire state change lock (held
by remoteDispatchDomainBlockJobAbort)
$ virsh blockcommit $domain --active --pivot
error: Timed out during operation: cannot acquire state change lock (held
by remoteDispatchDomainBlockJobAbort)
$ virsh blockjob $domain --abort
error: Timed out during operation: cannot acquire state change lock (held
by remoteDispatchDomainBlockJobA...
2019 Jun 04
2
blockcommit of domain not successfull
...tatus data
2019-06-01 01:05:43.848+0000: 22596: warning : qemuGetProcessInfo:1461 : cannot parse process status data
2019-06-01 01:06:11.438+0000: 26112: warning : qemuDomainObjBeginJobInternal:4865 : Cannot start job (destroy, none) for doma
in severin; current job is (modify, none) owned by (5372 remoteDispatchDomainBlockJobAbort, 0 <null>) for (39s, 0s)
2019-06-01 01:06:11.438+0000: 26112: error : qemuDomainObjBeginJobInternal:4877 : Timed out during operation: cannot acquire
state change lock (held by remoteDispatchDomainBlockJobAbort)
2019-06-01 01:06:13.976+0000: 5369: warning : qemuGetProcessInfo:1461 : cannot pa...
2017 Oct 25
0
Re: virsh does no longer respond to commands
...do basic
> operations on the virtual machine like if it was frozen and when issuing
> another command we see the following:
>
> $ virsh shutdown $domain
> error: Failed to shutdown domain $domain
> error: Timed out during operation: cannot acquire state change lock (held
> by remoteDispatchDomainBlockJobAbort)
>
> $ virsh blockcommit $domain --active --pivot
> error: Timed out during operation: cannot acquire state change lock (held
> by remoteDispatchDomainBlockJobAbort)
>
> $ virsh blockjob $domain --abort
> error: Timed out during operation: cannot acquire state change lock (he...
2017 Oct 25
1
Re: virsh does no longer respond to commands
...the virtual machine like if it was frozen and when issuing
> > another command we see the following:
> >
> > $ virsh shutdown $domain
> > error: Failed to shutdown domain $domain
> > error: Timed out during operation: cannot acquire state change lock (held
> > by remoteDispatchDomainBlockJobAbort)
> >
> > $ virsh blockcommit $domain --active --pivot
> > error: Timed out during operation: cannot acquire state change lock (held
> > by remoteDispatchDomainBlockJobAbort)
> >
> > $ virsh blockjob $domain --abort
> > error: Timed out during operation: can...
2019 Jun 11
2
Re: blockcommit of domain not successfull
...tatus data
2019-06-08 03:59:26.191+0000: 30303: warning : qemuGetProcessInfo:1461 : cannot parse process status data
2019-06-08 03:59:56.095+0000: 27956: warning : qemuDomainObjBeginJobInternal:4865 : Cannot start job (destroy, none) for domain severin; current job is (modify, none) owned by (13061 remoteDispatchDomainBlockJobAbort, 0 <null>) for (38s,
0s)
2019-06-08 03:59:56.095+0000: 27956: error : qemuDomainObjBeginJobInternal:4877 : Timed out during operation: cannot acquire state change lock (held by remoteDispatchDomainBlockJobAbort)
2019-06-08 03:59:56.325+0000: 13060: warning : qemuGetProcessInfo:1461 : cannot...
2019 Jun 05
3
Re: blockcommit of domain not successfull
...6: warning : qemuGetProcessInfo:1461 : cannot
>> parse process status data
>> 2019-06-01 01:06:11.438+0000: 26112: warning :
>> qemuDomainObjBeginJobInternal:4865 : Cannot start job (destroy, none) for doma
>> in severin; current job is (modify, none) owned by (5372
>> remoteDispatchDomainBlockJobAbort, 0 <null>) for (39s, 0s)
>> 2019-06-01 01:06:11.438+0000: 26112: error : qemuDomainObjBeginJobInternal:4877
>> : Timed out during operation: cannot acquire
>> state change lock (held by remoteDispatchDomainBlockJobAbort)
>
> So this means that the virDomainBlockJobAbo...
2019 Jun 05
0
Re: blockcommit of domain not successfull
...2019-06-01 01:05:43.848+0000: 22596: warning : qemuGetProcessInfo:1461 : cannot parse process status data
> 2019-06-01 01:06:11.438+0000: 26112: warning : qemuDomainObjBeginJobInternal:4865 : Cannot start job (destroy, none) for doma
> in severin; current job is (modify, none) owned by (5372 remoteDispatchDomainBlockJobAbort, 0 <null>) for (39s, 0s)
> 2019-06-01 01:06:11.438+0000: 26112: error : qemuDomainObjBeginJobInternal:4877 : Timed out during operation: cannot acquire
> state change lock (held by remoteDispatchDomainBlockJobAbort)
So this means that the virDomainBlockJobAbort API which is also used f...
2019 Jun 13
0
Re: blockcommit of domain not successfull
...> 2019-06-08 03:59:26.191+0000: 30303: warning : qemuGetProcessInfo:1461 : cannot parse process status data
> 2019-06-08 03:59:56.095+0000: 27956: warning : qemuDomainObjBeginJobInternal:4865 : Cannot start job (destroy, none) for domain severin; current job is (modify, none) owned by (13061 remoteDispatchDomainBlockJobAbort, 0 <null>) for (38s,
> 0s)
And this looks to me as if the Abort job can't be interrupted properly
while waiting synchronously for the job to finish. This seems to be the
problem. If the VM indeed crashed there's a problem in job waiting
apparently.
I'd still really like to h...
2019 Jun 13
2
Re: blockcommit of domain not successfull
...3: warning : qemuGetProcessInfo:1461 : cannot
>> parse process status data
>> 2019-06-08 03:59:56.095+0000: 27956: warning :
>> qemuDomainObjBeginJobInternal:4865 : Cannot start job (destroy, none) for
>> domain severin; current job is (modify, none) owned by (13061
>> remoteDispatchDomainBlockJobAbort, 0 <null>) for (38s,
>> 0s)
>
> And this looks to me as if the Abort job can't be interrupted properly
> while waiting synchronously for the job to finish. This seems to be the
> problem. If the VM indeed crashed there's a problem in job waiting
> apparently.
&g...