HP-UX Virtual Partitions Administrator's Guide (includes A.05.02)

Planning Your System for Virtual Partitions
Planning Your Virtual Partitions
Chapter 3
61
We have three CPUs that were not assigned to any of the virtual partitions, so we will have three CPUs
available.
vPars A.03.xx and earlier
For this example, winona1 will have two bound CPUs, winona2 will have two bound CPUs where the
hardware paths will be 41 and 45, and winona3 will have one bound CPU.
Unbound CPUs are assigned in quantity. We have three CPUs that were not assigned to any of the virtual
partitions, so we will have three unbound CPUs available.
Memory
For detailed information on memory allocation, please read “Memory: Allocation Notes” on page 257. If you
are planning an A.05 system, you should also see “Memory: Topics” on page 194.
NOTE 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. Please see the Install and Upgrade Guide for your OS and the nPartition
Administrator’s Guide for your server
In our examples, we will use the following sizes:
Unassigned
CPUs
three CPUs are available
Partition
Name
winona1 winona2 winona3
Bound CPUs
total = 2
min = 2
total = 2
min = 2
paths = 41,45
total = 1
min = 1
Unbound
CPUs
three CPUs are available
Partition
Name
keira1 keira2 keira3
Memory
1024 MB 1024 MB 1024 MB
Partition
Name
winona1 winona2 winona3
Memory
1024 MB 1280 MB 1280 MB