1. Overview of the Oracle VM Server for SPARC Software
2. Installing and Enabling Software
4. Setting Up Services and the Control Domain
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
Using Memory Dynamic Reconfiguration
Tracking the Progress of a Memory DR Request
Memory Reconfiguration of the Control Domain
Decrease the Control Domain's Memory
Dynamic and Delayed Reconfiguration
Memory Alignment for Active Domains
Memory Alignment for Bound Domains
Memory Alignment for Inactive Domains
Listing CPU Power-Managed Strands
List CPU Power-Managed Strands
Using Dynamic Resource Management
Show Syntax Usage for ldm Subcommands
Utilization Statistic Definition
Generate an Extended List (-e)
Generate a Parseable, Machine-Readable List (-p)
Generate a Subset of a Long List (-o format)
List Constraints for One Domain
List Constraints in XML Format
List Constraints in a Machine-Readable Format
12. Performing Other Administration Tasks
A. Oracle VM Server for SPARC Physical-to-Virtual Conversion Tool
B. Oracle VM Server for SPARC Configuration Assistant
C. Logical Domains Manager Discovery
D. Using the XML Interface With the Logical Domains Manager
A system that runs the Oracle VM Server for SPARC software is able to configure resources, such as virtual CPUs, virtual I/O devices, cryptographic units, and memory. Some resources can be configured dynamically on a running domain, while others must be configured on a stopped domain. If a resource cannot be dynamically configured on the control domain, you must first initiate a delayed reconfiguration. The delayed reconfiguration postpones the configuration activities until after the control domain has been rebooted.
Dynamic reconfiguration (DR) enables resources to be added or removed while the operating system (OS) is running. The capability to perform DR of a particular resource type is dependent on having support in the OS running in the logical domain.
Dynamic reconfiguration is supported for the following resources:
Virtual CPUs – Supported in all versions of the Oracle Solaris 10 OS
Virtual I/O devices – Supported in at least the Solaris 10 10/08 OS
Cryptographic units – Supported in at least the Oracle Solaris 10 9/10 OS
Memory – Supported starting with the Oracle VM Server for SPARC 2.0 release (see Using Memory Dynamic Reconfiguration)
Physical I/O devices – Not supported
To use the DR capability, the Logical Domains DR daemon, drd, must be running in the domain that you want to change. See the drd(1M) man page.
In contrast to DR operations that take place immediately, delayed reconfiguration operations take effect in the following circumstances:
After the next reboot of the OS
After a stop and start of a logical domain
Starting with the Logical Domains 1.2 software, delayed reconfiguration operations are restricted to the control domain. For all other domains, you must stop the domain to modify the configuration unless the resource can be dynamically reconfigured.
Starting with the Oracle VM Server for SPARC 2.0 software, you must first initiate a delayed reconfiguration on the control domain prior to performing resource configuration operations. You can initiate the delayed reconfiguration by using the ldm start-reconf primary command.
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 a delayed reconfiguration is pending for the control domain, reconfiguration requests for other logical domains are severely restricted and will fail with an appropriate error message.
The ldm cancel-operation reconf command cancels delayed reconfiguration operations on the control domain. You can list delayed reconfiguration operations by using the ldm list-domain command. For more information about how to use the delayed reconfiguration feature, see the ldm(1M) man page.
Note - You cannot use the ldm cancel-operation reconf command if any other ldm remove-* commands have already performed a delayed reconfiguration operation on virtual I/O devices. The ldm cancel-operation reconf command fails in these circumstances.