How to install logical domains and create guest domains

Solution Provider's preface: by using the commands in this section, you can create, view, install, build, and manage logical domains on the CMT server, create guest domains, and create virtual machines for users and install Oracle Solaris 10 systems. Logical domain technology enables system administrators to change CPU and virtual I/O resources in the guest domain, as well as to clone systems easily.

Installing logical domains and creating guest domains

This section describes how to install logical domains, create guest domains, and install the Oracle Solaris System on the CMT server. The installed domain will be used as the primary mirror for the next clone.

Verifying and installing the firmware

All CMT servers and blade modules have a domain with firmware support logic. However, it is necessary to ensure that the latest server firmware is installed, and that the installed firmware should match the Solaris version and the logical domain management software version in the control domain. You can get the latest information from http://docs.sun.com. Release notes, reference manuals, and logical domain software management guidelines list the firmware levels required for each server model. Please use the instructions in the Server Installation Guide or administration Guide to verify and install the firmware.

Logical domain Software Installation

The examples in this section are taken from the logical domain version 1.2. (Note: File name, command syntax, and screen output may be slightly different from the new version) you can download logical domain software from http://www.sun.com/servers/coolthreads/ldoms/downloads. The download file is a Zip compressed package, please use the following command to extract the file (or similar command):

# Unzip Ldoms_manager-1_2.zip before installing the software, please read the Readme file in the zip file. This Readme file describes all the hotfixes that need to be installed beforehand. You can download all the required patches from http://sunsolve.sun.com and install them using the Patchadd (1M) command.

At this point, you can run the setup script and respond to any prompts as needed.

You can then verify that the software is installed and that the logical domain daemon is running. Enter the LDM command Access command line interface. At this point, only one domain is running on the server, and the domain has all installed memory and CPU resources.

The following example comes from a small (6-core) T1000. Each time the LDM command runs, a warning pops up: The system is in configuration mode until the system reboots. For the sake of simplicity, we'll omit the same warning message later.

Configuring the control Domain

Initially the control domain has all the hardware resources, so the resource size of the control domain must be adjusted to provide the appropriate memory and CPU resources for the guest domain. At the same time configure the virtual hard disk, network and console and other basic services. When the domain is restarted, the control domain has the specified number of CPUs and memory size. The remaining hardware resources are assigned to the guest domain. The command program resembles the command line shown in the following illustration.

Line 1th defines a virtual disk server. Note the naming convention: the name of the server is PRIMARY-VDS0, primary (control domain) is the name of the domain where the server is located, and Vds0 represents the first virtual disk server. The end of the line tells us which domain will run the service. Although it is not necessary to follow this rule, it is recommended that you do so because it enables the service name to have a certain document function. Also, note that named rules are independent of the name of the Solaris device.

Line 2nd defines a VCC for listening on local connection ports 5000 through 5100. Line 3rd defines a virtual two-layer switch--primary-vsw0--The associated physical NIC device is e1000g0. Multiple virtual switches can be defined here and can be attached to different NIC devices, or no devices can be attached. Lines 4, 5, and 6 define the control domain: the domain has a single encryption accelerator, 4 CPUs and 3GB of memory. The remaining command line is used to save the initialization configuration to the firmware and reboot the server after a current cycle.