vparcreate.1m (2010 09)

v
vparcreate(1M) vparcreate(1M)
partitions. Refer to setboot (1M) for details.
nosearch Clears the autosearch attribute.
On hard partitioned systems with vPars the boot action corresponds to the autoboot
and autosearch flags in the following manner:
AutoBoot AutoSearch Boot Action
Halt the vPar for manual boot.off off
Attempt the primary path; on failure halt the vPar.on off
Attempt the primary path; on failure try the alter-
nate path.
on on
Skip the primary path and try the alternate path.
If the alternate path is not configured to boot or the
boot fails then halt the vPar.
off on
If the Instant CAPacity (iCAP) product has detected that the total of CPUs assigned to
all vPars exceeds the amount indicated by iCAP’s Intended Active number, it prevents
any vPar from rebooting, regardless of the setting of this attribute. The
vparboot
command is also disabled. Refer to the Instant CAPacity (iCAP) User’s Guide available
at
http://docs.hp.com
, and to the icod (5) manpage for more information.
If the
-B option is omitted, the attributes default to auto and nosearch.
-D db_file Create the vPar in the database contained in db_file.Ifdb_file does not exist, it is
created by this command. This option should be used when creating a new vPar data-
base.
The monitor need not be running.
Although db_file can reside in any path when accessed as an alternate database, it
must be placed in the
/stand directory before it can be loaded by the monitor as its
live database.
On Itanium-based platforms, there must also be a soft link between db_file and an
identically named file in the
/stand/boot.sys/stand
directory. The link is not
required on PA-RISC platforms. The command creates this link for you when you
create db_file with the absolute path prefix of
/stand. If you create db_file with a
different path or in a different directory and later move it to
/stand
,orifyoucreate
db_file on one system but copy it to another for use, you must manually create the link.
If the
-D option is omitted and the monitor is running, the vPar is created in the
monitor’s live database. If the monitor is not running, the vPar is created in the
default database file /stand/vpdb, which is itself created if it does not exist.
-g memtype:size[:update_fw]
Specifies the granularity of Cell Local Memory (CLM) or InterLeaved Memory (ILM)
requests for the database. All CLM or ILM memory specifications must be an integral
multiple of the corresponding granularity. This option is only valid when creating the
first vPar in a database.
Cell Local Memory, as its name implies, refers to memory address ranges on a specific
cell. InterLeaved Memory refers to memory address ranges whose adjacent addresses
are on different cells. The size of each memtype may be specified independently. Once
specified, each value applies to all vPars in a given database.
memtype is one of the two case-insensitive strings:
clm Cell Local Memory
ilm InterLeaved Memory
size is the granularity of memtype in megabytes.
size must be at least 64 megabytes. Higher values must be an integral power of 2
megabytes (128MB, 256MB, 512MB, etc.).
The optional update_fw is a case-insensitive
y or n. The default is n. It is applicable
only to Itanium-based platforms. It is ignored on PA-RISC platforms, but must be
2 Hewlett-Packard Company − 2 − HP-UX 11i Version 3: September 2010