HP Matrix Operating Environment 7.3 Release Notes

Patch required for proper management of Microsoft Windows Server 2008 with
Hyper-V systems
A patch from Microsoft is required for managing Microsoft Windows Server 2008 with Hyper-V
systems. Patches are installed on the Hyper-V hosts, and after you do so, you must install or update
Hyper-V Integration Services from the updated host to each VM guest. Do this as a precaution
because not all patches affect Integration Services on the guests.
Microsoft Windows Server 2008 SP2 with Hyper-V requires you to install the following patch that
fixes the hang in host servers with many simultaneous virtual machine operations. The patch is
located at http://support.microsoft.com/kb/980081.
See the Managing Microsoft Windows Server 2008 Hyper-V with HP Insight Software technology
brief for more information about other patches that might be required for later editions of Microsoft
Windows Server 2008 (R2):
Matrix OE Information Library
Patch required for HP Integrity VM version 6.1 to deploy IO services containing
shared guests
Patch PHSS_43030 is required to deploy Matrix infrastructure orchestration services containing
HP Integrity VM version 6.1 shared guests. Without this patch, Matrix infrastructure orchestration
virtual provisioning fails with an insufficient memory error.
Download from http://www.hp.com/go/hpsc. Log on with an HP Passport. From the Download
options list, select Patch management and enter the patch number in the search box. Click
Search.
Install Utilization Provider version A.01.08.07.00 for HP-UX 1203 Integrity VM host
Utilization Provider version A.01.08.07.00 is required for systems that have HP-UX vPars and
Integrity VM 6.1. Download this version from the HP Software Depot. Without this version, Utilization
Provider displays excessive high system memory for HP-UX 1203 Integrity VM hosts even though
there are no VMs hosted.
VM kernel port name used for management traffic must be “Management Network
In VMware ESXi, the default name of the Virtual Machine (VM) kernel port used for management
traffic is “Management Network. Do not modify this name in the vCenter client user interface. If
this name is modified, the following will result.
When trying to activate a logical server, the ESXi hosts appear as Rejected Target hosts with
an error that the hosts are not part of vCenter, or that virtual machine management is unable
to get vCenter information for the VM host.
The association between the host and vCenter does not appear in Systems Insight Manager.
Suggested action
Modify the Network Label of the VMKernel port used for management traffic to “Management
Network by performing the following steps.
1. Log into the vCenter using the vCenter client.
2. Select the Hosts and Clusters view from the menu ViewInventory.
3. Select the ESXi server from the tree displayed in the left pane.
4. Select the Configuration tab from the right pane.
5. From the Hardware section, select Networking.
6. Click Properties for the Virtual Switch where the VMKernel port used for management traffic
is located. If there are multiple VMKernel ports located on multiple virtual switches and
configured for management traffic, select the switch that has the VMKernel port that has the
Installation 15