HP Matrix Operating Environment 7.3 Update 1 Release Notes

Suggested action 1

To correct the GC overhead limit and/or Java heap space errors, modify the

configuration file to increase memory allocation:

1. Modify the configuration file (shown in the default location) at C:\Program

Files\HP\Virtual Server Environment\conf\hp_lsa_service.conf.

2. Increase the value of wrapper.java.maxmemory=1024. HP suggests a value

of 2048.

3. Restart the HP Logical Server Automation service.

Suggested action 2

To correct the PermGen space error, modify the configuration file to increase permanent

generation size:

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

VM logical server may not immediately activate when created using the logical

server copy feature

When using Logical Server Copy (Tools→Logical Servers→Copy) to make a copy of a

virtual logical server with storage, the newly created logical server may not immediately

activate. It may fail activation with an error similar to the following:

The save Configuration operation on virtual machine configuration

<vm path> failed: Failed to create VM! Invalid datastore path '[null]'.

Suggested action

Edit the newly created logical server, and modify the datastore information in the logical

server. Save the logical server and it will now activate successfully.

Performing operations on logical servers outside of Matrix OE visualization may

cause incorrect information to be displayed

If you use tools other than Matrix OE visualization 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.

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%