Select the VM type for the L-Server to be created.
It is not necessary to specify this when deploying an image, because the VM type of the image is used.
Enter the number of server CPUs to allocate to the L-Server. Enter an integer between 1 and 8.
[Oracle VM]
The range that can be entered differs depending on the OS type of VM guests.
Windows
An integer between 1 and 8
Linux
An integer between 1 and 32
[Hyper-V]
Enter an integer between 1 and 4.
[KVM]
The number of CPUs supported by the KVM in use is the upper limit.
The upper limit value is 64 for RHEL6.1.
Enter the server CPU speed to allocate to the L-Server. Enter a number with up to one decimal place, in units of gigahertz. A number between 0.1 and 8 can be specified.
The value entered here is used to determine the CPU ratio to allocate to the L-Server out of the clock speed of the physical CPU of the VM host. If VM hosts with different types of physical CPUs are registered in the VM pool, the actual processing performance may differ according to the allocated VM host.
[VMware]
For VM guests on VMware, set the CPU performance for the limit value and 0 for the reserved value.
Information
For details on limit values and reserved values of CPUs, refer to the "vSphere Resource Management Guide" of VMware.
Refer to the relevant version of document, referring to the following URL:
URL: http://www.vmware.com/support/pubs/vs_pubs.html |
[Hyper-V]
CPU performance is realized through the resource settings of VM guests and VM hosts.
When the SCVMM management console or a Hyper-V manager is used to change the resource reservation of a VM guest or VM host, there is a chance that the creation or starting of VM guests may fail, or the expected performance may not be obtained.
Please do not change VM guest and VM host resource reservations when L-Servers have been created.
[KVM]
CPU Capping functions will be ignored, since the function is not supported by RHEL6.1.
[Oracle VM]
Specify the size within the range of 0.3 to the_resource_size_of_the_hardware_on_which_the_VM_hosts_operate.
Enter the memory capacity to allocate to the L-Server. Enter a number with up to one decimal place, in units of gigabytes. A number between 0.1 and 255 can be specified.
[VMware]
For VM guests on VMware, set the memory size for the limit and reserved values.
Information
For details on limit values and reserved values of memory, refer to the "vSphere Resource Management Guide" of VMware.
Refer to the relevant version of document, referring to the following URL:
URL: http://www.vmware.com/support/pubs/vs_pubs.html |
[Hyper-V]
For VM guests with dynamic memory disabled, set the memory size for the virtual machine memory.
For VM guests with dynamic memory enabled, set the memory size to the maximum memory.
The enabled/disabled state of dynamic memory is determined according to the value specified in the VM specific information definition file. For details on VM specific information definition files, refer to "C.1 Definition Files Commonly Shared when Creating Virtual L-Servers" and "Chapter 8 Creating Definition Files" in the "Setup Guide CE".
[KVM]
The maximum size of available memory can be specified.
[Oracle VM]
The size of resources of hardware where VM hosts operate can be specified.
Specify the type of operating system to allocate to the L-Server. It is not necessary to specify this when deploying an image, because the VM type of the image is used. The OS type can be changed after the OS installation.
[Hyper-V]
If an unsupported OS type is specified, installation may fail or the OS of the VM guest may not operate correctly.
Additionally, if an incorrect OS type is specified, there is a chance that image collection or L-Server creation for a specified image may fail, and a guest OS may start but hang while awaiting entry. This occurs because Microsoft's Sysprep cannot be processed correctly during personalization processing.
The OS types displayed in the list are the guest OS's which can be specified on the SCVMM management console.
Resource Orchestrator displays all guest OS's in the list in order not to limit user selection, however this does not mean that all guest OS's are supported by SCVMM.
Hyper-V does not support some server type settings such as number of CPUs depending on the OS type. When an incorrect OS type and server type are selected, operation is not guaranteed.
Additionally, even when a service pack is not listed in the OS type list, it may be necessary to install the service pack.
When a guest OS that Hyper-V supports is specified for the OS type, a converged network adapter will be added to VM.
When a different OS has been selected, an emulated network adapter will be added.
For details on the guest OS's supported by SCVMM, refer to the Help of SCVMM.
For details on the guest OS's supported by Hyper-V, refer to the following Microsoft web site.
Microsoft download web site
URL: http://www.microsoft.com/windowsserver2008/en/us/hyperv-supported-guest-os.aspx |
[KVM]
Linux, Windows, and Linux (SELinux) can be selected.
A personalized guest OS can only be selected for Linux.
When creating a new guest VM, the information will be displayed. When information of a newly created VM guest is lost during backup and restoration, "unknown" may be displayed.
[Oracle VM]
The OS type cannot be changed.
Individually specify the resources to allocate to the L-Server.
Clicking <Select> displays the [Select a VM host] dialog.
Specify a VM host or VM pool. If you do not specify a VM host or VM pool, a VM host that can create an L-Server is automatically searched for from the VM pool. If there are multiple VM pools, the VM host is searched for, beginning with the VM pool with the highest priority.
Specify whether add the CPU and memory of the VM guests allocated to the L-Server to the total of the VM pool, when the power of the L-Server is OFF.
When the [Automatic (when powered off)] checkbox is checked, the CPU and memory of VM guests allocated to L-Servers cannot be calculated as the total usage amount of VM pools.
Decide whether the physical location of servers to be allocated to the L-Server can be changed.
Fixed
Starts the L-Server on the same VM host that operated last time. Move the L-Server between servers to start it on a separate VM host.
Relocate at startup
Automatically selects the optimal VM host when the L-Server is started. When [VM host] is specified, select VM hosts from the range.
Note
When RHEL-Xen is specified for the VM type, select [Fixed].
Specify the server redundancy to allocate to the L-Server. To enable redundancy, select the [HA] checkbox.
[VMware] [Oracle VM]
If the [HA] checkbox is selected
The HA function is located on an enabled VM host.
When there is no VM host for which the HA function has been enabled, the L-Server for which a configuration definition has already been created cannot be started.
If the [HA] checkbox is not selected
The HA function will be preferentially located on a disabled VM host.
However, the HA function will place a VM guest on an enabled VM host in the following cases:
The HA function is not located on a disabled VM host
There is no available CPU or memory
Information
If the HA function is located on an enabled VM host, the HA function of the server virtualization software will be enabled.
When a problem occurs on the physical server that the VM host is operating on, the virtual machine can be recovered by restarting it on a VM host that is operating normally.
[Hyper-V]
In Hyper-V environments this setting is ignored, and VM guests are always located on clustered VM hosts.
[KVM]
In RHEL-KVM environments this setting is ignored, and set as "none", since there are no server recovery functions on Hypervisor.
Note
When KVM or RHEL-Xen is selected for the VM type, because server recovery cannot be enabled, do not select the [HA] checkbox.
Configure alive monitoring as enabled or disabled.
The following operations are performed if you select the [HA] checkbox.
[Xen] [KVM] [Oracle VM]
The alive monitoring configuration is not displayed.
Enter when not operating the virtual machine on the same VM host as another virtual machine.
For example, when performing load-balanced work using multiple virtual machines, you can set exclusive operation to ensure that the work continues in a degenerate state because only one virtual machine stops when a physical server fails. Specify an L-Server name or resource folder name that you have operating privileges for.
The virtual machine of the specified L-Server is allocated to different physical servers.
If you specify a resource folder name, one's own L-Server can be included in the resource folder. In the following cases, the L-Server may be allocated to the same physical server, regardless of whether exclusive operation is specified:
If no other VM hosts that meet the conditions for exclusive operation can be found, such as when there are no VM hosts in the VM pool that have enough free space to install an L-Server
If the HA function or automatic re-installation function (examples: VMware HA or VMware DRS) of the VM product is enabled
Note
When an operation that puts a resource that has been configured for exclusive operation outside the access scope of users, the name of the resource will only be displayed on the screen for changing specifications or definitions.
With L-Servers, when performing batch power operations in a resource folder or a tenant folder, configure the priority for the L-Server.
Set a number between 1 and 256. Smaller values indicate higher priority. If omitted, "128" is set.
When not performing batch power operations, check the [Exclude from batch power operations] checkbox.
