On Fri, Oct 02, 2009 at 09:59:27PM +0200, Thomas Treutner wrote: > Hi list, > > I was wondering about the status of this bug: > > https://bugzilla.redhat.com/show_bug.cgi?id=512367 Patch proposed but the original reporter never indicated whether it actually fixed the problem or not. If someone can confirm .... > > Is it correct that this is a bug in the libvirt client? I ran into this today, > as I've written a kind of a VM scheduler (ressource requirements, placement > etc.) in Java (libvirt-java 0.3.0, libvirt 0.6.5) and this is a show-stopper > for me right now. I had some troubles with the newest version of libvirt (it > couldn't connect to Xen IIRC), so I don't want to mess my setup again for > nothing. > > What is actually causing this problem resp. in which situation is libvirt > broken? When a client uses more than one connection at the same time? Or when > a client uses more than one connection to the same server at the same time? > Are there any recommeded workarounds? I believe the problem is when you use multiple different virConnectPtr objects. If using one connection from multiple threads libvirt itself would have provided sufficient locking. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list