Sun Microsystems, Inc.  Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-71-1019970.1
Update Date:2011-05-27
Keywords:

Solution Type  Technical Instruction Sure

Solution  1019970.1 :   How to Assign Resources to Domains with the Oracle VM Server for SPARC (Formerly LDOM)  


Related Items
  • Sun SPARC Enterprise T2000 Server
  •  
  • Sun Netra T5440 Server
  •  
  • Sun SPARC Enterprise T5120 Server
  •  
  • Sun Blade T6300 Server Module
  •  
  • Sun SPARC Enterprise T1000 Server
  •  
  • Sun SPARC Enterprise T5140 Server
  •  
  • Sun Fire T2000 Server
  •  
  • Sun Blade T6320 Server Module
  •  
  • Sun Netra T2000 Server
  •  
  • Sun Netra T5220 Server
  •  
  • Sun SPARC Enterprise T5440 Server
  •  
  • Sun Blade T6340 Server Module
  •  
  • Sun Fire T1000 Server
  •  
  • Sun SPARC Enterprise T5220 Server
  •  
  • Sun SPARC Enterprise T5240 Server
  •  
  • Solaris SPARC Operating System
  •  
Related Categories
  • GCS>Sun Microsystems>Operating Systems>Solaris Operating System
  •  
  • GCS>Sun Microsystems>Servers>CMT Servers
  •  
  • GCS>Sun Microsystems>Servers>NEBS-Certified Servers
  •  

PreviouslyPublishedAs
250007


Applies to:

Sun Blade T6340 Server Module - Version: Not Applicable and later   [Release: N/A and later ]
Sun Netra T2000 Server - Version: Not Applicable and later    [Release: Unknown Release and later]
Sun Netra T5220 Server - Version: Not Applicable and later    [Release: Unknown Release and later]
Sun Netra T5440 Server - Version: Not Applicable and later    [Release: Unknown Release and later]
Sun Fire T1000 Server - Version: Not Applicable and later    [Release: Unknown Release and later]
All Platforms

Goal

Inadequate resources(CPU/MAU/Memory)assigned in LDOM configurations can resulted in various issues on the LDOM domains. This document provide steps to check through to ensure appropriate resources are assigned to LDOM domains.

This document provides steps to verify and set the LDOM configurations to ensure that the appropriate resources (VCPU/Memory/MAU) are assigned to the LDOM domains.  However, the actual amount of each resources needed to be allocated is dependent  on the guest operating system.  For recommended and minimum resource requirements, please refer to the installation guide for the operating system you are using.



Symptoms:

LDOM performance slow
Unable to enable crypto unit
Unable to jumpstart
Unable to boot
Unable to create domain.
Domain hang
Unable to add moreVCPUs/MAUs
Unable to install OS

Solution

Available Documents:

For Solaris 10 resource requirements, please refer to “System Requirements and Recommendations” in the Solaris 10 Installation Guide: Planning for Installation and Upgrade available on http://download.oracle.com/docs/cd/E19253-01/821-0441/index.html.

Further details on various LDOM  system requirements, please refer to the Release Notes of the specific version of Logical Domian Manager available on http://download.oracle.com/docs/cd/E19608-01/index.html .


Please note that Primary domain is also referred as Control domain.

Steps to Follow
Do take note that this document provides only steps to review and define resources assigned to a domain. It does not provide or recommend any actual amount of resources to be allocated as this is dependent on the actual guest operating system and applications requirements.

Do take note that this document provides only steps to review and define resources assigned to a domain. It does not provide or recommend any actual amount of resources to be allocated as this is dependent on the actual guest operating system and applications requirements.

Definitions

VCPU
Virtual Central Processing Unit. The CPU threads residing the sun4v cpus are presented as VCPUs within LDOM nomenclature. Each CPU thread corresponds to a VCPU.

Memory
Memory assigned to the domain. Unit in default in bytes. Can be specified in gigabytes(G), kilobytes(K), or megabytes(M).

MAU
Modular Arithmetic Unit, also know as cryptographic unit available in the sun4v processors.


LDOM configuration can reviewed and amended through the /opt/SUNWldm/bin/ldm(1M) command. Here we outline the steps to review and then steps to amend VCPU, Memory and MAU resources assigned to a domain.


Review VCPU/Memory/MAU assigned to a domain


A summary of resources allocated to all domains on the system can be displayed with the ldm(1M) list subcommand.

For example:

# /opt/SUNWldm/bin/ldm list
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
primary active -n-cv SP 8 4G 17% 32d 2h 3m
guestdom1 active -n--- 5001 4 4G 0.5% 38d 13h 44m
guestdom2 active -n--- 5002 4 4G 1.0% 38d 13h 45m
guestdom3 active -n--- 5003 4 4G 0.7% 38d 13h 45m
guestdom4 active -n--- 5004 4 4G 1.2% 38d 13h 46m
guestdom5 active -n--- 5005 4 4G 0.8% 38d 13h 48m
guestdom6 active -n--- 5006 4 4G 0.7% 38d 21h 58m



