JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Oracle VM Server for SPARC 2.1 Administration Guide     Oracle VM Server for SPARC
search filter icon
search icon

Document Information


Part I Oracle VM Server for SPARC 2.1 Software

1.  Overview of the Oracle VM Server for SPARC Software

2.  Installing and Enabling Software

3.  Security

4.  Setting Up Services and the Control Domain

5.  Setting Up Guest Domains

6.  Setting Up I/O Domains

7.  Using Virtual Disks

8.  Using Virtual Networks

9.  Migrating Domains

10.  Managing Resources

Resource Reconfiguration

Dynamic Reconfiguration

Delayed Reconfiguration

Resource Allocation

CPU Allocation

Enabling the Whole-Core Constraint

Disabling the Whole-Core Constraint

Allocating CPUs to the Control Domain

Interactions Between the Whole-Core Constraint and Other Domain Features

CPU Dynamic Reconfiguration

Dynamic Resource Management

Domain Migration

Power Management

Using Memory Dynamic Reconfiguration

Adding Memory

Removing Memory

Tracking the Progress of a Memory DR Request

Canceling a Memory DR Request

Partial Memory DR Requests

Memory Reconfiguration of the Control Domain

Decrease the Control Domain's Memory

Dynamic and Delayed Reconfiguration

Memory Alignment

Memory Alignment for Active Domains

Memory Alignment for Bound Domains

Memory Alignment for Inactive Domains

Adding Unaligned Memory

Memory DR Examples

Using Power Management

Listing Power-Managed CPU Strands and Virtual CPUs

List Power-Managed CPU Strands

List Power-Managed CPUs

Using Dynamic Resource Management

Listing Domain Resources

Machine-Readable Output

Show Syntax Usage for ldm Subcommands

Flag Definitions

Utilization Statistic Definition

Viewing Various Lists

Show Software Versions (-V)

Generate a Short List

Generate a Long List (-l)

Generate an Extended List (-e)

Generate a Parseable, Machine-Readable List (-p)

Generate a Subset of a Long List (-o format)

List a Variable

List Bindings

List Configurations

List Devices

List Available Memory

List Services

Listing Constraints

List Constraints for One Domain

List Constraints in XML Format

List Constraints in a Machine-Readable Format

11.  Managing Configurations

12.  Performing Other Administration Tasks

Part II Optional Oracle VM Server for SPARC Software

13.  Oracle VM Server for SPARC Physical-to-Virtual Conversion Tool

14.  Oracle VM Server for SPARC Configuration Assistant

15.  Using the Oracle VM Server for SPARC Management Information Base Software

16.  Logical Domains Manager Discovery

17.  Using the XML Interface With the Logical Domains Manager



Using Dynamic Resource Management

You can use policies to determine how to automatically perform DR activities. At this time, you can only create policies to govern the dynamic resource management of virtual CPUs.


Caution - The following restrictions affect CPU dynamic resource management (DRM):

  • When PM is in elastic mode, DRM cannot be enabled.

  • Any change from performance mode to elastic mode is delayed while DRM is enabled.

  • Ensure that you disable CPU DRM prior to performing a domain migration operation.

  • DRM policies do not apply to domains that are configured with the whole-core constraint.

A resource management policy specifies under what conditions virtual CPUs can be automatically added to and removed from a logical domain. A policy is managed by using the ldm add-policy, ldm set-policy, and ldm remove-policy commands:

ldm add-policy [enable=yes|no] [priority=value] [attack=value] [decay=value]
  [elastic-margin=value] [sample-rate=value] [tod-begin=hh:mm[:ss]]
  [tod-end=hh:mm[:ss]] [util-lower=percent] [util-upper=percent] [vcpu-min=value]
  [vcpu-max=value] name=policy-name ldom...
ldm set-policy [enable=[yes|no]] [priority=[value]] [attack=[value]] [decay=[value]]
  [elastic-margin=[value]] [sample-rate=[value]] [tod-begin=[hh:mm:ss]]
  [tod-end=[hh:mm:ss]] [util-lower=[percent]] [util-upper=[percent]] [vcpu-min=[value]]
  [vcpu-max=[value]] name=policy-name ldom...
ldm remove-policy [name=]policy-name... ldom

For information about these commands and about creating resource management policies, see the ldm(1M) man page.

A policy is in effect during the times specified by the tod-begin and tod-end properties. The time specified by tod-begin must be earlier than the time specified by tod-end in 24-hour period. By default, values for the tod-begin and tod-end properties are 00:00:00 and 23:59:59, respectively. When the default values are used, the policy is always in effect.

The policy uses the value of the priority property to specify a priority for a dynamic resource management (DRM) policy. Priority values are used to determine the relationship between DRM policies on a single domain and between DRM-enabled domains on a single system. Lower numerical values represent higher (better) priorities. Valid values are between 1 and 9999. The default value is 99.

The behavior of the priority property depends on the availability of a pool of free CPU resources, as follows:

For example, the ldg1 and ldg2 domains both have DRM policies in effect. The priority property for the ldg1 domain is 1, which is more favorable than the priority property value of the ldg2 domain (2). The ldg1 domain can dynamically remove a CPU resource from the ldg2 domain and assign it to itself in the following circumstances:

The policy uses the util-high and util-low property values to specify the high and low thresholds for CPU utilization. If the utilization exceeds the value of util-high, virtual CPUs are added to the domain until the number is between the vcpu-min and vcpu-max values. If the utilization drops below the util-low value, virtual CPUs are removed from the domain until the number is between the vcpu-min and vcpu-max values. If vcpu-min is reached, no more virtual CPUs can be dynamically removed. If the vcpu-max is reached, no more virtual CPUs can be dynamically added.

Example 10-4 Adding Resource Management Policies

For example, after observing the typical utilization of your systems over several weeks, you might set up policies to optimize resource usage. The highest usage is daily from 9:00 a.m. to 6:00 p.m. Pacific, and the low usage is daily from 6:00 p.m. to 9:00 a.m. Pacific.

Based on this system utilization observation, you decide to create the following high and low policies based on overall system utilization:

The following ldm add-policy command creates the high-usage policy to be used during the high utilization period on the ldom1 domain.

The following high-usage policy does the following:

# ldm add-policy tod-begin=09:00 tod-end=18:00 util-lower=25 util-upper=75 \ vcpu-min=2 vcpu-max=16 attack=1 decay=1 priority=1 name=high-usage ldom1

The following ldm add-policy command creates the med-usage policy to be used during the low utilization period on the ldom1 domain.

The following med-usage policy does the following:

# ldm add-policy tod-begin=18:00 tod-end=09:00 util-lower=10 util-upper=50 \ vcpu-min=2 vcpu-max=16 attack=1 decay=1 priority=1 name=med-usage ldom1