Displaying 3 results from an estimated 3 matches for "qemuconnectgetalldomainstat".
Did you mean:
qemuconnectgetalldomainstats
2018 Jan 17
0
Re: Could not destroy domain, current job is remoteDispatchConnectGetAllDomainStats
...ts, 0 <null>) for (30s, 0s)
> Jan 17 13:54:23 server1 libvirtd[20437]: 2018-01-17 13:54:23.805+0000:
> 20522: error : qemuDomainObjBeginJobInternal:4874 : Timed out during
> operation: cannot acquire state change lock (held by
> remoteDispatchConnectGetAllDomainStats)
Sounds like qemuConnectGetAllDomainStats() forgot to unset the job on a
domain. Can you please attach gdb to libvirtd and run 't a a bt' and
share the output?
Michal
2018 Jan 17
4
Could not destroy domain, current job is remoteDispatchConnectGetAllDomainStats
Hello libvirt-users list,
We're catching the same bug since 3.4.0 version (3.3.0 works OK).
So, we have process that is permanently connected to libvirtd via socket
and it is collecting stats, listening to events and control the VPSes.
When we try to 'shutdown' a number of VPSes we often catch the bug. One of
VPSes sticks in 'in shutdown' state, no related 'qemu'
2018 Jan 17
1
Re: Could not destroy domain, current job is remoteDispatchConnectGetAllDomainStats
2018-01-17 17:32 GMT+02:00 Michal Privoznik <mprivozn@redhat.com>:
> Sounds like qemuConnectGetAllDomainStats() forgot to unset the job on a
> domain. Can you please attach gdb to libvirtd and run 't a a bt' and
> share the output?
>
> Michal
>
This is output of gdb 't a a bt' ~5 seconds after that error message
appeared in log with remoteDispatchConnectGetAllDomainStats()...