So, just to make sure I understand this correctly. Any changes made to my control domain, such as adding/deleting/changing virtual disk, virtual network switch, etc and not saved to SP will be lost upon control domain reboot. Changes such as adding or changing guest domains should not require saving spconfig and will not be lost upon rebooting control domain.
Thank you, D. Peter Wilson wrote: > Its not 'necessary' to save configs to the SP, but it is advisable at > suitable checkpoint or snapshot points. Typically customers will > experiment with the LDOMs configs through a few iterations before they > get to their 'perfect' setup, at that point it would be a good time to > save a SP checkpoint of the config. > > Further iterations may also be a good point to take a > checkpoint/snapshot of the config, bearing in mind that there is only > space for four configs to be saved in the SP FLASH Memory so snapshot > points should be carefully chosen. > > Also, in case the server is ever subject to an unexpected power failure > or reboot, the last saved config is the one that the system will try to > reinstate when power returns and the server reboots. > > Other wise the customer risks the server coming back up in a > factory-default configuration and the guest domains failing to start, > this would require some manual intervention to bring to get back to a > functioning config. > > Peter > > > Dmitriy Krayzman wrote: >> I'm a little unclear when it's necessary to save configuration by >> running add-spconfig and when it's not necessary. What changes would >> require saving configuration? >> Thanks, >> D. >> _______________________________________________ >> ldoms-discuss mailing list >> ldoms-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss >
