vparresources.5 (2010 09)

v
vparresources(5) vparresources(5)
Table II. Allowed forms for each task
Allowed with
Task Form vPar running
-a (add) cell:cell_id:cpu::num Yes
cpu:path Yes
cpu::num Yes
cpu:::[min][:[max]] N/A
(vparcreate only)
io:path[:attr1[,attr2]] No
cell:cell_id:mem::size Yes
mem::size Yes
mem:::base:range Yes
-m (modify) cpu::num Yes
cpu:::[min][:[max]] No
cell:cell_id:cpu::num Yes
io:path[:attr1[,attr2]] No
mem::size Yes
cell:cell_id:mem::size Yes
-d (delete) cell:cell_id:cpu::num Yes
cpu:path Yes
cpu::num Yes
io:path[:attr1[,attr2]] No
cell:cell_id:mem::size No
cell:cell_id:mem::size:base No
cell:cell_id:mem::size:floating Yes
mem::size No
mem::size:base No
mem::size:floating Yes
mem:::base:range Yes
The forms above are subject to the following semantic rules enforced by the commands. Note that accord-
ing to Table II, except for the operations involving CPUs and memory, a vPar must be in the
Down state
(or in an alternate database) to apply any of the changes described below.
• CPUs
1)
-a cpu::num specifies that num CPUs be added to the target vPar. If the target vPar is in the
live monitor database, at least num CPUs must be available in the monitor.
2)
-a cpu:path specifies that the CPU at hardware path path be added to the target vPar. The
CPU must not be already assigned to another vPar. If the target vPar is in the live monitor data-
base, the CPU must also exist.
3)
-a cell:cell_id :cpu::num specifies that num CPUs on cell cell_id (CLPs) be added to the
target vPar. If the target vPar is in the live monitor database, at least num CPUs on cell_id must
be available in the monitor.
4) No matter how they are specified, the total number of CPUs assigned to a vPar must always be
within the range specified by the
cpu:::min:max specification.
5)
-m cpu::num specifies that the total non-cell specific processors in the vPar be set to num. This
operation may result in assignment or deletion of CPUs.
6)
-m cell:cell_id :cpu::num specifies that the total cell specific processors from cell cell_id in
the target vPar be set to num. This operation may result in assignment or deletion of CPUs.
7) 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 active CPUs in the underlying hard partition.
You can modify these defaults with command line options to the
vparcreate or vparmo-
dify command only when the vPar is down.
HP-UX 11i Version 3: September 2010 − 13 − Hewlett-Packard Company 13