vparresources.5 (2010 09)

v
vparresources(5) vparresources(5)
the specified device to your vPar.
The vparstatus command will also be able to display agile hardware paths. An example of how an agile
hardware path is displayed by the vparstatus command follows.
[IO Details]
1.0.12.1.0.0x500805f3000ff771.0x400e000000000000 BOOT
Note that virtual partitions running older versions of the product will not be able to specify agile
hardware paths, nor they will be able to properly display them. Virtual partitions running older versions
will be able to co-exist with virtual partitions booting from agile hardware paths, so long as legacy mode
is not disabled in any virtual partition.
Cells
Cells are container objects. They do not exist on systems that do not support hard partitioning, so this
discussion does not apply to those systems. Cells consist of CPUs, memory, and (optionally) I/O devices.
In HP-UX Release 11i, Version 2 (and later releases), cells themselves are not assignable resources. They
cannot be added to or deleted from virtual partitions in their entirety. CPU and memory resources on
cells can be allocated among different virtual partitions. For example, given a cell containing four CPUs,
one CPU can be allocated to each of four virtual partitions, all four to one vPar, or any other possible
combination.
Two additional syntax forms allow you to specify that available resources should be allocated from a
specific cell:
-a cell:cell_id :cpu::num allocates num CPUs on cell_id to the target vPar. The monitor is
allowed to assign any subset of CPUs on cell_id , and this subset may vary from boot to boot.
-a cell:cell_id:mem::size[:base|floating] allocates size MB of base or floating CLM from
cell_id to the target vPar. If the base|floating attribute is not specified, the memory added will
be treated as base memory. If size is not an integral number of granules, it is first rounded upward to
the next integral value. Whether rounded upward or not, the memory must have been previously
configured as CLM by the parmgr or parmodify commands in nPar mode. See parmgr(1M) and
parmodify (1M).
In a non-vPars environment or alternate database, availability is not checked, so the memory specified
becomes a
Requested attribute. It will be validated and may be modified when the database is
loaded into the vPar monitor.
COMMANDS AND THEIR RESOURCE SPECIFICATIONS
Each vPar can be configured with a subset of total system hardware resources such that any given physi-
cal resource is assigned to at most one vPar. This job is managed by two of the virtual partition com-
mands:
• vparcreate, used when creating a new vPar. (Resources can only be added)
•
vparmodify, used when modifying an existing vPar configuration. (Resources can be added,
modified, or deleted)
Each command has specific resource syntax and semantic requirements. For example, some
resource changes can only be made if the target vPar is not running. Some syntax forms can be
specified once. Additionally, beginning in vPars version A.02.02, there are specific hardware path
format rules to follow that did not exist when using previous versions of vPars. All of these are
described in the tables below.
The general form of a resource specification is up to six positional fields delimited by colons (":"). No
whitespace is allowed within any field.
Table I summarizes the three categories (CPU, I/O, and memory) and all the allowable forms
for each.
Table II specifies which forms are allowed for each of the three tasks (add, modify, or delete).
Table III is a detailed description of each syntax form and the conditions required for its use.
Table IV is a description of the hardware path format rules.
HP-UX 11i Version 3: September 2010 − 11 − Hewlett-Packard Company 11