HP-UX Virtual Partitions Administrator Guide (includes A.05.07) (5900-1229, September 2010)

Memory: Assigning (Adding) Or Deleting by Address Range
Within the already allocated memory sizes, you can specify the memory address ranges using
the mem:::base:range[:base|float]syntax. However, this is not recommended unless
you are familiar with using memory addresses. For PA-RISC systems, you should also be familiar
with the requirement that all HP-UX kernels fit within 2 GB of memory, as described in “2 GB
Restriction (PA-RISC only)” (page 192).
For usage information, see the vparmodify(1M) manpage. You should select your base:range
after consulting vparstatus -A to determine which ranges are available.
NOTE:
• Specifying an address range to a virtual partition that is down does not increase the amount
of memory assigned to the virtual partition. The address range is a specific subset of the
existing ILM or CLM amount assigned to the virtual partition. Therefore, the total amount
of memory specified by ILM or CLM addresses cannot exceed the amount of ILM and CLM
assigned to the virtual partition.
However, specifying an address range to a virtual partition that is up does increase the
amount of memory assigned to the virtual partition.
• Address ranges are unique within a given nPartition. Therefore, specifying base:range
(and not a cell_ID) is sufficient for using an address range within CLM. You can use
vparstatus -A to list the available ranges and whether the ranges are a part of ILM or
CLM. Further, if the range is within CLM, vparstatus -Aalso lists to which cell the range
belongs.
• See also “Memory: Notes on vPars Syntax, Rules, and Output” (page 200) and “Memory,
CPU: Canceling Pending Operations” (page 214).
CAUTION:
• Normally, ranges are granule-aligned (in other words, the starting address and the ending
address of the range is a multiple of a granule). However, due to memory fragmentation,
some of the ranges may not be granule-aligned. vPars does not support assigning ranges
that are not aligned to a granule and will return an error when such ranges are assigned to
a virtual partition.
2 GB Restriction (PA-RISC only)
When ranges are specified for the entire memory owned by a partition, you should ensure that
at least one of the ranges is below 2 GB and is large enough to accommodate the kernel for that
partition. However, other partitions also require memory below 2 GB for their kernels. Hence,
you also should ensure that the specified range below 2 GB is not so large such as to preclude
memory below 2 GB for the other partitions.
In general terms, the sum of the size of the kernels must be < 2 GB. To calculate the kernel sizes,
see “Calculating the Size of Kernels in Memory (PA-RISC only)” (page 317).
If a partition contains a user-specified float range below 2 GB, the partition will not boot. Ensure
that you have not assigned a float range below 2 GB on PA-RISC. If you have, remove such a
specified float range.
192 CPU, Memory, and I/O Resources (A.05.xx)