HP Matrix Operating Environment 7.1 Release Notes

of five PCI Controller devices (two SCSI controllers and three NICs) attached to a virtual machine.
ESX hardware version 7 allows four SCSI controllers and ten NICs.
Suggested action
Use an ESX native template with a hardware version of 7, or reduce the number of NICs in the
infrastructure orchestration template to three or fewer.
Physical disks with multiple partitions are unsupported unless all but the first partition are excluded
If your environment contains a physical disk with multiple partitions (volumes with the same disk
identifier) and you want to provision virtual machines on that disk, exclude all partitions except
the first partition on the disk. A virtual machine created on a physical disk with two or more partitions
without this exclusion is unsupported, and the service could fail to deploy with the error “Import
failed for logical-server. VM host datastore not found.”
Suggested action
Exclude all partitions except the first partition on the disk in the “VOLUMES TO EXCLUDE” section
of the hpio.properties file.
For example, if there are three volumes (C:, D:, and E:) on a physical disk, exclude the D: and E:
volumes to provision a logical server on the virtual machine created on the C: volume of the physical
disk.
Cluster shared volume does not appear after Microsoft Hyper-V VM provisioning with high availability
enabled
If you use infrastructure orchestration to create and deploy a virtual provisioning template on a
Microsoft Hyper-V VM host with the High Availability (HA) option enabled, and then view the
virtual machine in the Failover Cluster Manager on the Hyper-V host, the cluster shared volume
(CSV) is not displayed in the provisioned VM information.
However, if you manually deploy the virtual machine using the Microsoft Hyper-V Manager on the
Hyper-V VM host, the Failover Cluster Manager correctly displays the disk resource and the virtual
machine resources created.
Suggested action
No action is needed; the highly available virtual machine disk was created correctly on the CSV.
Cluster shared volume is not correctly recognized unless all VM hosts in the Hyper-V cluster are
registered in Insight Control virtual machine management
When only one VM host in a Hyper-V cluster is managed by Insight Control virtual machine
management, the following areas are impacted:
• Matrix infrastructure orchestration — IO treats a cluster shared volume (CSV) as a cluster disk,
and allocates only one VM to the cluster disk. When trying to deploy multiple VMs, the following
error is displayed:
Provisioning request has paused. Modify storage volumes on VM Hosts
to satisfy the logical disk requirements. An IO Administrator has
been notified.
• Matrix OE logical server management — Only the CSV and cluster disk are available on the
VM host if the registered VM host ID is the VM host owner. If it is not the owner, the VM host
is placed on the Rejected List and an error indicates that the storage is not available on the
VM host.
Suggested action
Add all VM hosts that are in the Hyper-V cluster to Matrix infrastructure orchestration, registering
them with Insight Control virtual machine management as VM hosts. The VM hosts can be left in
the Unassigned pool, or they can be used as regular VM hosts within IO.
22 Issues and suggested actions