vparresources.5 (2010 09)

ManualsBrandsHP ManualsSoftwareHP-UX Manpages

vparresources(5) vparresources(5)

NAME

vparresources - description of virtual partition resources and their requirements

Platform Support Remarks

This

vparresources

describes functionality on system not running Onboard Administrator (OA) based

partition management. For

vparresources

on systems with OA based partition management, refer to

vparresource2(5) by typing

man vparresources2

DESCRIPTION

Hardware resources are the most important property of a virtual partition (vPar). These resources are

divided into four major categories, or types:

• CPUs

• Memory

• I/O devices, such as disks, terminals, tapes and printers.

• Cells, hardware containers of processors (CPUs), memory, and I/O devices.

The essence of virtual partitions is the allocation and distribution of a set of resources among multiple

instances of the HP-UX operating system, each running in its own software environment. Resources,

once assigned to a vPar, belong only to that vPar and are not visible or accessible to other virtual parti-

tions except through the use of vPars commands such as

vparstatus to view them, or

vparmodify to

change the assignment of one or more resources or attributes. For example, if the I/O device at hardware

path 0.1.2.3.4.5 is assigned to vPar A, it cannot be accessed by vPar B. A user on vPar B can use the

vparstatus command to display the conﬁguration of vPar A, including this device, but can not other-

wise use the device.

Note: The

ioscan command displays hardware paths as a list of numbers separated by forward slashes

and dots. The vparstatus command displays all hardware path elements separated only by dots.

Either form can be supplied to the vparcreate or vparmodify command when conﬁguring a virtual

partition.

The

ioscan command can display either legacy or agile hardware paths depending on the options used.

It can also display mapping information between legacy and agile hardware paths. Refer to the

ioscan (1M) manpage for more information.

The Virtual Partition Database File

Virtual partition conﬁgurations (attributes and resources) are kept in a database ﬁle. The default

ﬁlename is

/stand/vpdb but other names may be speciﬁed. You can create the ﬁle in any path, but to

be used by the vPar monitor, the ﬁle must reside in /stand

On Itanium-based platforms, there must also be a soft link between the database ﬁle and an identically

named ﬁle in the

/stand/boot.sys/stand

directory. The link is not required on PA platforms. The

command creates this link for you when you create the database ﬁle in the

/stand

directory. If you

create it in a different directory and later move it to

/stand, or if you create it on one system but copy it

to another for use, you must manually create the link.

When the monitor is loaded, it reads the speciﬁed (or default) ﬁle into its memory. Any conﬁguration

changes while the monitor is running are made to this memory copy and then written to the disk copy of

all running virtual partitions.

Requested and Effective Resources

Because the monitor requires a database ﬁle, you must ﬁrst create one with the vparcreate command

while running in a full hard partition (nPartition) or on a supported non-partitioned system. Any

resources you specify at this time (or at any time when the monitor is not running) are termed

Requested, because they are not checked for existence. For example, vPars will allow you to distribute

16 GB of memory among your virtual partitions even if the nPartition has only 8 GB. This is because you

may be conﬁguring the database for use on another nPartition. vPars only ensures that you do not assign

the same speciﬁc resource to more than one vPar.

When the monitor loads this database ﬁle, it checks the existence of all the speciﬁed

Requested

resources, adjusting any that require it. The result of this validation step is a set of Effective

resources. In a running vPars environment, the monitor checks both existence and duplicate assignment

for every proposed resource change.

HP-UX 11i Version 3: September 2010 − 1 − Hewlett-Packard Company 1

Summary of content (32 pages)

