On Mon, Jul 14, 2008 at 04:36:03PM -0400, Bryan Kearney wrote: > I agree.. I could see a 2 very common use cases: > > 1) I am running on hypervisorX, and I get an image for hypervisor Y > which I want to play with. I should be able to convert Y to X without > having Y running in my enterprise. > > 2) I am building appliances, and I want to support hypervisor Y. I > should be able to build for my internal X and then convert to Y. For anything libvirt-supported, producing virt-image output would be the /best/ way to deal with these use cases. But indeed, for anything machine-specific Y, we will /have/ to have a non-connection backup. My argument is essentially that it's silly not to have a backup approach for libvirt too. If it becomes infeasible with device models or whatever in the future we can do: virt-convert: error: export of 'foo' in bar.xml requires a connection regards john _______________________________________________ et-mgmt-tools mailing list et-mgmt-tools@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/et-mgmt-tools
