HP Matrix Operating Environment 7.1 Release Notes

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.
Microsoft Hyper-V virtual machine logical server boot disk is IDE and data disks are SCSI
When you create a Hyper-V virtual machine logical server, the boot disk (where Windows or Linux
is installed) is always created using an IDE controller. Data disks are created using a SCSI controller.
The IDE controller is required to allow the installation of the operating system using Deploy Tools
or using images without additional drivers. If a virtual machine is created outside of Matrix OE
visualization and imported as a logical server, it is possible that the boot disk controller type is
SCSI. In this case, you must install the SCSI controller driver to allow installation of the operating
system.
If a virtual machine is provisioned by Matrix OE infrastructure orchestration (using either a SCSI
or an IDE controller) and the logical server is imported, the virtual machine has an operating system
installed so the SCSI driver is not needed.
One Microsoft Hyper-V target displayed when activating a logical server created on a cluster disk
volume
A limitation in Microsoft Hyper-V R1 prevents the hypervisor from providing logical server
management with required information about a Hyper-V cluster. The result is that only one target
is shown when you attempt to activate a virtual machine logical server configured to be created
on a cluster disk volume. In Hyper-V R1, a logical server that is high availability (HA)-enabled can
be configured only on a cluster disk volume.
Logical server management 33