Hi list,
I was wondering about the status of this bug:
https://bugzilla.redhat.com/show_bug.cgi?id=512367
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?
TIA & kr,
thomas