HP-UX Virtual Partitions 6.0 Release Notes

Table 5 Known behaviors in vPars v6.0 (continued)
Description / actionProblem
A vPar may hang indefinitely during boot without any indication of the cause
(This is a very rare occurrence). If a vparstatus is issued, the vPar in question
vPar hangs during reboot
may show a state of ATTN which is a visual indication that the vPar is
unresponsive. The ATTN state is only displayed for vPars that have been
unresponsive for a period of time. If the hang happens early in boot the vPar
may not display the ATTN state even after waiting for 10 minutes.
What to do
Wait for 10 minutes from the last console output to make sure that the vPar is
not making forward progress. Use the vparstatus command to determine if
the vPar is in the ATTN state. If the vPar is still not making forward progress
after 10 minutes, use the vparreset –h command to the vPar that is hung.
Try to boot the vPar after it comes back to the off state.
Upon repeated reboots, a vPar may not boot if its memory requirement is not
met. If this condition is encountered, the following error message is displayed
after executing vparboot:
vparboot failure due to resource
depletion
Not enough space.
This message reflects a low memory condition on the VSP that causes a memory
allocation failure that prevents the vPar from activating.
What to do
The failure may be transitory as an application may be using an excessive
amount of memory. Check for any large applications that may be running on
the VSP and terminate them. If the failure persists, contact your HP representative
for assistance in reconfiguring the VSP free memory pool.
When the virtual partitions are active and a shutdown –r is issued from the
VSP, the virtual partitions attempt to shutdown but do not fully make it to the
off state. The shutdown hangs and the system must be reset.
VSP shutdown may hang if virtual
partitions are active
What to do
A standard practice is to log in into each virtual partition and perform a
shutdown. After all the virtual partitions are in the off state, you can shutdown
the VSP.
If the base page size is changed to value other than 4K, the output value
corresponding to 4K is the value for the new base page size. This is true for
further displayed page sizes i.e. 8K, 16K, 64K, and so on.
Example 2 When base page size = 4K
...
149003 Page Select Size Successes for Page size 4K
139682 Page Select Size Successes for Page size 8K
494477 Page Select Size Successes for Page size 16K ...
Example 3 When base page size = 64K
...
28 Page Select Size Successes for Page size 4K
67 Page Select Size Successes for Page size 16K
14 Page Select Size Successes for Page size 64K
2 Page Select Size Successes for Page size 256K ...
In the example for base page size 64, the value 28 actually refers to the page
size 64K, 67 refers to the page size 256K, and so on.
Because the base page size of host is
set to 64K, the vmstat command
might show incorrect results
What to do
There is no workaround.
21