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

where:
-a add
-d delete
-m modify
cell_ID the cell number
size the quantity of memory in MBs
base add/delete as base memory
float add/delete as float memory
Example
• To add 1024 MB of memory as float from cell 6 to the existing partition keira2:
keira1# vparmodify -p keira2 -a cell:6:mem::1024:float
• You can set both ILM and CLM memory on the same partition. To assign 1024 MB of available
CLM and 1024 MB of available ILM as base memory to keira2:
keira1# vparmodify -p keira2 -a cell:6:mem::1024 -a mem::1024
• To see how much of the ILM memory is currently float memory, use vparstatus -v as shown
in the example below.
# vparstatus -p winona4 -v
...
[Memory Details]
...
CLM, user-assigned [CellID Base /Range]: 0 0x700b0000000/256 (Floating)
(bytes) (MB) 0 0x700c0000000/256
CLM, monitor-assigned [CellID Base /Range]: 0 0x70080000000/512
(bytes) (MB) 0 0x700a0000000/256 (Floating)
CLM (CellID MB): 0 1280 (Floating 512)
CLM Granularity (MB): 256
NOTE: When assigning ILM or CLM memory to a down partition, the size only reserves the
amount of physical memory the virtual partition gets. The exact physical ranges of memory the
virtual partition gets is decided by the vPars Monitor when the virtual partition boots. The vPars
Monitor will attempt to pick the memory ranges such that the sum of the ranges add up to the
amount of ILM and CLM reserved for the partition. However, due to memory fragmentation, which
occurs due to memory already taken by the vPars Monitor, firmware, or bad pages, the sum of
the ranges picked by the vPars Monitor may be slightly less than or more than the specified amount
reserved for the partition. If this occurs, the vPar Monitor adjusts the specified amount in the database
to the sum of the ranges that it picked.
See also “Memory: Notes on vPars Syntax, Rules, and Output” (page 190) and “Memory, CPU:
Canceling Pending Operations” (page 201).
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 183).
For usage information, see the vparmodify(1M) manpage. You should select your base:range after
consulting vparstatus -A to determine which ranges are available.
182 CPU, Memory, and I/O Resources (A.05.xx)