HP Matrix Operating Environment 7.3 Update 1 Release Notes

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.
Suggested action
Upgrade to Hyper-V R2. In R2, Microsoft corrected the problem so that the activation
of a virtual machine logical server configured to be created on a cluster disk or a cluster
shared volume lists all Hyper-V hosts in the cluster on the target screen.
High Availability Hyper-V virtual machine with RDM disk can be activated only on cluster
disk owner
When an HA Hyper-V logical server with a SAN-based storage pool entry (RDM disk)
is activated, only the RDM disk host owner displays as a target on which to activate
the logical server. It is not possible to enable HA for a VM with an RDM disk if the
Hyper-V host that is hosting the VM is not the owner of the RDM disk.
Some Virtual Connect profile capabilities are not supported by logical server management
Importing a server with Virtual Connect that implements the following features is not
supported by Matrix OE logical server management. If the Virtual Connect profile is
using these features, the error “The Server Profile cannot be imported because it contains
the following capabilities unsupported by Logical Servers:” is displayed.
EXTENDEDFC Server profile has two or more FC Connections using the same
connection bay (with the same connectionBay attribute value),
which identifies a server profile created for an HP Integrity BL860c)
EXTENDEDFCOE Server profile has more than one Fibre Channel over Ethernet
(FCoE) connection associated with the same interconnect bay (IO
bay)
ISCSI Server profile has at least one iSCSI connection
NAG Server profile has an associated Network Access Group
LUNs are not detected after activating a logical server using logical server management
on an HP Integrity Virtual Machine host
A logical server, when activated directly on an HP Integrity Virtual Machine host using
LSM, fails to detect the LUNs assigned to it at the virtual machine EFI prompt. Due to
this limitation, the logical server will not boot up the operating system automatically
even if it is assigned with a LUN that is pre-provisioned with an operating system.
41