vparresources.5 (2010 09)

v
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.
As with CPUs, once a specific memory address range is assigned to a vPar, it remains assigned to the
vPar, even when that vPar is not running. Memory allocated to the vPar, but not specified explicitly, is
assigned by the monitor when the vPar is booted. As with CPUs, monitor-assigned memory ranges may
be different each time the vPar is booted.
The
vparstatus command displays the monitor-assigned CLM and ILM memory ranges of each run-
ning vPar when either the
-v (detailed display) or the -M (machine readable) option is used.
Assigning Memory Ranges - Alternate Database or Monitor Not Running
Since vPars cannot tell if a specified memory range would be ILM or CLM, and the two granularities can
be different, there is no way that vPars can adjust a non-granular range specification.
I/O
General
I/O resources are all resources other than CPUs and memory. Disks, LAN cards and terminals all qualify
as I/O devices. vPars manages them as non-shareable resources. A minimally-configured vPar requires
one CPU, sufficient memory, and a disk device to boot from. In addition, if a LAN card is not configured,
the only terminal access to the vPar is through the serially-connected console.
The first three hierarchical levels of I/O resource specification are the cell, the System Bus Adapter
(SBA), and the Logical Bus Adapter (LBA). (On non-cellular systems, the first of these is not present.)
LBAs and lower are assigned to a specific vPar. LBAs and devices below that level cannot be shared with
any other vPar. For example, cell 1 might include the following SBAs: 1/0 and 1/2. LBAs attached to
these SBAs can be assigned to different virtual partitions. With this configuration, 1/0/0 (or any lower
path element can be assigned to vPar A, 1/0/4 can be assigned to vPar B, 1/2/0 can be assigned to vPar C.
This means that the disk at 1/0/0/3/0.6.0 is assigned to vPar A, because it is attached to LBA 1/0/0. A
LAN card at 1/0/0/1/0 cannot be assigned to vPar B because it is attached to LBA 0 which is assigned to
vPar A.
I/O resources can only be assigned to or deleted from a vPar when the vPar is
Down (not running).
Attributes
A vPar requires a bootable device. Usually this is a disk. The BOOT and ALTBOOT attributes allow you
to specify the device vPars should use when booting your vPar. vPars will try to boot the vPar from this
device unless overridden with the
-B option of the vparboot or MON>vparload command. vPars
does not verify that a device with the [ALT]BOOT attribute is actually a bootable device. If a vPar has a
non-bootable boot device assigned to it, the vPar will not boot when requested.
You specify an attribute using an optional additional field on an I/O resource specification. For example:
-a io:1/0/0/3/0.6.0 adds the specified device to your vPar, while -a
io:1/0/0/3/0.6.0:BOOT adds both the device and the BOOT attribute.
Attributes can be added or deleted independently of the device itself. You could specify the first example
above. Later you could specify the second example. The only change would be to add the
BOOT attribute
to the existing I/O configuration.
Deletion is similar. If you specify
-d io:1/0/0/3/0.6.0:BOOT you are only deleting the
BOOT
attribute. The underlying I/O resource remains assigned. If you specify -d io:1/0/0/3/0.6.0 the
entire resource is deleted.
Finally, if you add an attribute to a resource, it is silently deleted from any existing resource it may be
attached to.
Legacy and Agile (Lunpath) Hardware Paths
HP-UX Release 11i, Version 3 introduced additional types of hardware paths to I/O devices: lunpath
hardware paths and LUN hardware paths. The original format of hardware path is now referred to as a
legacy hardware path.
Support for agile hardware paths has been added to Virtual Partitions in the A.05.03 release. Agile
hardware paths can now be used to specify I/O devices when using the vparcreate and vparmodify com-
mands. For example:
-a io:1/0/4/1/0.0x500805f3000ff771.0x400e000000000000 adds
10 Hewlett-Packard Company − 10 − HP-UX 11i Version 3: September 2010