HP-UX Virtual Partitions Administrator's Guide (includes A.03.05 and A.04.05)

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 scenario is where you would want to use
vparcreate with the -g option and the:yspecification:
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
1
# shutdown -r
2
1
Set the mode for the next nPartition reboot.
2
Reboot the system.
vparcreate without the :y option and vparenv The following scenario is where you would
want to use vparcreate with the -g option but without the :yspecification. 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 that the current firmware has granularity values of
128 MB.
2. You create an alternate database /stand/vpdb.alt with a granularity value of 512 MB
for ILM and 256 MB for CLM.
# vparcreate -D /stand/vpdb.alt -g ILM:512 -g CLM:256 -p keira1 ...
3. This writes the granularity value to the vPars database but not to firmware, which allows
you to continue using the active vPars database /stand/vpdb with its 128 MB granularity
value.
When you wish to load /stand/vpdb.alt, then you can set the granularity value in
firmware using vparenv, reboot the nPartition, and load the alternate database.
# vparenv -g ILM:512 -g CLM:256
1
MON> reboot
2
...
HPUX> boot vpmon -D /stand/vpdb.alt
3
1
Set the granularity value in firmware.
2
Reboot the nPartition.
3
Load the alternate vPars database.
224 CPU, Memory, and I/O Resources (A.04.xx)