Creating and Starting a Guest Domain

The guest domain must run an operating system that understands both the sun4v platform and
the virtual devices presented by the hypervisor. Currently, this means that you must run at least
the Oracle Solaris 10 11/06 OS. Running the Oracle Solaris 10 8/11 OS provides you with all the
OracleVMServer for SPARC 3.0 features. See the OracleVMServer for SPARC 3.0 Release Notes
for any specific patches that might be necessary. Once you have created default services and
reallocated resources from the control domain, you can create and start a guest domain.

1. Create a logical domain.
For example, the following command would create a guest domain named ldg1.
primary# ldm add-domain ldg1

2. Add CPUs to the guest domain.
For example, the following command would add eight virtual CPUs to guest domain ldg1.
primary# ldm add-vcpu 8 ldg1

3. Add memory to the guest domain.
For example, the following command would add 2 gigabytes of memory to guest domain ldg1.
primary# ldm add-memory 2G ldg1

4. Add a virtual network device to the guest domain.
For example, the following command would add a virtual network device with these specifics to
the guest domain ldg1.
primary# ldm add-vnet vnet1 primary-vsw0 ldg1
Where:
■ vnet1 is a unique interface name to the logical domain, assigned to this virtual network
device instance for reference on subsequent set-vnet or remove-vnet subcommands.
■ primary-vsw0 is the name of an existing network service (virtual switch) to which to
connect.

5. Specify the device to be exported by the virtual disk server as a virtual disk to the guest domain.
You can export a physical disk, disk slice, volumes, or file as a block device. The following
examples show a physical disk and a file.
■ Physical Disk Example. The first example adds a physical disk with these specifics.
primary# ldm add-vdsdev /dev/dsk/c2t1d0s2 vol1@primary-vds0
Where:
■ /dev/dsk/c2t1d0s2 is the path name of the actual physical device. When adding a
device, the path name must be paired with the device name.
■ vol1 is a unique name you must specify for the device being added to the virtual disk
server. The volume name must be unique to this virtual disk server instance, because this
name is exported by this virtual disk server to the clients for adding. When adding a
device, the volume name must be paired with the path name of the actual device.
■ primary-vds0 is the name of the virtual disk server to which to add this device.
■ File Example. This second example is exporting a file as a block device.
primary# ldm add-vdsdev backend vol1@primary-vds0
Where:
■ backend is the path name of the actual file exported as a block device. When adding a
device, the back end must be paired with the device name.
■ vol1 is a unique name you must specify for the device being added to the virtual disk
server. The volume name must be unique to this virtual disk server instance, because this
name is exported by this virtual disk server to the clients for adding. When adding a
device, the volume name must be paired with the path name of the actual device.
■ primary-vds0 is the name of the virtual disk server to which to add this device.

6. Add a virtual disk to the guest domain.
The following example adds a virtual disk to the guest domain ldg1.
primary# ldm add-vdisk vdisk1 vol1@primary-vds0 ldg1
Where:
■ vdisk1 is the name of the virtual disk.
■ vol1 is the name of the existing volume to which to connect.
■ primary-vds0 is the name of the existing virtual disk server to which to connect.

7. Set the auto-boot? and boot-device variables for the guest domain.
The first example command sets auto-boot? to true for guest domain ldg1.
primary# ldm set-var auto-boot\?=true ldg1
The second example command sets boot-device to vdisk1 for guest domain ldg1.
primary# ldm set-var boot-device=vdisk1 ldg1

8. Bind resources to the guest domain ldg1 and then list the domain to verify that it is bound.
primary# ldm bind-domain ldg1
primary# ldm list-domain ldg1
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
ldg1 bound ----- 5000 8 2G

9. To find the console port of the guest domain, you can look at the output of the preceding
list-domain subcommand.
You can see under the heading CONS that logical domain guest 1 (ldg1) has its console output
bound to port 5000.

10. Connect to the console of a guest domain fromanother terminal by logging into the control
domain and connecting directly to the console port on the local host.
$ ssh hostname.domain-name
$ telnet localhost 5000

11. Start the guest domain ldg1.
primary# ldm start-domain ldg1

Create Logical domain (guest VM):-

root@proddb01:~# ldm add-domain erpdbnode01

root@proddb01:~# ldm add-vcpu 128 erpdbnode01

root@proddb01:~# ldm add-memory 440G erpdbnode01

root@proddb01:~# ldm add-vnet vnet1 primary-vsw0 erpdbnode01

root@proddb01:~# ldm add-vdsdev /dev/dsk/c0t000B08000C004050d0 vol1@primary-vds0

root@proddb01:~# ldm add-vdisk vdisk1 vol1@primary-vds0 erpdbnode01

root@proddb01:~# ldm set-var auto-boot\?=true erpdbnode01

root@proddb01:~# ldm set-var boot-device=vdisk1 erpdbnode01

root@proddb01:~# ldm bind-domain erpdbnode01

root@proddb01:~# ldm list-domain erpdbnode01

NAME             STATE      FLAGS   CONS    VCPU  MEMORY   UTIL  NORM  UPTIME

erpdbnode01      bound      ------  5000    128   440G                

root@proddb01:~# ldm add-vdsdev /u02/sol-11_1-text-sparc.iso s10u7iso@primary-vds0

Failed to add device /u02/sol-11_1-text-sparc.iso

as s10u7iso@primary-vds0 because this device is already exported on LDom primary.

Volume s10u7iso already exists in vds primary-vds0

root@proddb01:~# ldm add-vdisk vdisk_iso s10u7iso@primary-vds0 erpdbnode01

root@proddb01:~# ldm bind-domain erpdbnode01

LDom erpdbnode01 cannot be bound because it is already bound

root@proddb01:~# ldm list-bindings -e erpdbnode01