HP-UX Virtual Partitions Administrator Guide (includes A.05.08) (5900-1312, March 2011)

Table 2 Differences Among vPars Versions (continued)
A.05.xxA.04.xxA.03.xxvPars Version
yes
(PA-RISC: vPars A.05.xx)
(Integrity: A.05.02 and
later)
yes
(PA-RISC: vPars
A.04.03 and later)
(Integrity: A.04.04 and
later)
yes (vPars A.03.03 and
later)
Tape Boot Support
nonoyesvPars GUI
Not Required for InstallNot Required for InstallRequired for InstallParmgr
Both Percent Utilization
and Active CPU
Both Percent Utilization
and Active CPU
Percent UtilizationPPU Supported Products
mptconfigmptconfigvparutilSetting SCSI Parameters
1 Dynamic memory migration requires the firmware revisions indicated in the HP-UX Virtual Partitions Ordering and
Configuration Guide.
2 In order to work in a vPars environment, hyperthreading requires the firmware revisions indicated in the HP-UX Virtual
Partitions Ordering and Configuration Guide.
Resource Migration and Required States
The table below shows whether a resource is dynamically migratable; in other words, for each
given resource type and vPars version, the intersecting box shows whether the target virtual partition
must be up or down to migrate the resource.
Table 3 To Migrate the Resource, the Target Virtual Partition State must be...
I/OMemoryCPUsVersion
down
down
bound: down
unbound: up or down
vPars A.03.xx
boot processor: down
all others: up or down
vPars A.04.xx
float: up or down
base: add: up or down
delete: down
vPars A.05.xx
The table below shows the same information, but from the perspective of dynamic migration (in
other words, online migration):
Table 4 Dynamic Migration
A.05.xxA.04.xxA.03.xxvPars Version
Yes for non-boot processorsYes for non-boot processorsYes for unbound CPUsDynamic CPU
Migration
Yes for float. For base, can only
add base memory (cannot delete
online)
NoNoDynamic
Memory
Migration
NoNoNoDynamic I/O
Migration
42 How vPars and Its Components Work