HP Integrity Virtual Machines 4.2.5: Release Notes

6.2.13.10 Reenter Command to Start Packages
The procedure for configuring and starting guest packages includes the cmrunpkg command.
This command does not always work the first time you enter it. If the command does not start the
package, re-enter the command.
6.2.13.11 Do not Use Integrity VM Commands to Manage Distributed Guests
Guests configured as Serviceguard packages should be stopped and started using Serviceguard
package control commands. Do not use the Integrity VM commands (hpvmstart, hpvmstop,
and hpvmconsole) to start and stop these types of guests. For more information about using
Serviceguard to manage virtual machines, see the HP Integrity Virtual Machines 4.2: Installation,
Configuration, and Administration manual.
6.2.13.12 Different Cluster Nodes Report Virtual Machine Status Differently
Integrity VM commands can receive different warnings and errors from guests running on different
Serviceguard nodes. For example, the Serviceguard node that is starting a guest as part of a
package knows that the guest is running before any other nodes know. (The delay is usually less
than 10 seconds.) Commands that are run on different servers report different errors or warnings
depending on whether the guest is running or not.
6.2.13.13 Syslog Entries for cmcld Can Be Ignored
With Serviceguard and Integrity VM running, you might see the following types of message in the
syslog file:
Syslog entries - cmcld[XXXX]: Warning: cmcld process was unable to run for the last X.XX seconds
These messages can be ignored.
6.2.13.14 Using Integrity Virtual Machines Manager (VMMgr) to Manage Distributed Guests
The following situation might occur when you are using Insight Dynamics — VSE to manage
distributed guests (guests that are configured as Serviceguard packages):
• There is a guest configuration file for each guest on each VM Host. Therefore, when you
modify a distributed guest you must modify the guest on each VM Host that is a cluster node.
6.2.14 Managing Guests using gWLM
Guests configured with processing power specified in cycles instead of percentage are incompatible
with gWLM A.02.50 and earlier versions.
If gWLM/Insight Dynamics — VSE produces an error message similar to the following, a guest is
configured with the processing power specified in cycles:
A VM encountered with no size
This is apparent when using gWLM A.02.50 with Integrity VM A.03.00. You can correct the
problem by modifying the guest and specifying processing power in percentage rather than CPU
cycles. For example, to modify the guest named compass1 to use 10% of the CPU processing
power, enter the following command
# hpvmmodify -P compass1 -e 10
You must boot the guest to initiate this setting for gWLM.
Alternatively, upgrade gWLM to A.03.00 for use with Integrity VM A.03.00.
6.2 Known Issues and Information 67