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 a Cloning Image"
When using a Windows cloning image
OS versions supporting the OS auto-configuration functions
Detaching Disks and Deleting L-Servers
Users are recommended to delete the data on disks, as the data of disk resources for virtual L-Servers is not deleted when detaching disks or deleting L-Servers.
For details on how to delete data on disks, refer to "14.5 Storage Resources" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".
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".
Chapter 6. Overcommitting with KVM
URL:http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/index.html |
Configuration for L-Server Live Migration
In RHEL-KVM environments, use SSH to perform live migration on virtual L-Servers.
It is necessary to perform the following configuration to enable live migration of an L-Server from the manager.
Configuration of /etc/hosts
Configuration when using SSH
Configure the settings, referring to the following section in the "Red Hat Enterprise Linux 6 Virtualization Administration Guide".
Chapter 4. KVM live migration
Chapter 5. Remote management of guests
URL:http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/index.html |
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 Command Reference in the following Red Hat manuals:
15.1. virsh command quick reference
URL: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/index.html |
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.