On Tue, Jul 08, 2008 at 06:45:57PM +0000, David Lutterkort wrote: > > standalone without any libvirt connection. This means it is unable > > to get any hypervisor specific capabilities data to determine what > > the required OS / boot type options are. > > The right approach then seems to use virt-convert to convert to > image.xml and use virt-image to fill in the deployment specific bits, > even if the user thinks they are just converting a VM from one format to > another. If you mean implementation-wise (i.e. virtinstance.py should just call out to virt-image), then I suppose that'd be OK, because you can use virt-convert cmdline options plus the parsed config to specify exactly what you need in virt-image. If you mean the *user* should do this, then see my other mail. regards john _______________________________________________ et-mgmt-tools mailing list et-mgmt-tools@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/et-mgmt-tools
