A domain configuration is a complete description of all the domains and their resource allocations within a single system. You can save and store configurations on the service processor (SP) for later use.
Saving a configuration on the SP makes it persist across system power cycles. You can save several configurations and specify which configuration to boot on the next power-on attempt.
When you power up a system, the SP boots the selected configuration. The system runs the same set of domains and uses the same virtualization and partitioning resource allocations that are specified in the configuration. The default configuration is the one that is most recently saved. You can also explicitly request another configuration by using the ldm set-spconfig command or the appropriate ILOM command.
Caution - Always save your stable configuration to the SP and save it as XML. Saving the configuration in these ways enable you to recover your system configuration after a power failure and save it for later use. See Saving Domain Configurations.
A local copy of the SP configuration and the Logical Domains constraint database is saved on the control domain whenever you save a configuration to the SP. This local copy is called a bootset. The bootset is used to load the corresponding Logical Domains constraints database when the system undergoes a power cycle.
On SPARC T5 and SPARC M5 systems, the bootsets on the control domain are the master copies of the configurations. On startup, the Logical Domains Manager automatically synchronizes all configurations with the SP, which ensures that the configurations on the SP are always identical to the bootsets that are stored on the control domain.
A physical domain is the scope of resources that are managed by a single Oracle VM Server for SPARC instance. A physical domain might be a complete physical system as is the case of supported SPARC T-Series platforms. Or, it might be either the entire system or a subset of the system as is the case of supported SPARC M-Series platforms.