This section explains how to modify L-Server specifications. Use the following procedure to modify L-Server specifications:
[Solaris Zones]
Calculate the cap value to configure for the non-global zone from the number of CPUs and the CPU performance.
For details, refer to "C.7.6 Creating an L-Server" in the "Setup Guide CE".
The specifications of an L-Server linked with a virtual machine on a VM host not managed with server management software cannot be modified from the ROR console. Modify them from the global zone.
The Procedure when Using the GUI
Right-click the target L-Server in the orchestration tree, and select [Change Settings]-[Modify Specification] from the popup menu.
The [Modify an L-Server] dialog is displayed.
Change the values.
The current values for each item are displayed in the [Modify an L-Server] dialog. Items that have been changed are indicated with an asterisk ("*") in front of the item.
For details about the range of the value that can be specified, refer to "16.2.2 [Server] Tab" or "16.3.2 [Server] Tab".
Click <OK>.
When making changes while the power of the virtual L-Server is on, only the configuration of the virtual L-Server can be changed.
When changes were made while a virtual L-Server was powered on, follow the procedures for the OS's running on the virtual L-Server to have the changes recognized by the OS's.
The Procedure From the Command Line
Execute rcxadm lserver modify or rcxadm lserver set.
For details on the rcxadm lserver modify command and the rcxadm lserver set command, refer to "3.6 rcxadm lserver" in the "Reference Guide (Command/XML) CE".
When making changes while the power of the virtual L-Server is on, only the configuration of the virtual L-Server can be changed.
When changes were made while a virtual L-Server was powered on, follow the procedures for the OS's running on the virtual L-Server to have the changes recognized by the OS's.
Changeable Items
The items for which specifications can be changed differ depending on whether the L-Server is physical or virtual.
Changing Physical L-Server Specifications
The following items can be changed when the power status of the physical L-Server is OFF.
FC path
Boot Mode
CPU Performance (*)
Number of CPUs (*)
Memory Size (*)
* Note: Can be specified when using blade servers. When you start the L-Server after setting "Resource release" (for allocating and releasing resources to and from L-Servers) and adjusting CPU and memory settings, a physical server will be selected according to the modified conditions.
Changing Virtual L-Server Specifications
The following items can be changed when the power status of the virtual L-Server is ON. For details, refer to the manuals of VM products.
CPU Performance
[OVM for SPARC]
The CPU Performance cannot be changed.
Number of CPUs
Memory Size
OS Type (When no images are not deployed)
[OVM for x86 2.2] [Solaris Zones] [OVM for SPARC] [Citrix Xen] [OVM for x86 3.2]
The OS type cannot be changed, regardless of whether images are deployed or not.
[KVM]
When changing the specifications for the OS types (when images have not been deployed) of virtual L-Servers, for KVM it is necessary to perform settings based on the OS type that the user intends to install.
When the OS type differs from the OS installed on the virtual L-Server, operation is not guaranteed.
The items to which L-Server can change the specification in the state of power supply ON is different according to the VM product. For details, refer to "Table 17.2 Items that can be changed while the power is on".In addition, the specification change in the state of power supply ON cannot do Citrix XenServer.
Resource Name | Modification | VMware | Hyper-V | KVM | Solaris Zones | OVM for SPARC | OVM for x86 3.2 |
|---|---|---|---|---|---|---|---|
Number of CPUs | Add | Yes (*1) | No | No | Yes (*2) | Yes | No |
Reduction | No | No | No | Yes (*2) | Yes | No | |
CPU Performance | Add | Yes | Yes | Yes | Yes (*2) | No | Yes |
Reduction | Yes | Yes | Yes | Yes (*2) | No | Yes | |
Memory Size | Add | Yes (*1) | No | Yes | Yes (*2) | Yes | No |
Reduction | No | No | Yes | Yes (*2) | Yes | No | |
OS Type | Modification | No | Yes | Yes | No | No | No |
*1: Can be changed if memory/CPU hot plug is enabled. The memory/CPU hot plug is enabled on the virtual L-Server created by Resource Orchestrator.
*2: The changed value will be enabled on the actual virtual machine after it is restarted.
[VMware] [Hyper-V] [Citrix Xen]
When CPU reserve, memory reserve, and initial memory capacity have been set for the L-Server, changing the CPU performance and memory size to values smaller than those values is not possible. To change these settings, use the command-line or VM management software. (*)
[VMware]
When the memory size is changed, the limit value of memory is also changed.
However, when the limit value of memory has been set to "Unlimited", only the memory size is changed.
When changing the memory limit setting, use the VM management software to do so. (*)
For details on the configuration method, refer to the manual of the VM management software.
When VMware FT has been configured on a virtual machine linked with a virtual L-Server, server redundancy settings cannot be modified.
Check whether the memory/CPU hot plug has been enabled from the VM management software if an existing VM guest is to be linked to a virtual L-Server.
If it is not enabled, enable the setting from the VM management software. Refer to the manual for the VM management software network device for information on how to enable the memory/CPU hot plug with the VM management software.
[Hyper-V]
When dynamic memory settings are changed from disabled to enabled, without specifying memory capacity or initial memory capacity for the L-Server, the values for the following items of the virtual machine will be same as the memory size.
Initial Memory Capacity (StartupRAM)
Maximum Memory
When using dynamic memory or memory weight, the VM host must be either of the following.
Microsoft(R) Windows Server(R) 2008 R2 SP1 or later
Microsoft(R) Windows Server(R) 2012
SCVMM should be one of the following, either of which can manage the VM hosts.
System Center Virtual Machine Manager 2008 R2 SP1 or later
System Center 2012 Virtual Machine Manager
When dynamic memory is enabled and memory weight is specified, modification of an L-Server will fail unless the above-mentioned VM host and SCVMM have been prepared.
The change of the maximum memory value of the dynamic memory setting when the power status is ON is not supported.
[KVM]
When memory_hotplug is configured as false in a VM specific information definition file, the maximum memory size of the created L-Server is configured with the same value as memory size.
The memory size of an active L-Server cannot be modified when memory_hotplug is "false".
[OVM for SPARC]
In order to assign CPU per core, even when the CPU performance is specified, it becomes the CPU performance of a physical server.
When virtual L-Server has stopped, memory size is cut down per 4 MB with VM product.
When virtual L-Server has started, memory size is rounded up per 256 MB with VM product.
Depending on the busy condition of the memory on a virtual server, it may not be set to the memory size as specification.
When the number of CPUs and memory size are changed, it is necessary to save composition information at a service processor. When you carry out autosave of the composition information with this product, please add a setup to the execution propriety definition file of composition information preservation.
When executing modification of CPU number or memory size, saving of vm guest(s) configuration is necessary.
This product carry out autosave of the configuration at the time of the modification of L-Server.
When you repeal the automatic save facility of the configuration in this product, please add a definition to the definition file which sets up the execution propriety of cofiguration preservation.
Refer to "C.8.1 Creating Definition Files" in the "Setup Guide CE".
Please assign many resources to a guest domain by specification change of virtual L-Server rather than the resources of all the non global zone constructed on the Solaris zone.
When resources fewer than the resources of all the non global zone constructed on the Solaris zone are assigned, the following phenomena may occur.
It becomes impossible to start non global zone
The performance of non global zone deteriorates
* Note: The modified value is reflected on the configuration of the L-Server by periodic queries made to the VM management software. For details on reflection of L-Server configuration by periodic queries, refer to "17.2 Modifying".
Note
Immediately after a snapshot is restored, there may be differences between the configuration of VM guests managed by L-Server and those managed by VM management software.
When you change CPU information, please specify VM host's CPU performance or VM host's number of CPUs registered in the VM pool.
When using the overcommit function, the value more than VM host's CPU performance can be specified.
The differences in VM guest configuration are reflected on the configuration of the L-Server by periodic queries made to the VM management software.
For details on reflection of L-Server configuration by periodic queries, refer to "17.2 Modifying".
When changing the values for server redundancy for an L-Server to which a virtual machine is already allocated, the virtual machine is not changed, only L-Server attributes are changed.
[Solaris Zones]
If the CPU's CAP value has not been set, both "Number of CPUs" and "CPU performance" must be changed when changing the CPU settings.
