HP Integrity Virtual Machines Version 4.2 Release Notes

DynMem Min: The minimum memory that can be dynamically allocated to this virtual
machine with the dynamic memory allocation capability or automatic memory
reallocation (AMR).
—
— Memory EntitleDynMem Target: The value of the desired memory allocation for the
virtual machine. It may be set manually or automatically (by AMR). The amount of
memory entitlement this virtual machine is guaranteed to have allocated to it, provided
it has memory demand. This value is meaningful only if AMR is enabled for the virtual
machine. Otherwise, the value is ignored.
— DynMem Max: The maximum memory that can be dynamically allocated to this virtual
machine with the dynamic memory allocation capability or AMR.
— DynMem Current: The actual, current memory allocated to the virtual machine.
— Comfort Min: The memory allocation required to relieve memory "pressure" in the
virtual machine.
— Total Memory: The absolute maximum amount of memory this virtual machine may
be allocated.
— Free Memory: Amount of free memory in the virtual machine (according to the operating
system running there).
— Available Memory: Amount of memory allocated to the virtual machine's user processes
but not locked. This memory is available for paging by the virtual machine's operating
system.
— Memory Pressure: A value between 0 and 100 used as an indicator of memory deficit
and paging. The higher the number the longer the system has been in a memory deficit.
— AMR Chunk: The granularity of memory allocation used by AMR to increase or decrease
that allocated to a virtual machine.
— AMR State: Indicator for whether AMR is enabled or disabled for this virtual machine.
5.1.2 Boot-Problem Messages Now Found In Log File
Boot-problem messages generated by either the hpvmcreate, hpvmmodify, or hpvmstart
command and displayed on your screen are now also saved to your log file, /var/opt/hpvm/
common/command.log.
5.2 Known Issues and Information
The following sections describe known issues and information from previous releases that still
apply to V4.2.
5.2.1 Display Output from Some Integrity VM Tools Might Change in Form and
Content
Specific display output from some Integrity VM tools, such as the hpvmstatus command, is
subject to occasional changes of form and content. Program scripts should always use
machine-readable output options (for example, hpvmstatus -M) whenever available to avoid
future script maintenance.
5.2.2 Enabling or Disabling Virtual CPUs Online
Starting with HP Integrity VM V4.2, it is possible to change the number of enabled CPUs in
HP-UX guests, using the hpvmmgmt –c num command. This command sets the number of
enabled virtual CPUs to the number indicated by num, and disables the others. Depending on
the kernel version, Linux guests might support enabling or disabling virtual CPUs by writing
into /sys/devices/system/cpu/cpuN/ online, as on a physical system. Disabled virtual
CPUs no longer show up in the guest in commands such as top or GlancePlus, and no longer
consume resources on the host. However, disabled virtual CPUs still appear on the host, for
example in the hpvmsar command.
56 Using Integrity VM Commands