On Wed, Apr 25, 2007 at 02:51:50PM +0900, Kazuki Mizushima wrote: I would suggest like Dan Berrange that you look at integrating that feature in virt-manager. There is far more similarities with existing operations, 'appliance' support is being added (for at least some semantic of that term), and cloning is in this respect just one more way to provision a domain. If you are really expecting to push in libvirt to get remote support when it comes you need to consider the fact that this will not be possible until we get management operation for storage (snapshotting, partitionning and copy) and we didn't even started to really discuss this issue (and other developments like NUMA may preempt the effort in the group). I would feel way more comfortable doing an analysis of all the requirement to have a really working clone support in libvirt if we had a good working experience of at the virt-manager level. Like creation this is an entry point which could get a really wide array of options and settings, trying to implement a premature version there would not be productive. So I encourage you to try to rework it in the framework of virt-manager it should also be quite simpler to do all this prototyping in Python than C, honnestly this really look the best way forward at this point. Daniel -- Red Hat Virtualization group http://redhat.com/virtualization/ Daniel Veillard | virtualization library http://libvirt.org/ veillard(a)redhat.com | libxml GNOME XML XSLT toolkit http://xmlsoft.org/ http://veillard.com/ | Rpmfind RPM search engine http://rpmfind.net/