ldom installation and configuration[1]

8/6/2019 LDOM Installation and Configuration[1]

1/34

2009 Wi ro Ltd - Confidential

Ldom (Logical Domain)

Ankit Padegaonkar

April 2010

Installation & Configuration


2/34

2009 Wi ro Ltd - Confidential2


Hypervisor :

The SPARC hypervisor is a small firmware layer that

provides a stable virtualized machine architecture to which an

operating system can be written. Sun servers that use thehypervisor provide hardware features to support the hypervisor'scontrol over a logical operating system's activities.

Each logical domain is only permitted to observe and

interact with those server resources that are made available to itby the hypervisor. The Logical Domains Manager enables you tospecify what the hypervisor should do through the controldomain.

Introduction


3/34


4/34




5/34



The figure on previous slide shows the hypervisor supportingtwo logical domains. It also shows the following layers that makeup the Logical Domains functionality:

Applications, or user/services

Kernel, or operating systems

Firmware, or hypervisor

Hardware, including CPU, memory, and I/O


6/34



The hypervisor software is responsible for maintaining the

separation between logical domains. The hypervisor software alsoprovides logical domain channels (LDCs) that enable logicaldomains to communicate with each other. LDCs enable domains toprovide services to each other, such as networking or disk services.

The service processor (SP), also known as the systemcontroller (SC), monitors and runs the physical machine, but it doesnot manage the logical domains. The Logical Domains Manager

manages the logical domains.


7/34

2009 Wi ro Ltd - Confidential7 2009 Wi ro Ltd - Confidential7

The Logical Domains Manager is used to create and managelogical domains, as well as map logical domains to physicalresources.

Roles for Logical Domains :

All logical domains are the same and can be distinguished from

one another based on the roles that you specify for them. Therefollowing are the roles that logical domains can perform:

Control domain

The Logical Domains Manager runs in this domain, whichenables you to create and manage other logical domains, and to

Logical Domains Manager


8/34


allocate virtual resources to other domains. You can have only onecontrol domain per server. The control domain is the first domaincreated when you install the Logical Domains software. The controldomain is named primary and also known as I/O domain or servicedomain.

Guest domain

A guest domain is a non-I/O domain that consumes virtualdevice services that are provided by one or more service domains.

A guest domain does not have any physical I/O devices, but only hasvirtual I/O devices, such as virtual disks and virtual networkinterfaces.


9/34


Dynamic Reconfiguration :

Dynamic reconfiguration (DR) is the ability to add or

remove resources while the operating system is running. The abilityto perform dynamic reconfiguration of a particular resource type is

dependent on having support in the OS running in the logicaldomain.

Dynamic reconfiguration is supported for the followingresources:

Virtual CPUs Supported in all versions of the Solaris 10 OS

Virtual I/O devices Supported in at least the Solaris 1010/08 OS


10/34


MemoryNot supported

Physical I/O devices Not supported

To use the dynamic reconfiguration capability, the LogicalDomains dynamic reconfiguration daemon (drd), must be running inthe domain that you want to change.


11/34


Delayed Reconfiguration :

In contrast to dynamic reconfiguration operations that take

place immediately, delayed reconfiguration operations take effect inthe following circumstances:

After the next reboot of the OSAfter a stop and start of the logical domain

When a delayed reconfiguration is in progress on the control

domain, other reconfiguration requests for the control domain are

deferred until it is rebooted, or stopped and started. Also, when adelayed reconfiguration is outstanding for the control domain,reconfiguration requests for other logical domains are severelyrestricted and will fail with an appropriate error message.


12/34 2009 Wi ro Ltd - Confidential12 2009 Wi ro Ltd - Confidential12

Persistent Configurations :

You can use the ldm config command to store the current

configuration of a logical domain on the service processor. You canadd a configuration, specify a configuration to be used, remove a

configuration, and list the configurations.



Download the zip file (LDoms_Manager-1_2.zip) from the SunSoftware Download site.

Unzip the zip file.

Installing Logical Domains Software



b



Creating Default Services :

You must create the following virtual default services

initially to be able to use them later:

vdiskserver

virtual disk server vswitch virtual switch service

vconscon virtual console concentrator service

Setting Up Services and Logical Domains



1. Create a virtual disk server (vds) to allow importing virtualdisks into a logical domain. For example, the followingcommand adds a virtual disk server (primary-vds0) to thecontrol domain (primary).

2. Create a virtual console concentrator (vcc) service for use bythe virtual network terminal server daemon (vntsd) and as aconcentrator for all logical domain consoles. For example, thefollowing command would add a virtual console concentrator

