|Skip Navigation Links|
|Exit Print View|
|Oracle VM Server for SPARC 3.0 Administration Guide Oracle VM Server for SPARC|
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 and the Oracle Solaris 11 OS
Virtual I/O devices – Supported in at least the Oracle Solaris 10 10/08 OS and the Oracle Solaris 11 OS
Cryptographic units – Supported in at least the Oracle Solaris 10 8/11 OS and the Oracle Solaris 11 OS
Memory – Supported starting with the Oracle VM Server for SPARC 2.0 release (see Using Memory Dynamic Reconfiguration)
CPU whole cores – Supported starting with the Oracle VM Server for SPARC 2.0 release (see Required and Recommended Oracle Solaris OS Versions in Oracle VM Server for SPARC 3.0 Release Notes)
Physical I/O devices – Not supported
After the next reboot of the OS
After a stop and start of a logical domain if no OS is running
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.
While a delayed reconfiguration is in progress, other reconfiguration requests for that domain are deferred until it is rebooted, or stopped and started.
The ldm cancel-reconf command cancels delayed reconfiguration operations on the domain. For more information about how to use the delayed reconfiguration feature, see the ldm(1M) man page.
Note - You cannot use the ldm cancel-reconf command if any other ldm remove-* commands have already performed a delayed reconfiguration operation on virtual I/O devices. The ldm cancel-reconf command fails in this circumstance.
You can use delayed reconfiguration to decrease resources on the control domain. To remove a large number of CPUs from the control domain, see Removing a Large Number of CPUs From the Control Domain Fails in Oracle VM Server for SPARC 3.0 Release Notes. To remove large amounts of memory from the control domain, see Decrease the Control Domain's Memory.