HP-UX Virtual Partitions Administrator Guide (includes A.05.07) (5900-1229, September 2010)

designated-admin, then no virtual partitions will be able to perform vparmodify,
vparremove, or vparcreate operations on other virtual partitions.
• The status details reported by the vparstatus command are determined by the target
virtual partition version and the vPars software version of the virtual partition issuing the
command.
— Cell Local Memory (CLM) and Cell Local Processor (CLP) details are displayed only
when listing details from an HP-UX 11i v2 or 11i v3 virtual partition.
— Bound and floater CPU information is displayed only when listing details from an
HP-UX 11i v1 virtual partition. This information is presented in legacy (HP-UX 11i v1)
format.
— HP-UX 11i v1 bound processors are shown only when the HP-UX 11i v1 virtual partition
is in an “up” state.
— When the vparstatus command is run from an HP-UX 11i v2 or v3 virtual partition
to display information about an HP-UX 11i v1 virtual partition:
◦ The output is displayed in HP-UX 11i v2/v3 format.
◦ The bound CPUs in an HP-UX 11i v1 virtual partition are reported as “Min CPUs”.
— When the vparstatus command is run from an HP-UX 11i v1 virtual partition to
display information about an HP-UX 11i v2 or v3 virtual partition:
◦ An HP-UX 11i v2 or 11i v3 virtual partition's monarch CPU is reported as “bound”.
◦ If an HP-UX 11i v2 or 11i v3 virtual partition has Cell Local Processors, some CPUs
are reported as “user bound”. The vparstatus -A option does not list CLP details
when issued from HP-UX 11i v1.
◦ All other HP-UX 11i v2 or 11i v3 CPUs are shown as unbound (floater).
◦ Any Cell Local Memory assigned to an HP-UX 11i v2 or 11i v3 virtual partition is
listed as part of the total memory. (That is, the “total memory” reported for the
virtual partition is a sum of the interleaved memory and CLM.)
• The vparstatus -P command option is provided to display the HP-UX version running
on virtual partitions in a mixed HP-UX 11i v1/v2/v3 vPars environment.
• HP Global Workload Manager (gWLM) is supported in mixed HP-UX 11i v1/v2 vPars
environments with the following restrictions:
— Do not nest processor sets (Psets) under vPars A.03.05.
— Do not assign CLPs to any of the virtual partitions.
For details about these restrictions for using gWLM in a mixed vPars environment see the
HP-UX Virtual Partitions Release Notes (A.03.05).
• The Virtual Partition Manager (vparmgr) GUI is supported only on HP-UX 11i v1 virtual
partitions in a mixed HP-UX 11i v1/v2/v3 vPars environment.
• In a mixed HP-UX 11i v1/v2/v3 vPars environment, dynamic memory migration is only
supported on the vPars versions that support dynamic memory migration. In other words,
both the source and target virtual partitions must be running vPars A.05.03.
• Hyperthreading is not supported in mixed HP-UX 11i v1/v2/v3 vPars environments.
Enabling hyperthreading (HT ON) is supported only on Integrity systems with
hyperthreading-capable processors. However, only HP-UX 11i v3 supports hyperthreading.
HP-UX 11i v2 cannot boot on an Integrity system that has hyperthreading enabled, and
HP-UX 11i v1 only is supported on PA-RISC systems.
• HP-UX 11i v1 virtual partitions (vPars A.03.05) does not support CLM or CLP resources.
It is possible—but not supported—to add CLM or CLP resources to an HP-UX 11i v1 virtual
partition when it is in a “down” state. However, booting an HP-UX 11i v1 virtual partition
will be halted if it has CLM or CLP resources assigned to it.
• The system firmware must match the vPars A.05.03 firmware requirements.
64 Planning Your System for Virtual Partitions