1.1.3.4 Installing the Secondary Service Domain

After the secondary service domain has been created and the primary domain has finished rebooting, start the secondary service domain using the following commands in the control domain:

# ldm bind secondary
# ldm start secondary

Once the secondary service domain has been started, you can access its console by obtaining the console port using the following command:

# ldm ls secondary
NAME             STATE      FLAGS   CONS    VCPU  MEMORY   UTIL  NORM  UPTIME
secondary        active     -t--v-  5000    8     8G       0.0%  0.0%  0s

Note that the console port is listed in the CONS column. You can open a telnet connection to this port as follows:

# telnet 0 5000
Trying 0.0.0.0...
Connected to 0.
Escape character is '^]'.
 
Connecting to console "secondary" in group "secondary" ....
Press ~? for control options ..
 
{0} ok

Now you must install the Oracle Solaris 11 operating system into the secondary domain. This can be achieved by following the instructions provided in Installing Oracle Solaris 11.1 Systems in the Oracle Solaris 11.1 documentation available at:

http://docs.oracle.com/cd/E26502_01/html/E28980/index.html

Do not attempt to install either the Oracle VM Agent or the LDoms Manager into the secondary service domain. Only the Oracle Solaris 11 operating system is required.

Make sure that the secondary service domain is properly configured so that it can boot automatically. In particular, the OpenBoot PROM (OBP) variables of the domain must be correctly set. For instance, the auto-boot? parameter should be set to true, and boot-device parameter should contain the device path of the boot disk that is configured for the secondary domain.