HP Matrix Operating Environment 7.0 Release Notes

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.
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.
Reactivating and moving logical servers created on ESX 4x VM Hosts to ESX 3x VM Hosts
The ESX 4 virtual hardware version prevents virtual machine logical servers that were first activated
on an ESX 4x VM Host from being moved or reactivated on an ESX 3x VM Host.
ESX 4x supports virtual hardware version 4 and version 7 VM guests, but ESX 3x supports only
version 4 VM guests.
You can successfully move a virtual machine logical server first activated on ESX 3x to an ESX 4x
VM Host. If you attempt to move a logical server first activated on ESX 4.x to an ESX 3.x VM Host,
logical server management rejects the targets.
Different WWN and MAC range definitions for FCoE ports are not supported
If the WWNs and MAC addresses are from different ranges (such as VCEM-defined or user-defined)
when defining FCoE ports for the VC profile, the activation fails with the following error:
Workflow execution error: Failed to set SAN storage in profile
Suggested action
Be sure that the WWNs and MAC addresses are either both from a VCEM-defined range or both
from a user-defined range.
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.
Extended VLAN Multiple networks in the server profile have more than 28 Virtual Local Area
Networks (VLANs)
Logical server management 31