Top
ServerView Resource Orchestrator Cloud Edition V3.1.1 Setup Guide
ServerView

C.6.9 Advisory Notes for RHEL-KVM Usage

This section explains advisory notes for RHEL-KVM.


VM Type View

In the ROR console, the VM type of RHEL-KVM VM hosts and VM guests is displayed as "RHEL-KVM".


Snapshot

When using RHEL-KVM, snapshots cannot be used.


Guest OS Automatic Configuration

When using RHEL-KVM, guest OS auto-configuration can be used for Linux or Windows.

Note

When the OS type is Windows, OS auto-configuration can be used for the OS versions described below.

"C.6.7 Collecting Cloning Images"

  • When using a Windows cloning image

    • OS versions supporting the OS auto-configuration functions


Detaching Disks and Deleting L-Servers

The data in the disk resources for virtual L-Servers cannot be deleted when detaching disks or deleting L-Servers, except when deleting the disk details for virtual L-Servers is enabled using the definition files.

Therefore, it is recommended to delete the data from the disk.

For details on how to delete data on disks, refer to "14.5 Storage Resources" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

For details on how to specify definition files, refer to "C.6.1 Creating Definition Files".


Configuration of Swap Area for the Host OS

As a guide, set the twice the amount of memory of a VM host for the swap area of a host OS.
When there is insufficient swap area for the host OS, the virtual L-Server may fail to start.
When it is difficult to secure sufficient swap area, it is also possible to configure the kernel parameters (/proc/sys/vm/overcommit_memory) to avoid failure of start operations due to a lack of virtual L-Server memory space.

For details, refer to the following section in the "Red Hat Enterprise Linux 6 Virtualization Administration Guide".

Prerequisites for L-Server Live Migration

Before performing live migration of a virtual L-Server, it is necessary to confirm the configuration of Resource Orchestrator in advance.

If the conditions are not satisfied, live migration will fail. Execute live migration after checking the configuration.

For details on prerequisites for L-Server live migration, refer to "E.5.2 Preparations for Servers" in the "Design Guide CE".


Configuration for L-Server Live Migration

In RHEL-KVM environments, use SSH to perform live migration on virtual L-Servers.

It is necessary to configure each involved host to enable live migration of an L-Server from the manager.

For details, refer to "E.5.2 Preparations for Servers" in the "Design Guide CE".

Note

When performing live migration using the virsh migrate command for KVM, specify both the --undefinesource and --persistent options.

If the command is executed without specifying these two options, the same VM guests may exist on both the destination and source VM hosts. In this state, the VM guests cannot be turned on using Resource Orchestrator. This occurs to prevent double VM guest startup operations in the state that multiple instances of the same VM guest exist on different VM hosts.

When turning on VM guests, the state where there are multiple instances of the same VM guest must be avoided by using the virsh command.
For details on the virsh command, refer to the following section in the "Virtualization Administration Guide".

  • Chapter 14. Managing guests with virsh

    URL: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/index.html

You can refer to the above section from the following URL for the manuals of Red Hat Enterprise Linux.

URL: http://www.redhat.com/docs/manuals/enterprise/RHEL-6-manual/index.html


Max. Number of Possible L-Servers View

The available space on resources and the space displayed for [the number of L-Servers that can be created] are calculated as follows:

Available Amount of CPUs and [Number of L-Servers that can be Created]

Total resource space - (Total of resources reserved for VM hosts + Total of resources used for L-Server)


Directory for collecting performance information

When resources are registered, the directories and files that are necessary for performance monitoring are created on the server where the resources are registered.
The directories and files are created in the following location. (Files with the same name in the same location are overwritten.)

 /{Home directory of the user ID specified when registering the resources}/dsa_temp_*

Do not delete the above directory until the resources themselves are deleted.
Performance information will not be collected if this directory is deleted. Restart the Manager if the directory is deleted accidentally.
The above directory is not automatically deleted when the resources are deleted. Delete it manually.