HP Insight Dynamics 6.0 Release notes

User-defined portability group cannot have same name as default portability group
If you create a user-defined portability group with the same name as a default portability group
or another user-defined portability group in your environment, the user-defined group does not
appear in the list of available portability groups on the Create Logical Server Identity screen.
This prevents you from creating a logical server in the user-defined portability group.
If the resources are available on your system, the default portability groups are: each Virtual
Connect domain group, all ESX hypervisors, all Hyper-V hypervisors, and all Integrity VM
hypervisors.
Suggested action Ensure that the name of your user-defined portability group is different from
the names of any default portability groups or existing user-defined portability groups in your
environment. If you created a group with an identical name, modify the portability group to
change the name, then recreate the logical server. The new portability group should appear in
the drop-down menu.
Major issues
Unable to get detailed disk information on Microsoft Hyper-V VM host with a QLogic HBA
See “Unable to get detailed disk information on Microsoft Hyper-V VM host with a QLogic HBA”
(page 17) for information about downloading the QLogic HBA driver for Windows. Without
this driver, logical server management fails to operate correctly on Hyper-V cluster shared
volumes and cluster volumes with a QLogic driver.
LSA service may run out of memory on large scale systems
On large scale systems (on a 64-bit CMS), the HP Logical Server Automation service may run
out of memory and display an out of memory error in the /logs/hp_lsa_service.log file.
The error is similar to the following:
INFO | jvm 1 | 2010/03/08 19:15:14 |
java.lang.OutOfMemoryError: GC overhead limit exceeded
Suggested action Modify the configuration file to increase memory allocation, as follows.
1. Modify the configuration file in the default location at C:\Program Files\HP\
VirtualServer Environment\conf\hp_lsa_service.conf.
2. Increase the value of wrapper.java.maxmemory=1024. HP suggests a value of 2048.
Minor issues
Reactivating and moving logical servers created on ESX 4x VM Hosts to ESX 3x VM Hosts
The new 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.
Suggested action If your logical server was first activated on an ESX 4x VM host and specifies
SAN storage:
• For a SAN move or live move, only valid ESX 4x target hosts are displayed in the Available
Target Hosts table. ESX 3x targets are filtered out.
• Reactivating the logical server results in both ESX 3x and ESX 4x hosts displayed as valid
targets. Choose only an ESX 4x target. ESX 3x targets show the following soft error to remind
you to take care when moving the VM:
VM Host {target-host} may not support the virtual hardware version of VM Guest {vm-guest}.
Logical server management 31