This bug has been copied from bug #903248 and has been proposed to be backported to 6.4 z-stream (EUS).
In POST: http://post-office.corp.redhat.com/archives/rhvirt-patches/2013-February/msg00228.html
FYI. We have recently observed the same symptoms when a customer created a VM from a template, took a snapshot of this, and then the VM would not start thereafter. They also had some other similar scenarios that they tested that also failed, details of which can be provided, if necessary. What they found was that this worked fine on their RHEL6.3 hosts. They then upgraded to 6.4, or at least to some 6.4 components, e.g. vdsm, libvirt, and then experienced the problem. We have also reproduced this in our lab. The sequence doesn't specifically match the one outlined in the original bug, 903248, but the symptoms (in failure of execution, vdsm log and libvirtd log entries) are identical. GFW.
Verify this bug with: libvirt-0.10.2-18.el6_4.1.x86_64 qemu-kvm-rhev-0.12.1.2-2.355.el6_4.2.x86_64 vdsm-4.10.2-1.8.el6ev.x86_64 Steps: 1) need RHEVM env and ISCSI storage 2) start a vm 3) create 3 live snapshot via rhevm 4) kill -9 vm's pid 5) try to start vm ,vm can start up without error
Retest it with : libvirt-0.10.2-18.el6_4.2.x86_64 steps as comment13 : PASS
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. http://rhn.redhat.com/errata/RHBA-2013-0664.html