HP-UX Virtual Partitions 6.0 Release Notes

6 Known behaviors and workarounds
Table 5 (page 18) describes problems currently known to occur while using vPars v6.0.
Table 5 Known behaviors in vPars v6.0
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
When the requirements for satisfying
Locality-Optimized Resource Alignment
requirements for satisfying LORA configuration are not met, the following
message is displayed in the syslog of the vPar OS instance:
(LORA) configuration are not met, a
message is displayed.
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 available at http://h20000.www2.hp.com/
bc/docs/support/SupportManual/c02070810/c02070810.pdf
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 may show different values
CPU/memory info in machinfo
output on VSP could be confusing
based on when the command is executed. If executed on the VSP after installing
HP-UX and before installing the VirtualizationBase 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.
After the VirtualBase software is installed, the logical processor count of
machinfo represents the number of VSP logical processors. The remaining
logical processors are removed from the VSP and become part of an active
vPar or sit idle in firmware.
• Part of an active vPar. The logical processors are owned and managed by
the vPar.
• Idle in firmware. The logical processor is not currently assigned to a vPar
and executes in an idle loop waiting to be activated into a vPar or the VSP.
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 VirtualBase 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.
A vPar that transitions past the load of the HP-UX kernel will not produce a
vm.core on the VSP when it is terminated abnormally via a TOC. Once HP-UX
vm.core will not be generated when
vPar is in OS upon TC
transitions to the boot state, the responsibility for state capture when a TOC
occurs is via DUMP. An activating vPar that has not transitioned to the boot
state produces a vm.core when a TOC occurs.
What to do
There is no workaround. This is an expected behavior in vPars.
18 Known behaviors and workarounds