[libvirt] an old bug reappear-TimeoutError
hi, i encounter an error of libvirt, which is reported in 2011. i intended to update the ticket(spice password) of vm. https://bugzilla.redhat.com/show_bug.cgi?id=676205 ---------log------------------ Thread-162::ERROR::2013-05-08 13:50:46,000::BindingXMLRPC::909::vdsm::(wrapper) libvirt error Traceback (most recent call last): File "/usr/share/vdsm/BindingXMLRPC.py", line 904, in wrapper res = f(*args, **kwargs) File "/usr/share/vdsm/BindingXMLRPC.py", line 213, in vmSetTicket return vm.setTicket(password, ttl, existingConnAction, params) File "/usr/share/vdsm/API.py", line 550, in setTicket return v.setTicket(password, ttl, existingConnAction, params) File "/usr/share/vdsm/libvirtvm.py", line 2245, in setTicket self._dom.updateDeviceFlags(graphics.toxml(), 0) File "/usr/share/vdsm/libvirtvm.py", line 524, in f raise toe TimeoutError: Timed out during operation: cannot acquire state change lock
On 05/08/2013 11:28 PM, yue wrote:
hi,
[charset=GBK is an unusual encoding, which in turn caused my mail reader to render your message oddly; these days, sending mail in UTF-8 is preferred]
i encounter an error of libvirt, which is reported in 2011. i intended to update the ticket(spice password) of vm.
More likely, you encountered the same symptoms as a previous bug reported and fixed in 2011, but where the cause of those symptoms is a different bug. But without more details, such as what version of libvirt you are using, what distro provided that build, and what action you were attempting when things locked up, it's hard to say if it is a known issue.
That bug was created against RHEL 5. If you are going to report more details via bugzilla, then you are better off opening a new bug that is relevant to your setup (whether that be against RHEL or Fedora or upstream libvirt itself) rather than trying to piggyback on an old bug.
TimeoutError: Timed out during operation: cannot acquire state change lock
In the past, when this has happened, it was because libvirt disobeyed locking rules in its code; and a workaround was to restart libvirtd. -- Eric Blake eblake redhat com +1-919-301-3266 Libvirt virtualization library http://libvirt.org
participants (2)
-
Eric Blake -
yue