service (primary-vcc0) with a port range from 5000 to 5100 tothe control domain (primary).



3. Create a virtual switch service (vsw) to enable networkingbetween virtual network (vnet) devices in logical domains. Forexample, the following command would add a virtual switchservice (primary-vsw0) on network adapter driver e1000g0 tothe control domain (primary).

This command automatically allocates a MAC address to

the virtual switch. You can specify your own MAC address as anoption to the ldm add-vsw command.



4. Verify the services have been created by using the list-servicessubcommand. Your output should look some how similar tothe following.



Initial Configuration of the Control Domain :1. Assign cryptographic resources to the control domain.

Note If you have any cryptographic devices in the controldomain, you cannot dynamically reconfigure CPUs. So if you are

not using cryptographic devices, set-mau to 0.The following example would assign one cryptographic

resource to the control domain, primary. This leaves theremainder of the cryptographic resources available to a guestdomain.



2. Assign virtual CPUs to the control domain. For example, thefollowing command would assign 4 virtual CPUs to the controldomain, primary. This leaves the remainder of the virtual CPUsavailable to a guest domain.

3. Assign memory to the control domain. For example, thefollowing command would assign 4 gigabytes of memory to thecontrol domain, primary. This leaves the remainder of the

memory available to a guest domain.



4. Add a logical domain machine configuration to the serviceprocessor (SP). For example, the following command wouldadd a configuration called initial.

5. Verify that the configuration is ready to be used at the nextreboot.



Rebooting to Use Logical Domains :Shut down and reboot the control domain.

Note: Before rebooting the server, rename the/etc/hostname.interface_name file to /etc/hostname.vsw0 (thename of the virtual switch).



Enable the Virtual Network Terminal Server Daemon :1. Use the svcadm command to enable the virtual network

terminal server daemon, vntsd.

2. Use the svcs command to verify that the vntsd is enabled.



Creating and Starting a Guest Domain :The guest domain must run an operating system that

understands both the sun4v platform and the virtual devicespresented by the hypervisor. Currently, this means that you mustrun at least the Solaris 10 11/06 OS. Running the Solaris 10 5/09 OSprovides you with all the Logical Domains 1.2 features.

1. Create a logical domain.

For example, the following command would create a guestdomain named ldg1.



2. Add CPUs to the guest domain.For example, the following command would add four virtualCPUs to guest domain ldg1.

3. Add memory to the guest domain.

For example, the following command would add 2 gigabytes ofmemory to guest domain ldg1.

4. Add a virtual network device to the guest domain.

For example, the following command would add a virtualnetwork device with these specifics to the guest domain ldg1.



5. Specify the device to be exported by the virtual disk server as avirtual disk to the guest domain. You can export a physical disk,disk slice, volumes, or file as a block device. The followingexamples show a physical disk and a file.

Physical Disk Example: The first example adds a physical disk

with these specifics.

File Example. This second example is exporting a file as ablock device.



6. Add a virtual disk to the guest domain.The following example adds a virtual disk to the guest domainldg1.

7. Set auto-boot and boot-device variables for the guest domain.

The first example command sets auto-boot\? to true for guestdomain ldg1.

The second example command sets boot-device to vdisk forthe guest domain ldg1.



8. Bind resources to the guest domain ldg1 and then list thedomain to verify that it is bound.

9. Start the guest domain ldg1.

10. Taking the console of guest domain from the control domain.



1. Insert the Solaris 10 OS DVD into the DVD drive.2. Stop the volume management daemon, vold on the primary

domain.

3. Stop and unbind the guest domain (ldg1).Then add the DVDwith DVDROM media as a secondary volume(dvd_vol@primary-vds0) and virtual disk (vdisk_cd_media), forexample c0t0d0s2 is where the Solaris OS media resides

Installing Solaris OS on a Guest Domain



4. Check to see that the DVD is added as a secondary volume andvirtual disk.


31/34


5. Bind and start the guest domain (ldg1).


32/34


6. Show the device aliases in the client OpenBoot PROM.In this example, see the device aliases for vdisk_cd_media,

which is the SolarisDVD, and vdisk1, which is a virtual disk on

which you can install the Solaris OS.


33/34


7. On the guest domain's console, boot from vdisk_cd_media(disk@1) on slice f.

8. Continue with the Solaris OS installation menu.


34/34

Ankit Padegaonkar

Wipro System Integration (SI)Team

[email protected]

Thank You

ldom installation and configuration[1]

Documents