Backup guest domain configuration in xml and recreate the guest domain with xml file

This example is just to demonstrate how to save and restore guest domain.

Backup the xml file

#ldm list-constraints -x test-ldg1 > /var/tmp/test-ldg1.xml

bring down the guest domain OS -> stop the guest domain -> unbind the guest domain

# ldm list test-ldg1
NAME             STATE      FLAGS   CONS    VCPU  MEMORY   UTIL  UPTIME
test-ldg1 inactive   ——          16    8G

#ldm destroy test-ldg1

#ldm list (will not show test-ldg1 guest domain)

Impot the guest domain using backu xml file  /var/tmp/test-ldg1.xml

#ldm add-domain -i /var/tmp/test-ldg1.xml

Verify the domain details

# ldm list test-ldg1
NAME             STATE      FLAGS   CONS    VCPU  MEMORY   UTIL  UPTIME
test-ldg1 inactive   ——          16    8G

bind the guest domain -> start the domain -> start the OS on guest domain

#ldm add-domain -i /var/tmp/test-ldg1.xml

Status is inactive
test-ldg1 inactive   ——          16    8G

#ldm bind test-ldg1

Status is bound
test-ldg1 bound      ——  5000    16    8G

#ldm start test-ldg1
LDom test-ldg1 started

status is Active
test-ldg1 active     -t—-  5000    16    8G       3.8%  2s

Advertisements

LDOM reference

http://dbhk.wordpress.com/category/ldom/

http://gdesaboyina.wordpress.com/2012/08/03/parsing-ldom-db-xml/

http://docs.oracle.com/cd/E35434_01/pdf/E23807.pdf

http://unixsecure.net/ldom-%E2%80%93-ldm-configuration-lost-when-control-domain-reboots/

Difference between LDOMS’s and Zones (containers)

Today’s meeting one guy was speaking LDOM’s and Zones as one and the same. I thought I will write the difference between LDOM’s and Zones

LDOM’s can be created only on sun4v based cpu servers as they come with hypervisor, which is important hardware layer that give power of virtualization. Sun4v cpu latest server models are T4 series servers T4-1 (1 socket, 8 core, 8 threads per core=64 threads per server), T4-2 (2 socket, 2×64 threads), T4-4 (4 socket, 4×64 threads).

LDOMS have independent cpu, memory, file system and most important Kernel. These domains have their own console connectivity and boot prompt,

LDOMs are created and managed from service domain. Every LDOM needs it’s own administrative efforts like patching,

LDOMs now called as Oracle VM servers

 

Zones (containers) do not required any specific hardware as it’s a purely software based virtual technology. Zones also called as containers, reason is you will create compartments in a OS, sharing kernel, cpu, memory and file system

Zones (containers) share everything, CPU, Memory, File Systems and most important thing Kernel. Global zone runs on solaris 10, you can have non global zones with solaris 8, solaris 9 and even linux.

Zones (containers) zones are created and managed through global zones, most of the single administrative task will be applicable to all zones like patching.

 

Below link has a nice presentation on LDOMs, but beware it’s older version

http://unixfoo.blogspot.hk/2008/04/solaris-ldom-virtualization-documents.html

http://en.wikipedia.org/wiki/Logical_Domains

http://en.wikipedia.org/wiki/Solaris_Containers