HP Matrix Operating Environment 7.3 Update 1 Release Notes

Major Issues
High Availability Hyper-V VMs with RDM/pass-through disks violating various
constraints from Hyper-V result in errors
Service provisioning or logical server VM creation or reactivation fails with a job
message similar to the following:
The operation has failed. (The start function on virtual machine
vsels_name [VM info and XML path] failed. )
Matrix OE supports High Availability (HA) Hyper-V VMs with RDM/pass-through disks,
with various constraints from Hyper-V. Violating these constraints can result in failures.
Only HA VMs can have pass-through cluster disks attached. In addition, HA VMs can
only have such disks attached. The cluster disks must be in maintenance mode prior to
provisioning and activation.
Suggested action
If the error occurs when provisioning an HA VM using one or more pass-through cluster
disks:
1. Using Microsoft Failover Cluster Manager select More Actions→Turn On
Maintenance Mode for the cluster disks.
2. Repeat the provisioning operation such as submitting a service create or creating
a logical server.
3. Using Microsoft Failover Cluster Manager select More Actions →Turn Off
Maintenance Mode once the VM is provisioned and the OS is deployed.
If the error occurs when reactivating the HP VM using one or more pass-through cluster
disks:
1. Using Microsoft Failover Cluster Manager select More Actions→Turn On
Maintenance Mode.
2. Repeat the provisioning operation.
3. Using Microsoft Failover Cluster Manager select More Actions →Turn Off
Maintenance Mode once the VM is reactivated.
Linked clone provisioning of a VM template containing shared disks does not
succeed
During ESX server provisioning, errors similar to the following are displayed:
Error taking a snapshot on virtual Logical Server nnnnn. Virtual
machine is configured to use a device that prevents the snapshot
operation: Device is a SCSI controller engaged in bus-sharing.
The VM template created from an IO template specifies linked clone servers and deploys
software as an embedded shared disk. This combination is not supported.
Suggested action 1
Edit the template in IO designer and uncheck Deploy as Linked Servers.
Suggested action 2
Select other software to deploy without an embedded shared disk, and then retry the
Create Service operation.
Provisioning of Matrix OE service fails in customization
Provisioning of Matrix OE services can fail in customization if Insight Control server
provisioning or SA deployment is attempting to join the server to an Active Directory
during the OS installation. Doing so will cause the Matrix OE post-install customization
28