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

CPU, Memory, and I/O Resources (A.05.xx)
Memory: Setting the Granularity Values (Integrity)
Chapter 6
211
Note that this does not set the granularity value in the vPars database. Only vparcreate sets the granularity
value in the vPars database. Typically, you would change the granularity with vparenv rather than
vparcreate if you have more than one database with differing granularities, and wish to switch to a database
with different granularity during the next vPar Monitor boot.
CAUTION The granularity values in firmware must match those in the vPars database used during the
next boot of the vPars Monitor. If the granularity values in firmware do not match those in the
vPars database, the virtual partitions of that database will not boot.
vparcreate
# vparcreate -p vpar1_name [-g ILM: unit [:y] ] [-g CLM: unit [:y] ]
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.
Usage Scenarios
vparcreate with the :y option
The following is a scenario where you would want to use vparcreate with the -g option and the :y
specification:
1. In nPars mode, you create your first virtual partition with a 256 MB granularity value for ILM. The
command is
# vparcreate -g ILM:256:y -p keira1 ...
2. This writes the ILM granularity value to both the vPars database and to firmware. Since the default CLM
granularity value is 128, this also writes the CLM granularity value of 128 to both the vPars database
and to firmware. Because the values in both the vPars database and firmware match, you can boot this
vPars database immediately after setting the nPartition for vPars mode and rebooting the nPartition.
# vparenv -m vPars /* to set the mode */
# shutdown -r /* reboot the system */
vparcreate without the :y option and vparenv
The following is a scenario where you would want to use vparcreate with the -g option but without the :y
specification. It also shows where you need to use vparenv to set the granularity value in the firmware. Note
that this scenario would only occur on Integrity systems.
1. You are in a vPars environment, running the default vPars database of /stand/vpdb that uses the 128
MB granularity values for ILM and CLM. Because the virtual partitions have been booted successfully,
this means the current firmware also has granularity values of 128 MB.