Hide Forgot
Created attachment 510099 [details] vdsm log Description of problem: when killing a vm stats Thread gets "libvirtError: Domain not found" and still keeps on running. Thread-56159::ERROR::2011-06-27 15:22:19,117::utils::371::vm.Vm::(collect) vmId=`0f6e0767-272e-4739-a963-b164dc08c43f`::Stats function failed: ... libvirtError: Domain not found: no domain with matching uuid '0f6e0767-272e-4739-a963-b164dc08c43f' Thread-56159::ERROR::2011-06-27 15:22:24,121::utils::371::vm.Vm::(collect) vmId=`0f6e0767-272e-4739-a963-b164dc08c43f`::Stats function failed: <AdvancedStatsFunction _sampleNet at 0x24a13b0> .... libvirtError: Domain not found: no domain with matching uuid '0f6e0767-272e-4739-a963-b164dc08c43f' Version-Release number of selected component (if applicable): vdsm-4.9-76.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1.kill -9 qemu process Actual results: vdsm keeps on trying to get statistics on a killed vm. Expected results: vdsm should stop stats thread when getting VIR_ERR_NO_DOMAIN (42) Additional info: full log attached
Could it be that this was fixed by: Related to BZ#705297: have a single virEventLoopPure thread http://gerrit.usersys.redhat.com/625 It doesn't reproduce after applying the patch.
for a moment I thought that it could have nice if the stats thread knew that it should not continue polling after the domain no longer exists. but I'm not sure at all about it, and as you say - the underlying issue of lost events is solved. let's close.