This section explains advisory notes for when using OVM for x86 2.2.
Operating Systems for which Parameters can be Set and the Prerequisites for Performing the Settings
Depending on the server virtualization software used, some restrictions may apply to the operating systems that parameters can be set for and the prerequisites for performing the settings.
For details, refer to the manual of server virtualization software.
VM Host Functions
VM Hosts that have no ability to provide virtual machine and virtual server functions cannot be registered in VM pools.
If those VM Hosts were registered, when a VM host specification used to create L-Servers is omitted, one of the VM host may be selected as the operational VM host.
In this case, even if the VM host is registered in the VM pool, when it is selected to create an L-Server, creation will fail.
Snapshot
When using OVM for x86 2.2, snapshots cannot be used.
Creating an L-Server
When creating L-Servers, set the destination VM host to the Preferred Server of a created VM guest.
L-Server Disk
Disks cannot be detached while they are powered ON.
L-Server Network (NIC)
One or more networks must be specified.
L-Server CPU Performance
For L-Server CPU performance, do not specify a value of less than 1GHz.
Moving an L-Server between Servers (Migration)
When performing migration with an L-Server powered on, after powering it off, the L-Server may be moved back to the previous server.
In this case, power off the L-Server before migration, and power it on again after moving it.
When the L-Server is an HVM (Hardware Virtualized Machine)
Installation of paravirtual drivers is required to connect data disks as SCSI disks.
If paravirtual drivers are not installed, the OS may fail to recognize the data disks.
SSL Access Method for VM Management Software
When starting VM management software from the management console, SSL-enabled URL or SSL-disabled URL can be specified as the destination. In Oracle VM Manager configurations, if SSL is enabled for access to Oracle VM Manager, the following definition file is required: Use the UTF-8 character code for definition files.
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data
ovmm.rcxprop
The definition file is entered in the following format.
Key = Value |
Specify the following items in a definition file. Other key specifications will be ignored.
Item | Key | Value | Remarks |
|---|---|---|---|
Enable/Disable SSL | SSL | "vmm_ip[:port][,vmm_ip[:port]...]" vmm_ip: IP address of SSL-enabled VM management software | If the port number is omitted, the default port number (4443) is set. |
An example definition file is indicated below.
# Oracle VM Manager |
Name and Number of Detected Virtual Storage Resources
Even if multiple storage repositories are connected to a VM host, only a single virtual storage resource is detected for each VM host.
The displayed name of virtual storage resources is the string of the VM host root repository, excluding the path name (/var/ovs/mount).
Example
D1567B83A58D41FEB28FB8897801C7ED
Virtual Storage Resource Free Space
When multiple storage repositories have been connected to the VM host, a storage repository that has the largest available space is displayed as the available space of the virtual storage resource.
Therefore, the space may not decrease in proportion to the virtual disk space created during L-Server creation.
Total Virtual Storage Resource Size
Not displayed.
Virtual Storage Resource Used Space
Not displayed.
Cloning Images Collected from L-Servers
Cloning images are stored in Oracle VM Manager, using the following template name:
"cloning_image_name[_index]@version_number" |
However, in the template editor window of Oracle VM Manager, "@" cannot be included in the template name. When using Oracle VM Manager to edit the template information collected using Resource Orchestrator, modify the template name so that it does not contain"@".
VM Host Status
Even when a VM host is running and the xend daemon is not running, "normal" is displayed as the status of the VM host. If L-Server operation fails when the VM host status is "normal", execute the following command from the VM host to check the status of the xend daemon. If the xend daemon is not running, start it.
Status Check for the xend Daemon
>service xend status <RETURN> |
Starting the xend Daemon
>service xend start <RETURN> |
When Managing Multiple Server Pools Using Oracle VM Manager
When creating an L-Server or attaching a disk, specify an image, VM host, or virtual storage that satisfies the following conditions:
Belongs to the same server pool as the image and VM host
The disk created is a virtual storage recognized by the VM host
Check the server pool to which the image and the VM host belong using Oracle VM Manager
Image
"Server Pool Name" in the "Virtual Machine Templates" list
VM Host
"Server Pool Name" in the "Servers" list
The name of a virtual storage recognized by the VM host is the string of the root storage repository, excluding the path name (/var/ovs/mount). To check the root storage repository, log in to the VM host, then execute the following command:
# ls -l /OVS <RETURN> |
Example
lrwxrwxrwx 1 root root 47 Apr 11 23:15 /OVS -> /var/ovs/mount/D1567B83A58D41FEB28FB8897801C7ED |
