OS Startup Configuration while Starting Domains
When starting an OS while starting up an L-Server, specify "true" for the auto-boot? variable of the guest domain.
Display of CPU Performance and the Number of CPUs for L-Servers
The number of CPUs for L-Servers are calculated using the number of CPU threads configured for the domain, and is displayed per core.
The CPU performance of CPUs for L-Servers is calculated using the CPU performance and the number of CPU threads configured for the VM host.
The calculation formula is as below.
Number of CPUs = number of threads / number of threads per core (round-up any decimal values)
CPU performance = (number of threads * physical CPU performance) / (number of threads per core * number of CPUs)
Example
When creating an L-Server to which 2 cores (16 threads) are allocated on a VM host with a 2.8 GHz CPU, 1 core, and 8 threads
Number of CPUs = 16 / 8 = 2
CPU performance = (16 * 2.8) / (8 * 2) = 2.8 (GHz)
When creating an L-Server to which 12 threads are allocated on a VM host with a 2.8 GHz CPU, 1 core, and 8 threads
Number of CPUs = 12 / 8 = 1.5 ≑ 2
CPU performance = (12 * 2.8) / (8 * 2) = 2.1 (GHz)
CPU Capacity and Memory Capacity when Settings are Configured for Conversion Using Reservation Values
When the settings are configured to calculate using the reservation values, the same CPU capacity and memory capacity as used by a virtual machine are configured as the values for conversion using a maximum value.
Max. Number of Possible L-Servers View
For an OVM for SPARC VM host, the number for conversion is 0.
Display of Disk Information
The identifier information (ID number) is displayed for the device path.
L-Server Power Operations
When functions are not supported by OVM for SPARC, stopping and rebooting of L-Servers cannot be performed.
Depending on the statuses of virtual machines, either operate virtual machines directly, or perform a forced stop or a forced reboot.
When executing power control of VM guest in this product, binding / unbinding of resources is also executed.
When Starting VM guest
Binding of resources is executed
When stopping VM guest
Unbinding of resources is executed
When restarting VM guest
Binding/unbinding of resources is not executed
Overcommit
Do not register the VM host for OVM for SPARC in the VM pool used for overcommit.
When linking a virtual machine on the OVM for SPARC VM host with an L-Server in the VM pool used for overcommit, the overcommit attributes of the VM pool which the VM host is registered in are configured on the L-Server.
I/O Domain
In Resource Orchestrator, I/O domains are detected as VM guests.
An I/O domain may affect other guest domains when performing power operations.
It is recommended to perform management without linking an I/O domain with an L-Server.
This is to avoid performing incorrect operations due to confusion of the I/O domain with another guest domain, as a result of the I/O domain being managed as an L-Server or an L-Platform.
Number of VM Host CPUs
The number of cores that are recognized by the control domain is displayed for the number of CPUs of the VM host.
Adding disk to L-Server
When adding disk to L-Server, disk name of guest domain is named by following rule.
vdiskN |
N is disk number(0-63) which is specifyed when adding disk.
Migration Operations
The disk resource needs to be allocated to all the disks of L-Server when performing migration of L-Server. Moreover, the following conditions are fulfilled for the candidate of a movement place.
VM host that is sharing disk resource allocated in L-Server.
VM host with the same setup of the spare server to VM host.
When it moves to VM host that specified L-Server by one of the following methods, disks of L-Server after the movement is not in the disk resource with the relation, or disk information may not be updated.
Moving an L-Server between servers from the server tree on a ROR console.
Moving an L-Server between servers by the command which specified VM host.
For product specification of OVM for SPARC, It is not checked whether Disk allocated to guest domain is shared between source host and target host.
Therefore, please check following items to check sharing settings of disk.
All of disk allocated to guest domain is shared with target control domain
Disk services and volume name is same between source control domain and target control domain
When executing migration of guest domain with unshared disk, migration may be successful. But operation is not secured after migration.
After migration, it is necessary that executing command of "ldm add-spconfig" for saving of vm guest(s) configuration. Thereby, VM guest configuration is continuation even after a reboot.
In this product, VM guest(s) configuration is saved when detecting vm guest that is migrated. When repealing saving of vm guest(s) configuration in this product, please repealing definition of definition file indicated in "C.8.1 Creating Definition Files".
When VM host is down in migration, VM guest may carry out double starting. In order to prevent this phenomenon, we recommend to migrating with the state of preventing automatic boot after saving configuration with auto-boot setting to false.
In addition, for product specification of OVM for SPARC, operation for other guest domain under executing migration.
So, when executing operation for other VM guest / L-Server under executing migration, operation may be failed.
CPU Performance for L-Servers
With this product, the CPU value in performance of virtual L-Server is calculated based on VM host's CPU value in performance. Therefore, even when the number of CPUs of a virtual L-Server is the same, virtual L-Server's CPU value in performance may change with a VM Host's CPU value in performance.
Relation of guest domain to virtual L-Server
When Solaris zones are constructed on the guest domain and the guest domain is registered as a VM host, virtual L-Server linked with the guest domain cannot be taken into L-Platform.
Moreover, the administrator (supervisor or dual-role administrators) who manages the whole system needs to manage virtual L-Server which constructed the Solaris zone on the guest domain.
Since non global zone constructed on the Solaris zone is also influenced when the following operations are performed to virtual L-Server which constructed the Solaris zone on a guest domain, please operate it after checking the extent of the impact.
Power control of L-Server
Migration of a VM guest to a different VM host
Modifying L-Server specifications
Detaching a Disk
Virtual L-Server which constructs the Solaris zone on the guest domain recommends not containing in the scope of batch power operation of L-Servers.
When batch power operation of L-Servers is used on a guest domain in the environment which constructed the Solaris zone, please set up the priority of virtual L-Server which constructed the Solaris zone on the guest domain to become higher than the priority of virtual L-Server constructed on the Solaris zone. In addition, since it is carrying out using the function of virtual products, when power supply operation failed, please carry out power supply operation of the electric power control again to each L-Server.
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
Saving of VM guest(s) configuration
From this product, when the following operations are performed to VM guest / L-Server, it is necessary to save configuration at a service processor.
Power Control(ON/OFF/OFF(Forced)/Reboot/Reboot(Forced))
When using function of auto saving of vm guest configuration, VM guest configuration is maintain after reboot/force reboot is executed.
The reason used as the above-mentioned operation is that saving of vm guest(s) configuration is executed by change of a VM guest / L-Server's state.
Migration
Modification of CPU num an memory size
Adding / removing disk
When the following operations for guest domain are performed from control domain.
Creation / removing of guest domain
Binding / unbinding resources
Starting / stopping of guest domain
Modification of VCPU's num and memory size of guest domain
Adding / removing virtual disk to guest domain
Migration of guest domain
In this product, VM guest(s) configuration is saved after above-mentioned operation.
When saving vm guest(s) configuration manually, please set definition value to false in definition file indicated in "C.8.1 Creating Definition Files" and execute command of "ldm add-spconfig" in control domain.
When using function of auto saving of VM guest(s) configuration, be careful of the following points.
Since autosave of configuration is performed when change is detected in the renewal of a commuter's ticket of a server, after operation is completed before composition information is saved, a time lag produces it.
Moreover, also when change operation of a state and configuration to a guest domain is directly performed on VM host, in order for the renewal of a commuter's ticket of a server to detect change, autosave of the configuration is carried out.
However, since there will be a time lag by the time configuration is saved, when operating a guest domain directly on VM host, we repeal autosave of configuration and recommend you to save composition information manually.
When VM guest / L-Server which carried out migration are detected, configuration saving is performed by the moved material and VM host of a movement place.
In the autosave of configuration, this product overwrites the newest configuration at the configuration on a [current] state.
When factory-default is chosen as configuration for updating, this product do not save configuration (when factory-default is in [current] or the [next poweron] state).
With this product, since the newest configuration is saved temporarily, this product create the composition information on the name of config_tmp.
Therefore, please do not create the configuration named config_tmp.
Although configuration can be saved a maximum of eight pieces including factory-default in FUJITSU M10, in order to create the configuration of config_tmp temporarily, please create the configuration only to seven pieces including factory-default with this product.
A single quote (') cannot be used for a configuration name. This product do not save configuration, when a single quote (') is contained in the name of the composition information used as the candidate for updating.
For specification of OVM for SPARC, this product cannot save configuration during execution of migration. Therefore, when migration is performed continuously, configuration is not saved until the migration performed at the end is completed.
If operation to preservation and VM host of configuration is performed simultaneously, preservation of configuration may go wrong. In that case, since the message of the message number 41127 is outputted to an event log, please resave configuration.
For detail on how to restore configuration, refer to "3.1.1 411XX Series" in the "Messages".
CPU Dynamic Resource Management
When modifying CPU value of virtual L-Sever in this product, CPUs is allocated per core.
So, the function of CPU Dynamic Resource Management becomes impossible to use (*).
When using CPU Dynamic Resource Management, it is necessary to set up CPU per thread in control domain.
If the calculation of usage charges is enabled, the usage charge for CPUs will be calculated based on the number of CPUs changed dynamically by CPU Dynamic Resource Management.
*Note: The function of CPU Dynamic Resource Management makes the number of CPUs change dynamically per thread. When CPUs is allocated per core, it is impossible to change number of CPUs per thread. So, the function of CPU Dynamic Resource Management becomes impossible to use. For details, refer to manual of OVM for SPARC.
Sharing disks
The domain and virtual L-Server after the 2nd set that is sharing the disk cannot be linked at the following compositions.
Disks other than the system disk shared between two or more domains are registered to the virtual disk service.