PAGE 1
vparresources(5) vparresources(5) NAME vparresources - description of virtual partition resources and their requirements Platform Support Remarks This vparresources describes functionality on system not running Onboard Administrator (OA) based partition management. For vparresources on systems with OA based partition management, refer to vparresource2(5) by typing man vparresources2. DESCRIPTION Hardware resources are the most important property of a virtual partition (vPar).
PAGE 2
vparresources(5) vparresources(5) When you use the vparstatus command when the monitor is not running, or if you specify a database other than the one currently loaded into the monitor, it displays Requested resources. Otherwise it displays Effective resources. Resources described in this manpage are Effective resources unless noted otherwise. RESOURCES Different resource types call for different resource management. Each resource type and its management is described below.
PAGE 3
vparresources(5) vparresources(5) If the vPar is Up, the result varies as follows: • If path is that of a generically-allocated CPU that the monitor assigned to the vPar when it was booted, it changes to be specifically assigned. It will remain associated with the vPar until deleted by specific path. But the total CPU count does not change, hence iCAP need not authorize the operation.
PAGE 4
vparresources(5) vparresources(5) [CPU Details] Min/Max: 1/8 User assigned [Path]: Boot processor [Path]: 0.12 Monitor assigned [Path]: 2.10 2.11 2.12 3.10 3.11 Non-cell-specific: User assigned [Count]: 1 Monitor assigned [Count]: 3 Cell-specific [Count]: Cell ID/Count 3 2 Note that in the path displays, the user assigned CPU is also the boot processor, and so has been shown in the Boot processor line rather than the User assigned line. The boot processor is meaningful only when a vPar is running.
PAGE 5
vparresources(5) vparresources(5) needed to move any current work to another CPU. The OS cannot allow the boot processor to cease execution, so these states are disallowed for that CPU. The monitor may not boot a vPar whose configuration includes a CPU in either the Failed or MarkDC state. Nor will it silently modify a vPar’s configuration to reduce CPU count by the number of defective CPUs.
PAGE 6
vparresources(5) vparresources(5) Granularity Memory is normally assigned to virtual partitions in units called granules . Exceptions are described below. The granule values for CLM and ILM can be different. However, both are subject to the following rules: • MOST IMPORTANT, READ CAREFULLY. Granularity, the value of a granule specification, is not a resource. Resource assignments can be modified, even if some resource modifications require that a vPar be Down.
PAGE 7
vparresources(5) vparresources(5) Note: When memory is deleted from an active partition, the kernel makes the decision on which granules of memory is easier to delete. Hence, the granules that get deleted may not add upto the memory that was requested.
PAGE 8
vparresources(5) vparresources(5) when the vPar is Up. If size is not an integral multiple of the granularity of the specified memory type, vPars normally adjusts it upward to the next granule boundary. However, vPars will allow you to configure a sub-granular quantity of memory if doing so exhausts available memory. Consider a configuration with 4 GB granules and two granules of unassigned memory. Due to fragmentation, 2 GB of one granule are not available.
PAGE 9
vparresources(5) vparresources(5) allocation of that type of memory to the vPar, the warning is suppressed. Instead you will see the relevant error message. NOTE: Assignment of ranges that are not granule aligned is not supported. Hence this is not recommended. Here are some examples of memory range specifications. For simplicity, all examples show memory range addition, but operation is similar when deleting memory ranges.
PAGE 10
vparresources(5) vparresources(5) the vPar is Up. If the range is added as "floating" memory, it can be deleted even when the vPar is Up. NOTE: For online deletion of ranges, the base or floating attribute is not enforced. If the user specifies a floating range but does not specify the "floating" attribute, the deletion will still succeed. Irrespective of the attribute specified, online deletion of base ranges will always fail.
PAGE 11
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.
PAGE 12
vparresources(5) vparresources(5) Table I. Resource syntax summary Resource Form CPU cpu:path cpu::num cpu:::[min][:[max]] cell:cell_id:cpu::num (CLP) I/O io:h/w path[:attr1[,attr2]] Memory mem::size[:base|floating] (ILM) mem:::base:range[:base|floating] cell:cell_id:mem::size[:base|floating] (CLM) # times/command Multiple Once Once Once per cell_id Multiple Multiple Multiple Twice per cell_id The first field is always one of the (case-insensitive) strings cpu, io, mem, or cell.
PAGE 13
vparresources(5) vparresources(5) Table II.
PAGE 14
vparresources(5) • vparresources(5) Memory 1) -a mem::size[:base|floating] specifies that at least size MB of base or floating ILM must be available in the monitor. If size is not an integral multiple of the ILM granularity, it is first rounded up to the next granule boundary before testing for availability. By definition, this memory is of type ILM. 2) -a cell:cell_id:mem::size[:base|floating] specifies that at least size MB of base or floating memory on cell cell_id must be available in the monitor.
PAGE 15
vparresources(5) vparresources(5) or mem::size[:base|floating] specifications. However there is no such restriction if the target vPar is Up. Adding/deleting a range to/from an Up vPar increases/decreases the total memory assigned to that vPar. When you specify an explicit range of memory (whether adding or deleting), to a Down vPar, you do not change the total amount of memory assigned to the vPar.
PAGE 16
vparresources(5) vparresources(5) Table III. Detailed resource specifications Task: -a cell: cell_id :cpu::num Adds num CLPs from cell cell_id to the vPar’s configuration. cell_id: A positive integer or 0 num: A positive integer If the target vPar is in an alternate database file: o Total number of CPUs <= max Table III.a.
PAGE 17
vparresources(5) vparresources(5) Task: -a cpu:path Assigns a CPU resource at a specific path to the vPar’s configuration. A text string of the form returned by the ioscan command, such as "0/13" If the vPar is Down or in an alternate database, a non-CLP must have been previously specified. This CPU replaces the non-CLP. Table III.b.
PAGE 18
vparresources(5) vparresources(5) Task: -a cpu:::[min][:[max]] Specifies the minimum and maximum number of CPUs allowed for the vPar. This operation does not allocate any CPUs, but specifies the limits of other allocation tasks. Table III.d. Explanation Value Usage Restrictions Both min and max are optional. The default min is platform-dependent but is currently = 1. The default max is 32767 if creating a vPar in an alternate database.
PAGE 19
vparresources(5) vparresources(5) Task: -a io:path [:attr1 [,attr2 ]] Adds the I/O resource at path to the vPar. If attributes are specified, they are associated with the resource. If the vPar already owns the resource, any specified attributes are added to its configuration. Table III.e. Explanation Value Usage Restrictions Usage Guidelines This option only adds any specified attributes. The state of unspecified attributes is not changed.
PAGE 20
vparresources(5) vparresources(5) Task: -a cell:cell_id:mem::size[:base|floating] Specifies the increase, in megabytes rounded upward to the next CLM granule multiple, in the total amount of Cell Local Memory to be allocated to the vPar. This memory is taken from unspecified ranges of unassigned CLM on cell_id when the vPar boots. cell_id: A positive integer or 0 size: A positive 64-bit integer <= (0x100000000000 - CLM granularity) The target vPar can be Up or Down. Table III.f.
PAGE 21
vparresources(5) vparresources(5) Task: -a mem:::base:range[:base|floating] Specifies an explicit address space of memory starting at base bytes and extending for range megabytes. If the target vPar is in the live monitor database, both quantities are rounded upward as required to be aligned on a granule boundary. base: An unsigned 64-bit integer <= (0x1000000000000000 - appropriate granularity) range: A positive 64-bit integer <= (0x100000000000 - granularity) The target vPar can be Up or Down.
PAGE 22
vparresources(5) vparresources(5) Task: -m cpu::num Sets the total number of non-CLPs to num. A positive integer If the vPar is in an alternate database file: o num must be between min and max. Table III.i. Explanation Value Usage Restrictions In addition, if the vPar is in the live monitor database and num increases the total: o num active CPUs must exist in the hard partition. o They must be available (not assigned to any vPar). o iCAP must authorize their addition.
PAGE 23
vparresources(5) vparresources(5) Task: -m io:path [:attr1 [,attr2 ]] Changes the attributes of the resource to those specified in the option. Omitted attributes are removed from the attribute set. To retain an attribute, it must be specified. path: A text string of the form returned by the ioscan command, such as "0/0/6" Table III.l. Explanation Value Usage Restrictions Usage Guidelines attr: One or both of the case-insensitive attribute strings ALTBOOT, TAPE and BOOT.
PAGE 24
vparresources(5) vparresources(5) Task: -m mem::size[:base|floating] Specifies the total amount of ILM, in megabytes rounded upward to the next ILM granule multiple, to be allocated to the vPar. This memory is taken from unspecified ranges of unassigned ILM when the vPar boots. size: A positive 64-bit integer <= (0x100000000000 - ILM granularity) The target vPar can be Up or Down. Table III.m.
PAGE 25
vparresources(5) vparresources(5) Task: -m cell:cell_id:mem::size[:base|floating] Specifies total amount of base or floating Cell Local Memory, in megabytes rounded upward to the next CLM granule multiple, from cell cell_id to be allocated to the vPar. cell_id: A positive integer or 0 size: A positive 64-bit integer <= (0x100000000000 - CLM granularity) The target vPar can be Up or Down. Table III.n.
PAGE 26
vparresources(5) vparresources(5) Task: -d cell:cell_id :cpu::num Deletes num CLPs on cell cell_id from the vPar’s configuration. cell_id: A positive integer or 0 num: A positive integer If the target vPar is in an alternate database file: o Total number of CPUs >= min o num CPUs from cell_id must currently be assigned to the vPar. Table III.o. Explanation Values Usage Restrictions In addition, if the target vPar is in the live monitor database: o cell_id must exist in the configuration.
PAGE 27
vparresources(5) vparresources(5) Task: -d cpu::num Deletes num non-CLPs from the vPar’s total configuration. A positive integer The vPar must be assigned at least num non-CLP, non-user-specified CPUs. Table III.q. Explanation Value Usage Restrictions The new total number of CPUs >= min Table III.r.
PAGE 28
vparresources(5) vparresources(5) Task: -d cell:cell_id:mem::size[:base|floating] Specifies the decrease, in megabytes rounded upward to the next CLM granule multiple, in the total amount of base or floating Cell Local Memory to be allocated from cell cell_id to the vPar. cell_id: A positive integer or 0 size: A positive 64-bit integer <= (0x100000000000 - CLM granularity) The target vPar can be Up or Down. Table III.s.
PAGE 29
vparresources(5) vparresources(5) Task: -d mem:::base:range[:base|floating] De-assigns an explicit address space of memory starting at base bytes and extending for range megabytes. Both quantities are rounded upward as required to be aligned on a granule boundary. If rounding is required, the granularity used is that of the memory type (CLM or ILM) determined by the specified base.
PAGE 30
vparresources(5) vparresources(5) Table IV. Hardware Path Specifications Beginning with vPars A.02.02, the way to specify hardware paths has changed. This was done so that older vPars configuration databases remain compatible with additional hardware that is being supported. For example, given a path whose sequential digits are 4 0 1 0 0 0 0, it is not possible to determine 4/0/1/0/0.0.0 whether this path means a device at or a device at 4/0/1/0/0/0/0.0.0.0.0.0.0.
PAGE 31
vparresources(5) vparresources(5) vparmodify -p winona2 -m io:12.0.8.0.0.4.0.0.0.0.0.0.0:ALTBOOT. SEE ALSO ioscan(1M), parmgr(1M), parmodify(1M), vparadmin(1M), vparboot(1M), vparconfig(1M), vparcreate(1M), vpardump(1M), vparefiutil(1M), vparenv(1M), vparextract(1M), vparmodify(1M), vparreloc(1M), vparremove(1M), vparreset(1M), vparstatus(1M), vparutil(1M), icod(5), vpartition(5), vpmon(5).
PAGE 32
(Notes) A (Notes) vA 32 Hewlett-Packard Company −1− HP-UX 11i Version 3: September 2010