<div dir="ltr"><div>Yeah, I am totally fine with retiring them. </div>David </div><div class="gmail_extra"> <div class="gmail_quote">On Fri, Jan 10, 2014 at 1:49 PM, Richard W.M. Jones <<a href="mailto:rjones@redhat.com" target="_blank">rjones@redhat.com</a>> wrote: <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">virt-convert & virt-image: These tools depend on the virt-image format, a noble attempt to make a non-proprietary version of OVF. I think there is still a need to make an open version of the horrible proprietary fake-standard of OVF, but virt-image isn't it. Having these tools does create confusion for users (particularly versus when they should run 'qemu-img convert' or virt-v2v) so I think we should drop them. virt-clone: This tool is supposed to clone existing images. But you can just run dd/cp to clone the disks + 'virt-install --import' to create libvirt configuration. To do full cloning you will really need something a lot more advanced that can see inside the disks, ie. virt-sysprep, or that can sparsify disks (virt-sysprep), or that can do templating (virt-builder et al). virt-clone is troublesome for me. Most people I meet who try to use it should be using virt-sysprep. Rich. -- Richard Jones, Virtualization Group, Red Hat <a href="http://people.redhat.com/~rjones" target="_blank">http://people.redhat.com/~rjones</a> Fedora Windows cross-compiler. Compile Windows programs, test, and build Windows installers. Over 100 libraries supported. <a href="http://fedoraproject.org/wiki/MinGW" target="_blank">http://fedoraproject.org/wiki/MinGW</a> </blockquote></div> </div>