A.2 Configuration Requirements

This section describes the settings required to properly configure each different virtualization product for use with Resource Coordinator VE.

Configuration Requirements for Each Server Virtualization Product

The required configuration differs with each server virtualization product. For details on the configuration of each virtualization product, refer to the manual of each product.

[VMware]
Installation of VMware Tools is required to properly display the hostnames of guest OS's and enable their remote shutdown via the power control functions of Resource Coordinator VE.
Install VMware Tools after installing an operating system in a VM guest.

[Hyper-V]

Use the following procedure to enable remote management.
1. Enable remote control in WMI settings.
  1. In each VM host, access the Control Panel and open the [Administrative Tools]-[Computer Management].
    The [Computer Management] dialog is displayed.
    From the [Computer Management] dialog, open [Services and Applications], right-click on [WMI Control] and select [Properties].
    The [WMI Control Properties] dialog is displayed.
  2. In the [WMI Control Properties] dialog, open the [Security] tab, select [Root]-[virtualization] and click <Security>.
    The [Security for ROOT\virtualization ] dialog is displayed.
  3. In the [Security for ROOT\virtualization] dialog, select the VM host's user name, select the "Allow" checkbox for "Remote Enable" and click <OK>.
  The remote enable of WMI is set.
2. Configure the Windows firewall to enable remote WMI management.
  1. In each VM host, run the "GPedit.msc" command.
    The [Local Group Policy Editor] dialog is displayed.
  2. In the [Local Group Policy Editor] dialog, open the following folder.
    [Computer Configuration]-[Administrative Templates]-[Network]-[Network Connections]-[Windows Firewall]
  3. If the VM host is a member of a domain, double-click [Domain Profile]; otherwise double-click [Standard Profile].
    Either one of the [Domain Profile] or [Standard Profile] screen is displayed.
  4. In the displayed screen, right-click "Windows Firewall: Allow inbound remote administration exception" and select [Properties].
    The [Windows Firewall: Allow inbound remote administration exception] dialog is displayed.
  5. Select "Enabled" and click <OK>.
3. Configure DCOM.
  1. In each VM host, run the "Dcomcnfg.exe" command.
  2. In the [Component Services] dialog, expand [Component Services]-[Computers], right-click [My Computer] and select [Properties].
    The [My Computer Properties] dialog is displayed.
  3. In the [My Computer Properties] dialog, open the [COM Security] tab.
  4. Click <Edit Limits> under "Launch and Activation Permissions".
    The [Launch and Activation Permission] dialog is displayed.
  5. In the [Launch and Activation Permission] dialog, select the VM host's user name under "Groups or user names:", and select the "Allow" checkbox for "Remote Activation" and click <OK>.
  6. Click <Edit Limits> under "Access Permissions".
    The [Access Permission] dialog is displayed.
  7. In the [Access Permission] dialog, select " ANONYMOUS LOGON" under " Groups or user names:", select the " Allow" checkbox for " Remote Access" and click <OK>.
Perform configuration so that the networks of VM hosts and VM guests are not shared.
1. Prepare more that two physical NICs.
  The physical NIC that the VM host uses for the admin LAN and communication with external servers should only be used for physical servers. Please do not configure it for virtual networks.
2. Create a virtual network for the VM host to use for communication.
  - For Hyper-V 2
    Open the Hyper-V Manager, then [Virtual Network Manager] to create the virtual network. Clear the "Allow management operating system to share this network adapter" checkbox. (By default, the checkbox is unselected)
  - For Hyper-V 1.0
    On each VM host, access the Control Panel and open the [Network Connections]. Disable all external virtual network connections for the VM host which are displayed as "Local Area Connection".
Installation of VMware Tools is required to properly display the host names of guest OS's and enable their remote shutdown via the power control functions of Resource Coordinator VE.
Install OS's on VM guests and then install the integration service on those OS's.

[Xen]
With Citrix XenServer, perform settings to enable remote shutdown of VM guests via the power control functions of Resource Coordinator VE.
Install XenServer Tools after installing an operating system in a VM guest.

[Solaris Containers]
Set SSH access permission for accounts with administrator privileges, and enable password authentication.

Note

[Hyper-V]
If a VM host belongs to a domain, make sure that its host name can be properly resolved by the admin server (from the VM host IP address).
If host name resolution fails, perform the necessary DNS (or hosts file) settings to enable host name resolution.

[Xen]

Make sure that each VM host is able to resolve the host name of the admin server from its IP address (on the admin LAN).
If host name resolution fails, perform the necessary DNS (or hosts file) settings to enable host name resolution.
When using Citrix XenServer with a resource pool, confirm that a home server is set for each VM guest.
If no Home server is set, Resource Coordinator VE is only able to recognize active VM guests. For details, refer to "A.3 Functional Differences between Products".
When using Citrix Essentials for XenServer with a resource pool, high-availability should be enabled for that resource pool.
If high-availability is not enabled, and the pool master become unreachable, Resource Coordinator VE won't be able to control or get information from the VM hosts and VM guests placed in that resource pool. If VM guest statuses become out-of-date, or operations on VM hosts or VM guests fail, check the status of the pool master. If the pool master is not reachable, resolve any communication problem that may prevent the manager from communicating with it (if necessary, change the pool master to another VM host).
For details, refer to the server virtualization software manual.

Configuration Requirements for System Center Virtual Machine Manager

The following settings are required when using System Center Virtual Machine Manager (hereafter SCVMM) as VM management software.

Install Windows PowerShell.
Install PowerShell 2.0 or later on the admin server if it was not installed yet.
Configure Windows Remote Management settings.
- VM management software
  Remote administration rights should be granted on the server where SCVMM is installed.
  1. Log in to the SCVMM server as the administrator.
  2. Run the following command from the command prompt.
    >winrm quickconfig <RETURN>
  3. Reply "y" to the confirmation that follows execution of the above command.
- Admin server
  If the admin server and the SCVMM server are in different domains, add the SCVMM server to the list of hosts trusted by the admin server to enable authentication.
  1. Log on to the admin server as the administrator.
  2. Run the following command from the command prompt.
    >winrm set winrm/config/client @{TrustedHosts="SCVMM_server_ip_address"} <RETURN>

Configuration Requirements for VM Guest Switchovers

Depending on the virtualization product being used, the following settings should be made to enable switchover of a newly created VM guest.

[VMware]
The VM guest's UUID must be changed.
Perform the following settings before switchover of a VM guest.

From the VM management client, add the following parameter to the guest's virtual machine configuration.

Name         Value
uuid.action  keep

For details on how to add parameters to a virtual machine configuration, refer to the help section of the VM management client.

Without this setting, a confirmation dialog is shown each time a virtual machine is started after being moved to a different VM host. Enabling this setting will prevent such confirmation dialogs from being shown, and the virtual machine will be set to always keep its UUID when moved between different servers.

[Hyper-V]
No specific configuration is required.

[Xen]
No specific configuration is required.

Starting VM Management Software Clients

[VMware]
VMware Infrastructure Client or VMware vSphere Client should be installed on the Resource Coordinator VE admin client.

[Hyper-V]
Hyper-V Manager or a VMM Administrator Console (*1) should be installed on the Resource Coordinator VE admin client.

*1:When System Center Virtual Machine Manager (SCVMM) is registered, this VMM Administrator Console is used to control the VM hosts managed by SCVMM.

[Xen]
When using Citrix XenServer, XenCenter should be installed on the Resource Coordinator VE admin client.