HP-UX Virtual Partitions Administrator's Guide (includes A.05.03)

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 2-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 2-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
NOTE: In a mixed HP-UX 11i v2/v3 vPars environment or 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, memory migration operations can be initiated only
from virtual partitions running vPars A.05.xx, and the virtual partition target for the memory
migration must be running vPars A.05.xx as well.
Transitioning from vPars A.03.xx to vPars A.04.xx/A.05.xx (CPU Syntax
and Rules)
The values in a vPars database that were created using vPars A.03.xx and ported to vPars A.04.xx
will have the following A.04.xx meanings for those values; likewise, using vPars A.03.xx syntax
on a vPars A.04.xx system has the following A.04.xx meanings.
This table summarizes the A.04.xx and A.05.xx CPU syntax and rules
44 How vPars and Its Components Work