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...
Version | CPUs | Memory | I/O |
|---|
vPars A.03.xx | - bound:
down - unbound:
up or down
| down | down |
vPars A.04.xx | |
vPars A.05.xx | - base:
add: up or down delete: down
|
The table below shows the same information, but
from the perspective of dynamic migration (in other words, online
migration):
Table 2-4 Dynamic Migration
vPars Version | A.03.xx | A.04.xx | A.05.xx |
|---|
| Dynamic CPU Migration | Yes for unbound CPUs | Yes for
non-boot processors | Yes for non-boot processors |
| Dynamic Memory Migration | No | No | Yes for float. For base, can only add base memory (cannot
delete online) |
| Dynamic I/O Migration | No | No | No |
 |
| |
|
 | 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. |
|
| |
|
Printable version
