Variable updates persist across a reboot but not across a power cycle unless the variable updates are either initiated from OpenBoot firmware on the control domain or followed by saving the configuration to the SP.
Note the following conditions:
When the control domain reboots, if there are no bound guest domains and no delayed reconfiguration in progress, the SP performs a power cycle of the system.
When the control domain reboots, if guest domains are bound or active (or the control domain is in the middle of a delayed reconfiguration), the SP does not perform a power cycle of the system.
Logical Domains variables for a domain can be specified using any of the following methods:
At the OpenBoot prompt.
Using the Oracle Solaris OS eeprom(1M) command.
Using the Logical Domains Manager CLI (ldm).
In a limited fashion, from the service processor (SP) using the bootmode command. This method can be used for only certain variables, and only when in the factory-default configuration.
Variable updates that are made by using any of these methods should always persist across reboots of the domain. The variable updates also always apply to any subsequent domain configurations that were saved to the SP.
In Oracle VM Server for SPARC 3.4 software, variable updates do not persist as expected in a few cases:
All methods of updating a variable persist across reboots of that domain. However, they do not persist across a power cycle of the system unless a subsequent logical domain configuration is saved to the SP.
However in the control domain, updates made using either OpenBoot firmware commands or the eeprom command do persist across a power cycle of the system even without subsequently saving a new logical domain configuration to the SP. The eeprom command supports this behavior on servers starting with SPARC T4.
If you are concerned about Logical Domains variable changes, do one of the following:
Bring the system to the ok prompt and update the variables.
Update the variables while the Logical Domains Manager is disabled:
# svcadm disable ldmd update variables # svcadm enable ldmd
When running Live Upgrade, perform the following steps:
# svcadm disable -t ldmd # luactivate be3 # init 6
If you modify the time or date on a logical domain, for example, using the ntpdate command, the change persists across reboots of the domain but not across a power cycle of the host. To ensure that time changes persist, save the configuration with the time change to the SP and boot from that configuration.
The following Bug IDs have been filed to resolve these issues: 15375997, 15387338, 15387606, and 15415199.