vparcreate.1m (2010 09)

v
vparcreate(1M) vparcreate(1M)
syntactically correct if specified. If it is specified on an Itanium-based platform with
the value y, the specified size is also written to system firmware storage. This setting
does not take effect until the underlying hard partition is rebooted. update_fw should
only be specified with a value of
y if you intend to use the newly created database in
the current hard partition.
If the
-g option is omitted when creating a new database, vPars chooses the default
granularity, 128 megabytes, for both CLM and ILM, and does not update firmware on
an Itanium-based platform.
-S static_attr Specifies the static vPar attribute. static_attr can have the following (case-insensitive)
values:
static sets the static attribute.
dynamic resets the static attribute.
vPars with the
static attribute do not support any dynamic resource migration, nor
can resource attributes be added/deleted/modified with
vparmodify. This attribute
becomes effective after any initial resource allocation, so it is possible to assign
resources when creating a new virtual partition and still specify that the resulting vPar
be static.
If the
-S option is omitted, the attribute defaults to dynamic.
-b kernel_path Specifies the absolute path to a bootable kernel for the vPar. For example, if a
non-partitioned system start string at the ISL prompt is:
ISL> hpux -iS /stand/vmunix
the kernel_path is the /stand/vmunix
portion of this string. If this option is omit-
ted, the virtual partition is created with a default kernel path of
/stand/vmunix
.
-o boot_opts Specifies the command-line string, except for the kernel path, applied when the vPar is
booted. For example, if a non-partitioned system start string at the ISL prompt is:
ISL> hpux -iS /stand/vmunix
the boot_opts string is the -iS portion of this string. Note that if the string includes a
space, the string must be quoted.
Refer to "Monitor and Shell Commands" in Installing and Managing HP-UX Virtual
Partitions for a full list of supported boot option strings.
The default is the empty string.
-a rsrc Adds resources to a virtual partition. rsrc is a hardware resource specification, as
described in detail in the vparresources(5) manpage. You should refer to the section
"CPUs and Instant CAPacity (iCAP)" in that manpage when adding CPU resources.
The iCAP product will not allow CPU activation in excess of that shown by iCAP’s
Intended Active number. The underlying nPartition is said to be compliant .
vpar-
create fails if you attempt to create a vPar in the loaded monitor database such that
the total processors assigned to all vPars would exceed Intended Active .
When creating a new vPar in an alternate database, iCAP displays a warning if the
total number of processors in the database exceeds the current Intended Active number
of the nPartition. The operation is allowed, but the database will be non-compliant if
loaded by the monitor in this nPartition. If that happens, iCAP will not allow any
vPars to boot.
Refer to the Instant CAPacity (iCAP) User’s Guide available at
http://docs.hp.com, and to the icod (5) manpage for more information.
A summary of resource syntax forms is shown in Table 1 below. Multiple
-a rsrc
specifications in the same command are allowed, but some syntax forms are only
allowed once. This in indicated in Table 1. In all cases, resources in multiple
specifications must not repeat or conflict with each other.
HP-UX 11i Version 3: September 2010 − 3 − Hewlett-Packard Company 3