Verified with rhevm-3.6.8.1-0.1.el6.noarch, host with vdsm-4.17.34-1.el7ev.noarch. Verified according to steps in description. Result after kill -19 <qemu-pid> : vdsClient is reporting the vm in state 'UP' but in engine the vm is reported as not responding which is the expected result. Not sure I got the implementation of this fix, let me know if I missed something that should be checked as well.
(In reply to sefi litmanovich from comment #2) > Verified with rhevm-3.6.8.1-0.1.el6.noarch, host with > vdsm-4.17.34-1.el7ev.noarch. > > Verified according to steps in description. > Result after kill -19 <qemu-pid> : > vdsClient is reporting the vm in state 'UP' In vdsClient: 1. if you "list" VMs, you should see them marked as 'UP*' <- please note the asterisk 2. if you use 'getAllVmStats', you should see 'monitorResponse' = -1 This is how Vdsm reports unresponsive VMs.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-1925.html