HP Insight Dynamics 6.3 Release Notes

1. Modify the configuration file (shown in the default location) at C:\Program Files\HP\
Virtual Server Environment\conf\hp_lsa_service.conf.
2. Add the following line. (Change additional.2 to additional.3 if a line with
additional.2 already exists; change additional.2 to additional.4 if lines with
additional.2 and additional.3 already exist, and so on.)
wrapper.java.additional.2=-XX:PermSize=32m -XX:MaxPermSize=128m
3. Restart the HP Logical Server Automation service.
Minor issues
Performing operations on logical servers outside of Virtualization Manager may cause
incorrect information to be displayed
If you use tools other than Virtualization Manager to manage logical servers, modifications to the
underlying resources managed by logical server management are not immediately reflected in the
logical server.
For example, if you modify the power state of a managed resource outside of logical server
management, the power state of the logical server is displayed incorrectly until logical server
management resets its data.
Suggested action
Wait several minutes for the logical server to reset its data, or use Tools→Logical Servers→Refresh...
to manually refresh server resources.
Integrity VM activated on an HP-UX VM host incorrectly shows failure powering on logical
server
When activating an Integrity VM guest on an HP-UX VM host, the final step is powering on the
logical server. When this step is completed successfully, the “Powering on logical server” job status
incorrectly displays as Failed.
Suggested action
On the Virtualization Manager Report→Logical Server Job Status... screen, select the Failed job
and view its Job Details at the bottom of the screen. If the message is “The selected resource is
already powered on,” you can safely ignore the Failed job status.
Activating an Integrity VM virtual machine logical server with three or more vCPUs may
fail with entitlement error in VM host
If you attempt to activate an Integrity VM logical server with three or more vCPUs on an Integrity
VM host with 1596 Mhz processor speed or more, and the entitlement value used to create the
virtual machine on the VM host falls below the minimum 5% value, the activation may fail with the
error “Value x.x for entitlement_min is below minimum, setting to 5.0.” This error is displayed on
the VM host.
Suggested action
On the Integrity VM host, set the Integrity VM configuration variable GUESTMHZMIN to the nearest
integer value that is five percent of the host processor speed in cycles. The following commands
can be used to perform the GUESTMHZMIN variable setting on the Integrity VM host:
# typeset -i i j k
# i=$(hpvmstatus -sM | cut -d: -f3)
# j=i/20
# k=j*20
# if ((i>k)) ; then j=j+1 ; fi
# ch_rc -a -p GUESTMHZMIN=$j /etc/rc.config.d/hpvmconf
Logical Server Management 35