[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

[libvirt] libvirt 3.5.0 locks



Hi. I'm testing libvirt 3.5.0 and have many issues like this:

Jul 14 09:47:25 cn25 libvirtd[18820]: 2017-07-14 06:47:25.598+0000:
18841: error : qemuDomainObjBeginJobInternal:3872 : Timed out during
operation: cannot acquire state change lock (held by
remoteDispatchConnectGetAllDomainStats)
Jul 14 09:47:25 cn25 libvirtd[18820]: 2017-07-14 06:47:25.598+0000:
18841: warning : qemuDomainObjBeginJobInternal:3860 : Cannot start job
(query, none) for domain 147565; current job is (query, none) owned by
(18828 remoteDispatchConnectGetAllDomainStats, 0 <null>) for (53670s,
0s)
Jul 14 09:46:55 cn25 libvirtd[18820]: 2017-07-14 06:46:55.576+0000:
18836: error : virNetDevTapInterfaceStats:751 : internal error:
/proc/net/dev: Interface not found
Jul 14 09:46:55 cn25 libvirtd[18820]: 2017-07-14 06:46:55.542+0000:
18832: warning : qemuGetProcessInfo:1428 : cannot parse process status
data
Jul 14 09:46:31 cn25 libvirtd[18820]: 2017-07-14 06:46:31.050+0000:
18838: warning : qemuGetProcessInfo:1428 : cannot parse process status
data

Domain in status in shutdown
as i see tap device already removed from the system, so
virNetDevTapInterfaceStats says right info.

My question - why lock now released and why only libvirt restart can
helps in this case
-- 
Vasiliy Tolstov,
e-mail: v tolstov selfip ru


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]