This section describes the changes in behavior in using the Oracle Solaris OS that occur once a configuration created by the Logical Domains Manager is instantiated.
The OpenBoot firmware is not available after the Oracle Solaris OS has started because it is removed from memory.
To reach the ok prompt from the Oracle Solaris OS, you must halt the domain by using the Oracle Solaris OS halt command.
Whenever performing any maintenance on a system running Oracle VM Server for SPARC software that requires you to perform a power cycle of the server, you must save your current logical domain configurations to the SP first.
To save your current domain configurations to the SP, use the following command:
# ldm add-config config-name
You can initiate Oracle Solaris OS breaks as follows:
Press the L1-A key sequence when the input device is set to keyboard.
Enter the send break command when the virtual console is at the telnet prompt.
When you initiate such a break, the Oracle Solaris OS issues the following prompt:
c)ontinue, s)ync, r)eset, h)alt?
Type the letter that represents what you want the system to do after these types of breaks.
You can use the reboot and shutdown -i 5 commands to reboot the control (primary) domain.
No other domains configured. Reboots the control domain without graceful shutdown, no power off.
Other domains configured. Reboots the control domain without graceful shutdown, no power off.
shutdown -i 5:
No other domains configured. Host powered off after graceful shutdown, stays off until powered on at the SP.
Other domains configured. Reboots with graceful shutdown, no power off.
Sometimes, executing the uadmin 1 0 command from the command line of a Oracle VM Server for SPARC system does not leave the system at the ok prompt after the subsequent reset. This incorrect behavior is seen only when the auto-reboot? variable is set to true. If auto-reboot? is set to false, the expected behavior occurs. To work around this problem, use the uadmin 2 0 command or always run with auto-reboot? set to false.
For information about the consequences of rebooting a domain that has the root domain role, see Rebooting the Root Domain With PCIe Endpoints Configured.