Comment 5 for bug 931540

In both cases I was ultimately able to recover the vms, either by restarting libvirt or rebooting the compute node. The problem is that this is a serious bug that has not really been reproduced in a reliable way but which a number of deployers have experienced. I will try to debug more if my users report it again but as I said, it has only happened twice since mid-Januaryy. I posted on the openstack list to see if there were any deployers of real long-lived clusters with kvm that have *not* ever seen this happen. I realize this bug ticket does not have enough information to understand the problem.