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

3. Remove the amount of :base memory from the target partition that you wish to convert to
:float memory.
keira1# vparmodify -p keira3 -d mem::512
4. Add that amount of memory as :float to the target partition.
keira1# vparmodify -p keira3 -a mem::512:float
5. Boot up the target partition.
keira1# vparboot -p keira3
NOTE: If you have the available memory and do not wish to shut down the target virtual partition,
instead of converting base memory to float memory, you can simply add that amount of memory
as float memory while the target partition is up:
keira3# vparmodify -p keira3 -a mem::512:float
NOTE:
Mixed vPars Environments
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, the both source and target virtual partitions must be running vPars
A.05.xx.
It is possible to perform add/delete memory operations on virtual partitions running A.04.xx, as
long as the target virtual partition is in the down state. Note that the vparmodify command must
be executed on a virtual partition running vPars A.05.xx.
For more information on mixed HP-UX 11i v2/v3 vPars environments or mixed HP-UX 11i v1/v2/v3
vPars environments, see “Mixed HP-UX 11i v2/v3 vPars Environments in vPars A.05.xx” (page 58)
or “Mixed HP-UX 11i v1/v2/v3 vPars Environments in vPars A.05.03” (page 62).
Memory: Granularity Concepts
Granularity refers to the unit size by which memory assigned to all virtual partitions in a vPars
database (vpdb) can be increased or decreased. Granularity reflects only the unit size of memory
and not the amount of memory that is assigned.
This section briefly covers configuring memory granularity.
The default granularity is 128 MB for ILM and 128 MB for CLM. However, you can specify your
own granularity for CLM and/or ILM. Granularity has some specific restrictions and cannot be
changed in a vPars database after they are set. Be sure to read the CAUTION portion in the next
section.
Granularity Value Locations
Integrity Systems. There are two areas where granularity values are set:
1. The nPartition firmware, specifically the EFI variables in NVRAM (non-volatile RAM).
2. The vPars database.
In order for the virtual partitions in the vPars database to be able to boot, the granularity values
in the vPars database must match the granularity values in the firmware.
On Integrity systems, memory is divided into the granules by the firmware; therefore, it is required
that you set and match the corresponding EFI variables.
PA-RISC systems. There is only one area where granularity values are set: the vPars database.
For PA-RISC, there are no granularity values in the PA-RISC firmware. The memory is divided into
the granules by the vPars Monitor itself. Note that this means the update firmware option ([:y]) of
vparcreate is ignored on PA-RISC.
Memory: Granularity Concepts 185