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

migration (in other words, where the target partition is up), it does not apply to the vparcreate
command, where the target virtual partition should never be up during the vparcreate
invocation.
• In the same command, you cannot have an online addition and online deletion. For example,
the following are illegal:
— keira1# vparmodify -p keira2 -a cpu::2 -d cpu::1
— keira1# vparmodify -p keira2 -a mem::1024 -d mem::512
You must specify each change on a separate command line. For example, the following are
allowed:
— keira1# vparmodify -p keira2 -a cpu::2
keira1# vparmodify -p keira2 -d cpu::1
— keira1# vparmodify -p keira2 -a mem::1024
keira1# vparmodify -p keira2 -d mem::512
• In the same command, you cannot make changes to both memory and CPU. For example,
the following is illegal:
— keira1# vparmodify -p keira2 -a cpu::2 -a mem::1024
• In the same command, you cannot make changes by both address and ILM or both address
and CLM. For example, the following are illegal:
— keira1# vparmodify -p keira2 -a mem::1024 -a mem:::0x40000000:256
— keira1# vparmodify -p keira2 -a cell:6:mem::1024 -a
mem:::0x40000000:256
• In the same command, you can specify both ILM and CLM changes. For example, the
following are allowed:
— keira1# vparmodify -p keira2 -a mem::1024 -a cell:6:mem::1024
• In the same command, you can migrate both base and float memory. For example, the
following are allowed:
— keira1# vparmodify -p keira2 -a mem::512:b -a mem::512:f
— keira1# vparmodify -p keira2 -a mem::512:b -a cell:0:mem::512:f
-a cell:2:mem::1024
Memory: Allocation Unit 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. 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 granule size.
• On cellular systems that have System Firmware (SFW) version 6.xx or later installed, a
non-optimal memory configuration may result in CLM memory in the vPars available
memory, even though CLM is not configured. This is new behavior, and must not be
considered an error. This behavior occurs because the firmware returns a portion of the
memory reserved for the firmware back to the operating system as CLM.
CPU: Topics
The CPU topics in this section are:
• “CPU: Concepts and Functionality” (page 202)
• Assigning (Adding) Or Deleting CPUs
CPU: Topics 201