Hi Richard, I killed the qemu process, turned the VM on again, and everything is fine now. Tonight I'll update the libvirt of this server. Thank you very much. ;D ----- Att, Bruno Menezes <div class="gmail_quote"> On Tue, May 10, 2011 at 8:59 AM, Richard W.M. Jones <<a href="mailto:rjones@redhat.com">rjones@redhat.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"> <div class="im">On Tue, May 10, 2011 at 08:37:55AM -0300, Bruno Lamps wrote: > virsh # destroy ldapdebian > > erro: Falha ao destruir o domínio ldapdebian > > erro: Timed out during operation: cannot acquire state change lock </div>This is pretty strange ... *after* restarting libvirtd? If it's a qemu/KVM guest, I would suggest just killing the qemu process associated with the guest. If the guest doesn't boot, try virt-rescue but ***only*** when you are sure the guest [ie. qemu] is not running. Otherwise you'll permanently corrupt the disks. Rich. -- Richard Jones, Virtualization Group, Red Hat <a href="http://people.redhat.com/%7Erjones%0Avirt-df" target="_blank">http://people.redhat.com/~rjones virt-df</a> lists disk usage of guests without needing to install any software inside the virtual machine. Supports Linux and Windows. <a href="http://et.redhat.com/%7Erjones/virt-df/" target="_blank">http://et.redhat.com/~rjones/virt-df/</a> </blockquote></div>