On Wed, Dec 03, 2008 at 08:07:08PM +0000, Daniel P. Berrange wrote: > > > We need to have distinct meaning for them, because many distros images > > > & hypervisors will support both kernel+initrd and BIOS based > > > provisioning, so we need to be able to distinguish between them. > > > > Isn't the correct solution to add another virt type (--hvm-whatever), > > not make life miserable for the users? > > > > At the *very* least, can't we decide whether to try kernel+initrd based > > upon detected OS type? I have a queued patch that adds 'os_type' to each > > of the OSDistro classes. > > Unfortunately it varies based on (os type + hv type + hv version). True. But Windows and Solaris isn't ever going to do it. regards john _______________________________________________ et-mgmt-tools mailing list et-mgmt-tools@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/et-mgmt-tools
