Hello Daniel, I'm running cluster of libvirt-managed KVM's, and I'm having quite a lot of problems with libvirt concurrent access. It seems that this batch of patches might fix some of those, right? Should I test them or wait till next release before digging further into it and reporting? thanks a lot with best regards nik On Tue, Nov 03, 2009 at 02:49:54PM -0500, Daniel P. Berrange wrote:
This is an update of this series:
http://www.redhat.com/archives/libvir-list/2009-October/msg00644.html
minus the patches DV already ACKd which I've merged.
The main change in this series is that I've removed the change which added a RW-lock primitive in the QEMU driver. Instead I've implemented the job condition variable idea I described here
http://www.redhat.com/archives/libvir-list/2009-October/msg00815.html
The nice thing about this is that its actually possible to start doing timeouts of commands. This series only partially supports timeouts. A long running monitor command itself will not timeout, but if a second API call is made while someone else is using the monitor, this waiting call will timeout after 30 seconds if the monitor was not relased.
Daniel
-- Libvir-list mailing list Libvir-list@redhat.com https://www.redhat.com/mailman/listinfo/libvir-list
-- ------------------------------------- Nikola CIPRICH LinuxBox.cz, s.r.o. 28. rijna 168, 709 01 Ostrava tel.: +420 596 603 142 fax: +420 596 621 273 mobil: +420 777 093 799 www.linuxbox.cz mobil servis: +420 737 238 656 email servis: servis@linuxbox.cz -------------------------------------