HP Integrity Virtual Machines Release Notes Version A.03.50

3.9 hpvmstop Manpage Incorrect
The hpvmstop manpage incorrectly states that the -g option is the default behavior when in
fact the -h option is the default.
3.10 New option for hpvmstatus Command
The user can now determine whether the VM Host and guests use Cell Local Memory (CLM)
interleaved Memory (ILM) with the hpvmstatus -C option. The hpvmstatus -C command
provides a list of guests with their memory type.
If you do not use CLM at all, then all the guests use Interleaved Memory (ILM). If however, CLM
is set, every hpvmstart command checks whether Integrity VM chooses cell or interleaved for
this particular guest, and if cell is chosen, which cell it is. For example, you have an 8 GB VM
Host configured with 75 percent CLM and 25 percent ILM. With two cells, each contributes 3
GB to cell local and 1 GB to interleaved. On boot, the operating system takes 1 GB of the
interleaved memory. If each guest takes 1 GB to start, the breakdown looks like this:
• guest 1: cell 0 (2 GB CLM left)
• guest 2: cell 1 (2 GB CLM left)
• guest 3: cell 0 (1 GB CLM left)
• guest 4: cell 1 (1 GB CLM left)
• guest 5: cell 0 (no CLM left)
• guest 6: cell 1 (no CLM left)
• guest 7: interleaved (no memory left at all)
3.11 The hpvmstatus Display Can Lag in a Serviceguard Cluster
When Integrity VM guests are configured as packages in a Serviceguard (SG) cluster, the
hpvmstatus command displays which VM Host is running the distributed guest as an SG
package. This information comes from SG and can be delayed by as much as 10 seconds. This
delay does not cause any risk of starting the same guest on two different Integrity VM Hosts,
because SG is controlling the start of these guests and will allow only a single instance to run at
any time.
3.9 hpvmstop Manpage Incorrect 33