HP Matrix Operating Environment 7.0 Release Notes

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.
Multiple datastores are not supported
All storage volumes for a virtual machine logical server must be part of the same datastore. (To
import a virtual machine, the virtual machine must be using a single datastore.) File volumes are
created on the same disk as the virtual machine's configuration file.
Virtual machine datastore size and configuration filename limits
When creating a virtual machine logical server (ESX, Hyper-V, or Integrity VM), the maximum
datastore size that you can specify is 2048 TB (2097151 GB). Additionally, the maximum number
of allowed characters for a virtual machine configuration filename is 255. If you specify a size
larger than the maximum, a warning message is logged and the entry is ignored.
VM technologies have individual configuration limits that may limit the VM disk size.
Logical server management supports virtual machines created only on the first partition of a physical
disk
If a physical disk has multiple partitions (volumes with the same disk identifier), only the first volume
is recognized and supported by logical server management. For example, if a disk has volumes
C:, D:, and E:, you can create and import a virtual machine logical server created only on the C:
volume.
Importing a Microsoft Hyper-V virtual machine with configuration file in the default location is not
supported
A Hyper-V virtual machine whose configuration file is in the default location on the hard disk in
\ProgramData\Microsoft\Windows\Hyper-V is not supported by logical server management.
You cannot import a virtual machine guest as a logical server if the virtual machine's configuration
file is in this location. There is a limitation in Microsoft Hyper-V that allows Insight Control virtual
machine management to re-register the virtual machine if the configuration file is created in this
directory. To prevent issues with reactivation, logical server management checks the path and
rejects any virtual machines with a configuration file in the default location.
Hyper-V cluster shared volumes created with GPT disk partitioning system have limited support
Hyper-V VM Hosts configured with cluster shared volume (CSV) storage with a GUID partition table
(GPT) disk partitioning system are supported with the following conditions:
• All hosts (cluster nodes) must contain the same LUN identifiers for the LUN
• LUN identifiers must be unique in the host if the LUNs are presented from different storage
arrays
iSCSI disk requirements for use with Microsoft Hyper-V virtual machine logical servers
To enable selection of a specific iSCSI datastore as the storage definition during logical server
creation or modification, iSCSI disks associated with Microsoft Hyper-V hosts must be a cluster
disk or a shared cluster volume, online, and contain a volume created with a drive letter.
30 Issues and suggested actions