* John Levon <john.levon at Sun.COM> [2006-07-11 09:27]: > 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.
So either I have no-Xen, with the image running as i86pc, or I have with-Xen, and have 1 + N domains, all of which are i86xen? And the postulated scenario is that I flip back and forth at some administratively significant frequency-justifying your use of "very annoying" (even though to manage this system I must have a sensible install image management infrastructure)--between these two states for performance reasons? > > 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. Please don't, unless your intent is to remove it from all i386 ISA systems. Make eeprom(1M) do nothing on i86xen, or make the start method do nothing (which is what I meant by "dynamic"). - Stephen -- Stephen Hahn, PhD Solaris Kernel Development, Sun Microsystems stephen.hahn at sun.com http://blogs.sun.com/sch/
