On Fri, Nov 30, 2012 at 11:10:58AM +0100, Nathanaël Blanchet wrote: "not responding" usually means that there's a qemu or libvirt bug, making communication to the VM impossible. If stopping the VM fails, too, it may mean that libvirtd is not responding. Could you post your vdsm.log and libvirtd.log (when you send the vmDestroy verb to vdsm) somewhere? Does virsh -c qemu+tls://hostname/system dominfo <yourvm> or virsh -c qemu+tls://hostname/system destroy <yourvm> # DANGER to VM! block? Dan.