HP-UX Reference (11i v1 05/09) - 5 Miscellaneous Topics (vol 9)

v
vparresources(5) vparresources(5)
more than one attributes. This means it is possible for one device to own all the ALTBOOT, TAPE and
BOOT attributes, but it is not possible for two or more devices to own BOOT.
Users must guard against assigning an attribute to an inappropriate device, for example, assigning BOOT
to a tty. The commands do not check for this, nor do they prevent it.
Table II. Allowed Forms for Each Task
Allowed with
Task Form vPar running
-a (add) cpu:path No
cpu::num Yes
cpu:::[min][:[max]] N/A
(vparcreate only)
io:path[:attr1[,attr2]] No
mem::size No
mem:::base:range No
-m (modify) cpu::num Yes
cpu:::[min][:[max]] No
io:path[:attr1[,attr2]] No
mem::size No
-d (delete) cpu:path No
cpu::num Yes
io:path[:attr1[,attr2]] No
mem::size No
mem:::base:range No
The forms above are subject to the following semantic rules enforced by the commands. Note that accord-
ing to Table II, except for the cpu::num form, a vPar must be in the Down state (or in an alternate data-
base) to apply any of the changes described below. This requirement may be relaxed or removed in a future
release.
• CPUs
• The total number of CPUs assigned to a vPar, specified by cpu::num, must always be within the
range specified by the cpu:::min:max specification. min of these are bound; (num-min) are
unbound.
• Any or all bound CPUs can be specified by explicit path, the cpu:path form. Any that are not so
specified are allocated from the available pool and bound by the vPar monitor.
A corollary to this is that you cannot specify more than the min CPUs by explicit path. If you wish
to specify more, you must first increase the min, which in turn may require you to increase the
max, num, or both.
When you use
-a cpu:path or -d cpu:path you do not change the total number of CPUs in
your vPar. Instead, you replace a monitor-assigned bound CPU with one that you specify (
-a)or
replace a CPU that you specified with a monitor-assigned CPU (
-d).
Hewlett-Packard recommends that users configure specific CPUs only when required for perfor-
mance reasons. In other situations, specify only the total number of CPUs (num) and how many of
these should be bound (min), and allow the monitor to manage the actual CPUs allocated.
• Since the monitor is not consulted when you are configuring a vPar in an alternate database (it
need not even be running), you can specify any value for min (but <= max) in this case. When this
database is loaded into the monitor, the monitor adjusts min downward as required if the specified
number of CPUs is not available.
• Defaults: When a vPar is created, the following defaults are in effect:
• min: Platform dependent, usually
1
• num: 1
• max: If the vPar is created in an alternate database, 32767. If it is created in the live moni-
tor database, max is equal to the total number of CPUs on the entire hardware system.
You can modify these defaults with command line options to the vparcreate or vparmo-
dify
command.
Section 5−−386 Hewlett-Packard Company − 2 − HP-UX 11i Version 1: September 2005