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

incorrectly using the initial vparcreate command, you cannot adjust it later. You must re-create
the vPars database.
Usage Scenario
In standalone mode, you create your first virtual partition with a 256 MB granularity value for both
ILM and CLM. The command is:
# vparcreate -g ILM:256 -g CLM:256 -p keira1 ...
This writes the granularity values to the vPars database.
Note that with the vparcreate command, when you specify the granularity value for only one
type of memory (ILM or CLM), the granularity value for the other type of memory is set using the
default granularity value. For example, if you specify only -g ILM:256, the -g CLM:128 is
implied where 128 is the vPars default granularity value.
Memory: Allocation Notes
• The default memory assigned to a virtual partition is 0 MB, so you need to specify enough
memory for your applications and the operating system. While there is no specific minimum
base memory requirement per vpar, the HPUX kernel does require a certain amount of base
memory to boot successfully. For this reason, we currently recommend that 1 GB of base
memory is assigned per vpar. The more base memory a virtual partition has, the better the
performance will be. This is especially true of applications that require large amounts of locked
memory. See the Installation and Update Guide for your OS and the nPartition Administrator’s
Guide for your server.
• The unit for the specified size of memory for the vPars commands is megabytes; parmodify
uses gigabytes.
• Memory is allocated in multiples of 128 MB by default. Memory assignments are also rounded
up (to the next highest granule boundary).
CPU
NOTE:
Processor Terminology
Processing resources under vPars, both as input arguments and command outputs, are described
as “CPUs.” For multi-core processors such as the PA-8800 and dual-core Intel Itanium processors,
the term “CPU” is synonymous with “core.” The term “processor” refers to the hardware component
that plugs into a processor socket. Therefore a single processor can have more than one core, and
vPars commands will refer to the separate cores as distinct “CPUs,” each with its own hardware
path.
Two vPars terms pre-date multi-core processors, so they are exceptions to this terminology:
• “Boot processor,” which refers to the CPU (that is, core) on which the OS kernel of the virtual
partition was booted.
• “Cell local processor (CLP),” which refers to a CPU (core) on a specified cell.
For more information on dual-core processors, see “CPU: Dual-Core Processors” (page 227).
CPU migration refers to adding CPUs to and deleting CPUs from a virtual partition. Dynamic CPU
migration refers to migrating CPUs while the target virtual partition is running. vPars allows the
assignment of most CPUs while the virtual partitions are running.
For vPars A.04.01 and later, the two types of CPUs are Boot Processor and dynamic CPUs. This
discussion begins at “CPU: Boot Processor and Dynamic CPU Definitions ” (page 220). The bound
and unbound CPU types in vPars A.03.xx and earlier no longer apply.
Memory: Allocation Notes 219