Hello, I am trying to execute virsh commands on a host but it is giving errors due to failure in acquiring lock. root at kvm01:~# virsh suspend blindone error: Failed to suspend domain blindone error: Timed out during operation: cannot acquire state change lock Any suggestions how can we figure out possible reasons. -- Jatin -------------- next part -------------- An HTML attachment was scrubbed... URL: <listman.redhat.com/archives/libvirt-users/attachments/20111024/c8d92b13/attachment.htm>
On Mon, Oct 24, 2011 at 10:35:13AM +0530, Jatin Kumar wrote:> Hello, > I am trying to execute virsh commands on a host but it is giving errors > due to failure in acquiring lock. > > root at kvm01:~# virsh suspend blindone > error: Failed to suspend domain blindone > error: Timed out during operation: cannot acquire state change lock > > Any suggestions how can we figure out possible reasons.What version of libvirt? Dave
Accidentally sent to OP only. This has been with 0.8.7 on CentOS 6 CR that Ive had the problem. ---------- Forwarded message ---------- From: "Trey Dockendorf" <treydock at gmail.com> Date: Oct 24, 2011 12:31 AM Subject: Re: [libvirt-users] Unable to acquire lock To: "Jatin Kumar" <cs5090243 at cse.iitd.ernet.in> On Mon, Oct 24, 2011 at 12:05 AM, Jatin Kumar <cs5090243 at cse.iitd.ernet.in>wrote:> Hello, > I am trying to execute virsh commands on a host but it is giving errors > due to failure in acquiring lock. > > root at kvm01:~# virsh suspend blindone > error: Failed to suspend domain blindone > error: Timed out during operation: cannot acquire state change lock > > Any suggestions how can we figure out possible reasons. > > -- > Jatin > > _______________________________________________ > libvirt-users mailing list > libvirt-users at redhat.com > redhat.com/mailman/listinfo/libvirt-users >I've run into this a few times when a snapshot hangs. Unfortunately I can't offer much advice on why it happens, but increasing log verbosity may help troubleshoot it. These are the relevant lines I use in /etc/libvirt/libvirtd.conf log_level = 2 log_filters="2:remote 2:event" log_outputs="2:file:/var/log/libvirt/libvirtd.log" Be careful with level 1 alerts...I generated a 100GB text log in 3 days. To fix that problem and unlock a VM, you need to kill libvirt, remove the PID files and start libvirt # service libvirtd stop # rm -rfv /var/run/libvirt # service libvirtd start More information here, bugzilla.redhat.com/show_bug.cgi?id=676205 - Trey -------------- next part -------------- An HTML attachment was scrubbed... URL: <listman.redhat.com/archives/libvirt-users/attachments/20111024/75f48916/attachment.htm>