I've got some bad news: libvirt remote support is probably not going to make libguestfs 1.20. John Eckersberg is diligently working on this, but I don't want to hold up the release of the next stable libguestfs for this, particularly since it needs dependent changes in libvirt. The last stable branch of libguestfs (1.18) happened in the middle of May. That's 7 months ago, making this the longest cycle we've ever had by a large margin. Therefore it is time to start thinking about the next stable version, 1.20. As usual, bugs that need to be fixed for 1.20 should have "1.20" (without quotes) placed in the Devel Whiteboard field in Bugzilla. (There are currently none, but I plan to mark some). You can get a list of these bugs using this link: https://bugzilla.redhat.com/buglist.cgi?query_format=advanced&field0-... ( http://tinyurl.com/bx8kter ) or all bugs here: https://bugzilla.redhat.com/buglist.cgi?component=libguestfs&product=... The draft release notes (not quite up to date) are here so you can get an idea of the new features: http://libguestfs.org/guestfs-release-notes.1.html#release-notes-for-libg... I'm planning to spend at least the next 3 weeks making the libvirt backend stable, so that we can use this as the default in Fedora 18, but I'm quite prepared to pull this and go with the ordinary backend if I cannot do this. Note that the default upstream is the non-libvirt appliance backend, and this will remain so. If there are any other problems, please let me know. Rich. -- Richard Jones, Virtualization Group, Red Hat http://people.redhat.com/~rjones virt-top is 'top' for virtual machines. Tiny program with many powerful monitoring features, net stats, disk stats, logging, etc. http://et.redhat.com/~rjones/virt-top