It means, you are setting granularity. However, the default value is the same value you are trying to specify.
Granularity refers to the unit size in which memory is assigned to all virtual partitions in a given vPars database (vpdb). Granularity reflects only the unit size of memory and not the amount of memory that is assigned.
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.
Integrity Systems.
There are two areas where granularity values are set:
- The nPartition firmware, specifically the EFI variables in NVRAM (non-volatile RAM).
- 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 Monitor itself. Note that this means the update firmware option ([:y]) of
vparcreate is ignored on PA-RISC.
Syntax works like this:
# vparcreate -p vpar1_name [-g ILM:unit[:y] ] [-g CLM:unit[:y] ]
Note the below:
If you specify the above command without the :y, vparcreate only writes the unit granularity value to the vPars database; it does not write the value to firmware.
If you specify the above command with the :y, vparcreate writes the unit granularity value to both the vPars database and to firmware.
When using this method, note that the -g option must be performed when creating the vPars database (in other words, when performing the initial vparcreate command). If you choose not to set a value, or if you set
the value incorrectly using the initial vparcreate command, you cannot adjust it later. You must re-create the vPars database.
-DB
