HP vPars and Integrity Virtual Machines V6.1 Release Notes

Table 2 Known behaviors in vPars V6.1 (continued)
Description/ActionProblem
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.
vm.core will not be generated when vPar is in OS upon
TC
The vPars v6 product supports dynamic CPU addition and
deletion. The selection criteria for CPU addition are
performed from within the VSP based on LORA CPU OLD
policy policies. The selection criteria for CPU deletion is
performed from within the HP-UX instance that is target of
the CPU deletion. The following criteria are used to select
the CPU cores to be deleted:
• Only cores in the default pset (see psrset(1M)) can
be dynamically removed.
• The monarch core can never be deleted.
• If the default pset does not contain enough cores to
satisfy a full request to reduce the number of cores, the
processor assignments will remain unchanged.
• Processors can be moved to the default pset and then
deleted.
What to do
There is no workaround.
CPU OLD Policy
When Serviceguard detects a hang of the operating system,
it uses a system interface to TOC the operating system. If
Serviceguard initiates a TOC in a TC/RS/stop behavior
during Serviceguard TOC v6.0 vPar, any subsequent
vparreset operation initiated from the VSP to that specific
vPar causes a message to be logged to syslog. The
command completes but no action is taken until the
Serviceguard TOC operation completes.
What to do
There is no workaround.
TC/RS/stop behavior during Serviceguard TOC
An ioscan issued from within a vPar does not display any
LUNs behind the NPIV HBA unless the –N option is
specified. The ioscan command without NPIV LUNs not
shown by default invocation of ioscan the –N option only
displays devices that use the old style device file format.
The NPIV LUNs use the agile device file format and require
the –N option to ioscan in order to display LUNs in the
output.
What to do
Use the –N option with the ioscan command to view
devices behind NPIV HBAs.
NPIV LUNs not shown by default invocation of ioscan
3.1 Changes and Issues in this Release 23