On Tue, Jul 08, 2008 at 09:55:57PM +0100, John Levon wrote: > > If we accept we want to use virt-convert to generate libvirt XML, then > > we need to require a hypervisor connection URI for this conversion so > > we can fetch the capabilities data and fill in the deployment specific > > bits. And the resulting libvirt XML generated will be specific to the > > machine it was generated on (or another with equivalent setup). > > Why is this an improvement over specifying stuff on the command line > (like --arch) ? I take that back, whilst certainly the capabilities stuff is irrelevant today for Xen (based on what I get back on Solaris, anyway), I can see that it will matter in the future. So yes, we need a --connect option. It would typically default to none except when needed, and then we use the default connection. regards john _______________________________________________ et-mgmt-tools mailing list et-mgmt-tools@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/et-mgmt-tools
