HP vPars and Integrity Virtual Machines V6.1 Release Notes

Table 2 Known behaviors in vPars V6.1
Description/ActionProblem
Resources for a given vPar are chosen (as part of the vPar's
boot up sequence) based on the resource availability and
locality considerations. When the requirements for
satisfying LORA configuration are not met, the following
message is displayed in the syslog of the vPar OS instance:
AutoSensor: LORA Mode Disabled -- Single
Locality Partition.
This message is seen even on a multiple locality vPar when
it does not meet the LORA requirements.
What to do
You can ignore the message. For more details, see the
Locality-Optimized Resource Alignment white paper on the
BSC website http://h20000.www2.hp.com/bc/docs/
support/SupportManual/c02070810/c02070810.pdf
When the requirements for satisfying Locality-Optimized
Resource Alignment requirements for satisfying LORA
configuration are not met, configuration are not met, a
message is displayed.
When a TOC is performed on the VSP or the VSP
encounters an MCA, no vPar crash dump is provided. Only
a VSP crash dump is available and it is augmented with
some debugging information from the vPars.
What to do
Currently, there is no workaround.
No vPar crash dump when the VSP crashes on TOC/MCA
The machinfo command displays system information
from the HP-UX view of the system configuration. The
machinfo command might show different values based
on when the command is executed. If executed on the VSP
after installing HP-UX and before installing the Integrity VM
software, machinfo shows all the sockets and logical
processors. The logical processor count represents cores
if the kernel tunable lcpu_attr value is 0 and threads
when lcpu_attr value is 1. You can obtain the value
of lcpu_attr by using the kctune command.
Note that lcpu_attr is set to zero in the VSP by default
for optimal VSP performance, and so, the logical processor
count is always the CPU core count.
After the Integrity VM software is installed, the logical
processor count of machinfo represents the number of
VSP logical processors and the logical processors in the
vPar/VM pool, but not yet activated in a vPar.
When a vPar is started, the logical processors in the
vPar/VM pool assigned to the vPar are deallocated from
the VSP and the machinfo output in the VSP will reflect
that reduction in logical processor count.
When a vPar is stopped, the processor count shown in the
VSP machinfo output will increase by the number of CPUs
assigned to the vPar.
The memory value displayed by the machinfo command
shows the amount of memory that was available to HP-UX
when booted on the VSP. This memory value includes
memory that is allocated to the vPars and the memory used
by the VSP. Unlike the logical processor count, the memory
amount does not change with the installation of the Integrity
VM software.
What to do
As workaround, use the vparhwmgmt —p cpu —l
command to view the number of processor cores that are
allocated to the VSP and to the vPar pool.
CPU/memory info in machinfo output on VSP could be
confusing
22 Issues in this release