On Tue, Jul 11, 2006 at 09:03:45AM -0700, Stephen Hahn wrote: > A domain can be booted as either i86pc or i86xen? Can you expand on
Even the "controlling" domain, domain 0, runs virtualised under Xen. Thus, you can boot either on metal, or running under Xen. Other OS instances on the machine will always run as i86xen. As running under Xen has an impact in terms of performance and features, we need to make the choice available at boot-time. The other option (install time) would make re-purposing a machine very annoying. > > This is somewhat problematic, in particular: > > > > - the "first" boot might be i86xen. In that case we'll end up with > > platform_none.xml applied. > > > > Whilst this only affects the eeprom service right now, which seems to be > > legacy > > code anyway, we most likely need some kind of fix; perhaps as simple as > > looking > > for a uname -p profile first, and introducing a platform_i386.xml later if > > and > > when we need it. > > Why wouldn't you change the eeprom service to be dynamic with respect > to platforms? It is transient, after all. I'm not sure what you mean here, but we're simply going to remove this service altogether. > For more distinct differences, you can introduce platform_i86xen.xml. This hits the first problem above. The platform profile choice happens only once not every boot-time: manifest-import doesn't re-create the link, and even if it did, the hash-checking behaviour would prevent any changes being applied. regards john
