Resource Pools on Citrix XenServer
Register all VM hosts in the resource pool on Citrix XenServer as managed servers on Resource Orchestrator. Register such VM hosts in all VM pools.
Templates Used as Virtual Image Resources
In Resource Orchestrator, use Citrix XenServer templates as virtual image resources. However, templates without disks cannot be used as virtual image resources, which is the same as the templates provided by default.
Install OSs and XenServerTools on templates.
Device 2 and 3 of a VM Guest
Devices 2 and 3 of VM guests are not used for disks as they are used for CD/DVD drives. When operating Citrix XenServer directly and connecting to device 2 or 3, they will be detected as unmanaged disks.
When importing the VM guest to a virtual L-Server, disk operations (addition or deletion) cannot be performed for the virtual L-Server.
Moreover, please do not use device 2 of the specified cloning image when creating virtual L-Server by using the customizing function of guest OS.
When creating the image (template) with the VM management product
Do not use single quotation (') for the image name.
Corresponding Terms Related to Memory in Resource Orchestrator and Citrix XenServer
The relationship of the terms related to memory in Resource Orchestrator and Citrix XenServer is as follows:
Virtual L-Server Parameters for Resource Orchestrator | VM Guest Parameters for Citrix XenServer |
|---|---|
Maximum memory size | Maximum static memory size (memory-static-max) |
Memory size | Maximum dynamic memory size (memory-dynamic-max) |
Memory Reservation Capacity | Minimum dynamic memory size (memory-dynamic-min) |
None | Minimum static memory size (memory-static-min) |
Memory Size when Creating an L-Server
When creating an L-Server in Resource Orchestrator, configure the same value as the Citrix XenServer VM guest for the maximum dynamic memory size. Configure 0 for the minimum static memory size. When changing the maximum dynamic memory size, or the minimum static memory size, operate Citrix XenServer directly, and modify the settings.
Maximum Number of CPUs when Creating an L-Server
In Resource Orchestrator, when creating an L-Server, configure the same values for the maximum number of CPUs as the already specified number of CPUs. When changing the maximum number of CPUs, operate Citrix XenServer directly, and modify the settings.
VM Guest Home Server Configurations
When using Citrix XenServer, while VM guests are powered off, they are not managed by a specific VM host. Therefore, in Resource Orchestrator the VM host used to manage powered off VM guests is determined based on the Home Server settings. When Home Server settings are not configured, if a VM guest is powered off, it will not be managed by Resource Orchestrator.
Then, the status of virtual L-Servers related to a VM guest will become unknown, and operations other than deletion cannot be performed. Power on the VM guest using Citrix XenServer, check that the virtual L-Server status returns to normal, and then perform the operation again.
High Availability Functions of Citrix XenServer
When using 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 Orchestrator will not 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 manual of server virtualization software.
VM Maintenance Mode
With Citrix XenServer, a VM host assigned as a pool master cannot be put into maintenance mode.
To put such a VM host into maintenance mode, the pool master role should first be assigned to a different VM host (within the same resource pool).
The Windows shared folder used by the customizing function of guest OS
Resource Orchestrator operates by the System account. Therefore, when create the Windows shared folder for servers other than the server that installs Resource Orchestrator. Can access the shared folder by the System account.
