The only significant change here is that these now don't block all threads during a long-running libvirt API call. So you can have a thread to keep the display updated and another making libvirt calls. As with all libvirt programs, each thread that needs to make libvirt calls should have its own connection. http://libvirt.org/ocaml/ Rich. -- Emerging Technologies, Red Hat - http://et.redhat.com/~rjones/ Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SL4 1TE, United Kingdom. Registered in England and Wales under Company Registration No. 03798903