Hi Mark!
Thanks for the info. > To enable the hypervisor: > > svcadm enable svc:/milestone/xvm > > This will use bootadm(1M) to convert an existing menu.lst entry so that > on next reboot the hypervisor will be started. The store service, > svc:/system/xvm/store, goes into maintenance to indicate that a reboot is > required. > > To disable the hypervisor: > > svcadm disable svc:/milestone/xvm > > This will use bootadm(1M) to convert an existing menu.lst entry so that > on next reboot Solaris will start on hardware. > > Please be aware that using this service will result in any tweaked parameters > being discarded. In addition, the service will install a default value for > the dom0_mem property (half of system memory or 2048MB, whichever value > is lower). > > It is still possible to manually edit the menu.lst file, however use of the > service will discard your changes. So do I understand correctly that if I ignore the new milestone I can still use the old menu.lst-based behavior? I like the existing setup much better. Now, I can decide if I want the hypervisor within my custom timeout _when booting_. Using the milestone, I would have to decide about the next boot _while shutting down_. Usually I boot my test systems for whatever I want to test _now_. Is this maybe a solution looking for a problem? Of course if the old behavior is still available I don't really mind... Thanks -- Volker -- ------------------------------------------------------------------------ Volker A. Brandt Consulting and Support for Sun Solaris Brandt & Brandt Computer GmbH WWW: http://www.bb-c.de/ Am Wiesenpfad 6, 53340 Meckenheim Email: [email protected] Handelsregister: Amtsgericht Bonn, HRB 10513 Schuhgröße: 45 Geschäftsführer: Rainer J. H. Brandt und Volker A. Brandt _______________________________________________ xen-discuss mailing list [email protected]
