HP Matrix Operating Environment 7.3 Update 1 Release Notes

• Hyper-V VM linked clone disks must either specify the same storage volume name
not specify a name at all.
• Microsoft does not support VM Linked Clone using multiple data stores.
• A Copy Move operation for a VM using multiple data stores will result in all files
on the one chosen data store
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.
With this limitation, only MBR (master boot record) formatted iSCSI cluster disks are
supported.
40