Logical Domains Manager (LDOM)

The Logical Domains Manager is used to create and manage logical domains. There can be only
one Logical Domains Manager per server. The Logical Domains Manager maps logical domains
to physical resources.

Logical Domain roles

All logical domains are the same except for the roles that they are assigned. There are multiple
roles that logical domains can perform such as:

 Control domain
 Service domain
 I/O domain
 Root domain
 Guest domain

Control domain, as its name implies, controls the logical domain environment. It is used to
configure machine resources and guest domains, and provides services necessary for domain
operation, such as virtual console service. The control domain also normally acts as a service
domain.
Service domains present virtual services, such as virtual disk drives and network switches, to
other domains. In most cases, guest domains perform I/O via bridged access through services
domains, which are usually I/O domains and directly connected to the physical devices. Service
domains can provide virtual LANs and SANs as well as bridge through to physical devices. Disk
images can reside on complete local physical disks, shared SAN block devices, their slices, or
even on files contained on a local UFS or ZFS file system, or on a shared NFS export or iSCSI
target.
I/O domains have direct ownership of a PCI bus, or card on a bus, or Single Root I/O
Virtualization (SR-IOV) function, providing direct access to physical I/O devices, such as a
network card in a PCI controller. An I/O domain may use its devices to have native I/O
performance its own applications, or act as a service domain and share the devices to other
domains as virtual devices.
Root domains have direct ownership of PCIe "root complex" and all associated PCIe slots. This
can be used to grant access to physical I/O devices. A root domain is also an I/O domain. There
are a maximum of two root domains for the UltraSPARC T1 (Niagara) servers, one of which also
must be the control domain. UltraSPARC T2 Plus, SPARC T3, and SPARC T4 servers can have as
many as 4 root domains, limited by the number of PCIe root complexes installed on the server.
SPARC T5 servers can have up to 16 root complex domains. Multiple I/O domains can be
configured to provide resiliency against failures.
Guest domains run an operating system instance without performing any of the above roles,
but leverage the services provided by the above in order to run applications.
Resources
The following resources are supported:
core
CPU cores.
io
I/O devices, such as PCIe root complexes and their attached adapters and devices. Also
direct I/O-assignable devices and PCIe SR-IOV virtual functions.
mem, memory
Default memory size in bytes. Or specify gigabytes (G), kilobytes (K), or megabytes (M).
Virtualized memory of the server that can be allocated to guest domains.
vcc, vconscon
Virtual console concentrator service with a specific range of TCP ports to assign to each
guest domain at the time it is created.
vcpu
Each virtual CPU represents one CPU thread of a server. See your platform
documentation.
vdisk
Virtual disks are generic block devices backed by different types of physical devices,
volumes, or files. A virtual disk is not synonymous with a SCSI disk and, therefore,
excludes the target ID (tN) in the disk name. Virtual disks in a logical domain have the
following format: cNdNsN, where cN is the virtual controller, dN is the virtual disk
number, and sN is the slice.
vds, vdiskserver
Virtual disk server that allows you to export virtual disks to other logical domains.
vdsdev, vdiskserverdevice
Device exported by the virtual disk server. The device can be an entire disk, a slice on a
disk, a file, or a disk volume.
vnet
Virtual network device that implements a virtual Ethernet device and communicates
with other vnet devices in the system using the virtual network switch (vsw).
vsw, vswitch
Virtual network switch that connects the virtual network devices to the external
network and also switches packets between them.
Command Preparation
ldm add-vds service-name ldom
#ldm add-vds primary-vds primary
ldm add-vcc port-range=x-y vcc-name ldom
#ldm add-vcc port-range=5000-5100 primary-vcc primary

Enable Service Ldom

#svcadm enable vntsd

For the first time by default, primary domain use whole resources such as cpu, memory, io etc.
So we can reduce the cpu and memory from Primary Domain for Guest Domain.

Start reconfigure Primary Domain and then reboot the OS.

# ldm start-reconf primary

Command to Create Guest Domain.

Create Guest DOM
ldm add-domain [mac-addr=num] [hostid=num] [failure-policy=ignore|panic|reset|stop]
[master=master-ldom1,...,master-ldom4] ldom
#ldm add-domain Solaris11
Set CPU Guest Dom
ldm set-core number ldom
#ldm add-core 8 Solaris11

Set Memory Guest Dom

ldm set-memory size [unit] ldom
#ldm set-memory 64G Solaris11

Create Virtual Switch

ldm add-vsw [default-vlan-id=vlan-id] [pvid=port-vlan-id] [vid=vlan-id1,vlan-id2,...]
[mac-addr=num] [net-dev=device] [mode=sc] [mtu=size] [id=switch-id] vswitch-name ldom
#ldm add-vsw net-dev=net1 Solaris11-vsw primary

Create Virtual Net

ldm add-vnet [mac-addr=num] [mode=hybrid] [pvid=port-vlan-id] [vid=vlan-id1,vlan-id2,...]
[id=network-id] [mtu=size] if-name vswitch-name ldom
#ldm add-vnet vnet0 Solaris11-vsw Solaris11
Create Virtual Device
ldm add-vdsdev [-f] [options={ro,slice,excl}] [mpgroup=mpgroup] backend
volume-name@service-name
#ldm add-vdsdev /dev/dsk/c0t0d0s2 Solaris11_os@primary-vds

Create Virtual Disk

ldm add-vdisk [timeout=seconds] [id=disk-id] disk-name volume-name@service-name ldom
#ldm add-vdisk Solaris11_os Solaris11_os@primary-vds Solaris11

Bind Config Guest Dom

ldm bind ldom
#ldm bind Solaris11

Set Guest Dom to Autoboot False

ldm set-var var-name=[value]... ldom
#ldm set-var auto-boot\?=false GGJKTOAPP02

Start Guest Dom

ldm start ldom
#ldm start Solaris11

Console to Guest Dom

#telnet 0 5000
==============================================================================
Check List Services for Logical Domains
#ldm ls-services

Check configuration net Guest Dom

ldm ls-dom [-e] [-l] [-o format] [-p][ [ldom...]
#ldm ls –o net Solaris11

Check configuration disk Guest Dom

ldm ls-dom [-e] [-l] [-o format] [-p][ [ldom...]
#ldm ls –o disk Solaris11

Check list devices

#ldm ls-devices