For an extensive review of the resources allocated to a specific domain, please use the ldm(1M) list-domain sub command. Take note of the VCPU, MEMORY and MAU section for the individual resources assigned to the domain.

For example:

# /opt/SUNWldm/bin/ldm list-domain -l guestdom1
NAME STATE FLAGS CONS VCPU MEMORY UTIL UPTIME
guestdom1 active -n--- 5001 4 4G 0.4% 38d 13h 51m
SOFTSTATE
Solaris running
VCPU
VID PID UTIL STRAND
0 4 100% 100%
1 5 1.1% 100%
2 6 0.9% 100%
3 7 0.0% 100%
MAU
ID CPUSET
0 (8, 9, 10, 11, 12, 13, 14, 15)
MEMORY
RA PA SIZE
0x8000000 0x108000000 2G
0x408000000 0x688000000 2G
...
Setting of VCPU/Memory/MAU resources for a domain


Allocation of VCPU

To set the number of VCPUs for a given domain, use the ldm(1M) set-vcpu subcommand:

# /opt/SUNWldm/bin/ldm set-vcpu  ldom


To add additional VCPUs to a given domain, use the ldm(1M) add-vcpu subcommand:

# /opt/SUNWldm/bin/ldm add-vcpu  ldom


There are limited number of VCPUs on a given machine. There are times that one may want to reduce the number of VCPUs from one domain, and then assign them to another domain.

To remove a number of VCPU assigned to a domain, used the ldm(1M) remove-vcpu subcommand.

# /opt/SUNWldm/bin/ldm remove-vcpu  ldom



Allocation of Memory

To set the amount of memory for a given domain, use the ldm(1M) set-memory sub command:

# /opt/SUNWldm/bin/ldm set-memory  ldom


To increase additional memory to a given domain, use the ldm(1M) add-memory subcommand:

# /opt/SUNWldm/bin/ldm add-memory  ldom


There are limited amount of memory on a given machine. There are times that one may want to reduce the amount of memory from one domain, and then assign them to another domain.

To remove certain amount of memory assigned to a domain, used the ldm(1M) remove-memory sub command.

# /opt/SUNWldm/bin/ldm remove-memory  ldom



Allocation of MAU

MAUs can only be assigned to specific domain only if at least of the VCPU from the owning processor core is assigned to the domain. Please refer to Page 19 & 26 of Beginners Guide to LDOMs, available at www.sun.com/blueprints.


To set the number of MAUs for a given domain, use the ldm(1M) set-mau subcommand:

# /opt/SUNWldm/bin/ldm set-mau  ldom


To add additional MAUs to a given domain, use the ldm(1M) add-mau subcommand:

# /opt/SUNWldm/bin/ldm add-mau  ldom


There are limited number of MAUs on a given machine. There are times that one may want to reduce the number of MAUs from one domain, and then assign them to another domain.

To remove a number of MAU assigned to a domain, used the ldm(1M) remove-mau subcommand.

# /opt/SUNWldm/bin/ldm remove-mau  ldom


Saving the new configuration

The newly configured resource, though may have been assigned to the target domain dynamically, the configurations need to be saved to the system controller (SC) for it to persist across reboot of the primary domain.

In order to store the configuration, use the ldm(1M) add-config subcommand:
# /opt/SUNWldm/bin/ldm add-config config_name


For example, saving the current configuraton as cfg090221:
# /opt/SUNWldm/bin/ldm add-config cfg090221

On LDoms 1.0.3 or earlier, issuing the ldm(1M) list-config subcommand will show that configuration named cfg090221 will be the next active configuration(Though the changes may indeed be already active) when the primary domain reboots:
# /opt/SUNWldm/bin/ldm list-config
factory-default
initconfig
cfg090113 [current]
cfg090221 [next]

On LDoms 1.1, issuing the ldm(1M) list-config subcommand will show that configuration named cfg090221 is shown as [current], which provides a better reflection that the changes are already in active and also will be the next active configuration when the primary domain reboots:
# /opt/SUNWldm/bin/ldm list-config
factory-default
initconfig
cfg090113
cfg090221 [current]

If after the above steps fail to make the necessary resource allocation, please contact Sun Support with the following information:

- The latest explorer output using the latest version of explorer script.
- The if there is any specific error, please provide session log illustrating the error concerned.

Please refer to Sun[TM] Explorer X.XX Data Collector for the latest Explorer Script 1002383.1.

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a discussion in the My Oracle Support Community, Oracle Solaris System Administration Community.


Internal Comments
This document contains normalized content and is managed by the the Domain Lead(s) of the respective domains. To notify content owners of a knowledge gap contained in this document, and/or prior to updating this document, please contact the domain engineers that are managing this document via the "Document Feedback" alias(es) listed below:

Normalization Lead: global-systems-tsc-domain-engineers@Sun.COM


Normalized, ldom, ldm


Attachments
This solution has no attachment
  Copyright © 2011 Sun Microsystems, Inc.  All rights reserved.
 Feedback