HP Insight Dynamics 6.2 Release Notes

to protect the VM guests from inadvertent operations, a logical server that is a physical server
running as a VM host has the following restrictions:
• Deactivate, move, power off, and delete operations on the VM host logical server are not
supported while there are guest VM logical servers residing on the VM host logical server.
You must move the guest VM logical servers off of the VM host logical server before performing
any of these operations on the VM host logical server.
• Deactivate, move, power off, and delete operations on the VM host logical server are not
supported while there are running jobs on the VM host logical server that could result in
creating or leaving a VM guest logical server on the VM host logical server. If this occurs,
re-identify the source and target server blades and VM host. If the orphan VM guest logical
server remains after re-identification, unmanage the logical server and, if necessary, remove
its underlying resources.
Managing a CMS as a logical server is not supported
HP strongly recommends that systems running Central Management Server (CMS) software not be
managed as logical servers. This includes the Insight Dynamics CMS, as well as any other CMS
managed by the Insight Dynamics CMS.
Note that logical server management does not prevent you from managing a CMS as a logical
server. For example, Insight Dynamics will allow any managed node, including the CMS, to be
selected for moving or other logical server operations; doing so may result in unpredictable results.
Hyper-V cluster shared volume created with GPT disk partitioning system is not supported
If you attempt to move a Hyper-V virtual machine logical server to a Hyper-V VM host that is
configured with cluster shared volume (CSV) storage with a GUID partition table (GPT) disk
partitioning system, the target host is rejected with the error:
VM Host was filtered out because the data storage of logical server
logical-server-name does not match the available storage on VM Host hyper-v-vm-host-name.
Suggested action
Recreate the CSV using master boot record (MBR) storage. GPT disks are typically used only if you
need volumes that exceed 2TB.
Moving a logical server from a Microsoft Hyper-V R2 host to a Hyper-V R1 host is not supported
A limitation from Microsoft prevents you from moving or reactivating a virtual machine logical
server from a Microsoft Hyper-V R2 host to a Hyper-V R1 host. An error message is displayed if
you attempt the operation.
You can move or reactivate a virtual machine logical server from a Hyper-V R1 host to a Hyper-V
R2 host.
NOTE: The Hyper-V host version is shown in the Platform column in the Available Target Hosts
table on the activate or move logical server target screen. The host is a Hyper-V R1 host if the host
version begins with 6.0 (for example, 6.0.6001 or 6.0.6002 in Windows 2008 Server – Hyper-V
SP1 or Windows 2008 Server – Hyper-V SP2). The host is a Hyper-V R2 host if the host version
begins 6.1 (for example, 6.1.7077 in Windows Server 2008 R2).
Suggested action
Be certain that you want to move or reactivate the logical server from Microsoft Hyper-V R1 to R2
before you complete the operation. After the operation completes, you cannot move or reactivate
the logical server back to Hyper-V R1.
Logical Server Management 29