|
|
vPar Hardware Paths
|
|
vparmodify(1M) vparmodify(1M) NAME
vparmodify - rename a virtual partition or modify the attributes of a virtual partition SYNOPSIS
vp_name boot_attr] sequence_id] db_file] static_attr] kernel_path] boot_opts] new_vp_name] rsrc]... rsrc]... rsrc]... DESCRIPTION
The command modifies attributes and resources of the specified virtual partition (vPar). The command can also rename the virtual parti- tion. vp_name is a symbolic name for an existing virtual partition and must be used in all references to it. cannot create a virtual par- tition. Use the command for that purpose. Some CPU resources have special requirements when being added to a virtual partition. These special CPU resource requirements are described following Table 1. Older versions of the and commands allowed specification of IO resources using the legacy hardware path only (see intro(7)). Starting with the A.05.03 version of the Virtual Partitions product, agile (lunpath) hardware paths are also supported. This functionality means that you can now create a virtual partition with legacy mode disabled (see insf(1M) and rmsf(1M)), but only if all virtual partitions have been updated to A.05.03 or later. Note that the mixing of legacy and agile hardware paths within one vPar is not recommended. This command cannot detect when a legacy hard- ware path and an agile hardware path identify the same device. Options o If the option is specified, vp_name in db_file is modified; otherwise vp_name in the virtual partition monitor database is modified. If db_file specifies the file currently loaded into the monitor, vp_name in the monitor database is modified. If the option is not speci- fied and the monitor is not running, vp_name is modified in the default database file if both exist. Otherwise the command fails. o If the attribute has been configured in vp_name, none of its resources may be added, modified, or deleted. Attributes (all options except and may be modified. Refer to the option description. o Only the and/or options may be specified more than once in a command. o If any of the following options are specified: or the virtual partition to be modified must be in the or state. Refer to the vparsta- tus(1M) manpage for a complete list of vPar states and their definitions. o Resources allocated with the option must be available, that is, not already assigned to a virtual partition, and they must not exceed the overall limits of the resources. Addition of CPU resources must be authorized by the Instant CAPacity (iCAP) product. o Resources to be modified or deleted must be currently assigned to vp_name. Violation of any condition is a command error. recognizes the following command line options and arguments. The options are processed from left to right. Specifies the symbolic name of the existing virtual partition which is to be modified. Required. Specifies the autoboot and autosearch attribute of the virtual partition. boot_attr can have the following case-insensitive values: Sets the autoboot attribute. If the autoboot attribute is set to the vPar is rebooted following a successful command or when the monitor is first loaded, if appropriate monitor options have been specified. Clears the autoboot and autosearch attributes. If the attribute is set to the vPar halts after a and does not boot when the monitor is loaded. It must then be booted manually with the command. Sets the autosearch attribute. If the autosearch attribute is set to then the combination of autoboot and autosearch decides the boot action to be taken. The interpretation of autoboot and autosearch has changed for systems that support hardware par- titions. Refer to setboot(1M) for details. 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 ------------------------------------------------------- off off Halt the virtual partition for manual boot. on off Attempt the primary path; on failure halt the virtual par- tition. on on Attempt the primary path; on failure try the alternate path. off on Skip the primary path and try the alternate path. If the alternate path is not config- ured to boot or the boot fails then halt the virtual parti- tion. ------------------------------------------------------- If the 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 command is also disabled. Refer to the available at and to the icod(5) manpage for more information. Boot attributes may be changed while vp_name is running. If the option is omitted, the attributes are not changed. Cancel a pending Resource OL* operation. sequence_id specifies the Resource OL* operation to cancel. Information about the unique sequence_id associated with dif- ferent OL* operation can be obtained using the command. See vparstatus(1M). Apply changes to the vp_name contained in db_file. The virtual partition monitor need not be running. If it is, and db_file is its database, changes are made to the live database. If db_file is a different database, the monitor is not notified of the modifica- tion. Although db_file can reside in any path when accessed as an alternate database, it must be placed in the directory before it can be loaded by the virtual partition monitor as its live database. If the option is omitted, either the virtual partition monitor must be running, or the default vPar database file, must exist and contain a configured vp_name. If the monitor is running, changes are applied to vp_name in the monitor's data- base. Specifies the static virtual partition attribute. static_attr can have the following values: sets the static attribute. resets the static attribute. The static/dynamic attribute may be changed while vp_name is running. If the option is omitted, the attribute is not changed. No hardware resource changes can be made to a static virtual partition, that is, the and options are not allowed. This restriction applies to all virtual partitions, whether in an alternate database file, or in the monitor's database. Since command line options are processed left-to-right, you can modify resources in a static partition by specifying on the command line before any resource options, then specifying after all resource options to prevent further resource modi- fications. Specifies the absolute path to a bootable kernel for the partition. If the option is omitted, the kernel_path is not changed. The kernel path may be changed while vp_name is running. Specifies the command-line string, except for the kernel path, applied when the virtual partition is booted. For example, if a non-partitioned system start string at the ISL prompt is: the boot_opts string is the portion of this string. Note that if the string includes a space, the string must be quoted. Refer to "Monitor and Shell Commands" in for a full list of supported boot option strings. The boot options may be changed while vp_name is running. If the option is omitted, boot_opts is not changed. Specifies a new name for the virtual partition being modified, that is, after all modifications are successfully applied to vp_name, it is renamed to new_vp_name, assuming no virtual partition with that name already exists in the monitor database, the specified alternate database file, or the default database file The name can consist of alpha-numeric characters the underbar character and period The maximum length of the name is 239 characters. The vPar name may be changed while vp_name is running. If the option is omitted, vp_name is not changed. adds resources to a virtual partition. deletes resources from a virtual partition. modifies existing resources in 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 fails if you attempt to add one or more processors such that the total processors assigned to all vPars would exceed Intended Active. Refer to the available at and to the icod(5) manpage for more information. A summary of resource syntax forms is shown in Table 1. Multiple resource specifications in the same command are allowed, but some syntax forms are restricted to specific options, and some are only allowed once. Both are indicated in Table 1. In any case, resources in multiple specifications must not repeat or conflict with each other. Table 1. Resource syntax summary +---------+------------------------------+------------+------------------+ |Resource | Forms | Options | # times/command | +---------+------------------------------+------------+------------------+ |CPU | cpu:path | -a, -d | Multiple | | | cpu::num | -a, -m, -d | Once | | | cpu:::[min]:[max] | -m | Once | | | cell:cell_id:cpu::num (CLP) | -a, -m, -d | Once per cell_id | +---------+------------------------------+------------+------------------+ |I/O | io:path[:attr1[,attr2]] | -a, -m, -d | Multiple | +---------+------------------------------+------------+------------------+ |Memory | mem::size (ILM) | -a, -m, -d | Once | | | mem:::base:range | -a, -d | Multiple | | | cell:cell_id:mem::size (CLM) | -a, -m, -d | Once per cell_id | +---------+------------------------------+------------+------------------+ Cell Local Memory (CLM), as its name implies, refers to memory address ranges on a specific cell. InterLeaved Memory (ILM) refers to mem- ory address ranges whose adjacent addresses are on different cells. size must be in units of granularity for the specified memory type. The command shows memory granularities. Refer to the vparstatus(1M) manpage. Online memory addition/deletion is not supported for the default (base) memory type. In order to delete floating memory (ILM or CLM) the keyword "floating", "float" or "f" should be explicitly specified on the command line. Refer to the vparresources(5) man page for syntax details. On PA-RISC platforms, a vPar whose memory consists entirely of CLM will not boot. The vPar needs ILM in the first 2 GB of memory to load and launch its kernel. You should always retain sufficient ILM in your vPar to accommodate this requirement. Refer to the section "Mem- ory" and the subsection "Recommendations for ILM and CLM granularity specifications" in the vparresources(5) man page for details. A vp_name in the monitor database must be in the state to add or delete resources, with one exception: CPU resources can be added to or deleted from a running virtual partition. This restriction may be relaxed for other types of resource management in a future release. Certain tasks can affect the outcome of others. To avoid errors, see the detailed description of the dependencies in the vparresources(5) manpage. Dynamically increasing or decreasing the number of CPUs in a running virtual partition results in an asynchronous request to the OS. The OS requires an indeterminate time to complete the operation, based on overall system load and (for CPU deletion) the time required to migrate all threads on that CPU on to one or more of the remaining CPUs. During this time, the CPU is said to be undergoing migration into or out of the vPar. The CPU is assigned to its vPar throughout the migration process. For migration out, the CPU is not available for assignment to another vPar until the migration has completed. The command shows migrating CPUs. Refer to the vparstatus(1M) manpage. SECURITY RESTRICTIONS
This command is restricted to processes owned by superuser. When virtual partition flexible administrative capability is enabled, only a Designated-Admin vPar can rename, modify resources and attributes on other virtual partitions. RETURN VALUE
The command exits with one of the following values: Successful completion. One or more error conditions occurred. A warning condition occurred. EXAMPLES
Change the name of the virtual partition called to Turn on the autosearch attribute for the virtual partition Turn off the autoboot and autosearch attributes for the virtual partition Add two processors to the virtual partition in alternate database file Add two processors to the virtual partition in the running vPar monitor database: Add two cell-local processors from cell 1 to the virtual partition Delete 1 gigabyte of floating cell-local memory (CLM) on cell 0 from the virtual partition ERRORS
displays error messages on standard error for any of the following conditions: An invalid option is specified. An invalid value is specified for an option or a value is omitted. The specified db_file does not exist, cannot be accessed, or has been corrupted. vp_name does not exist in the specified db_file or in the monitor database. new_vp_name already exists in the monitor database or specified db_file. vp_name is static and you have attempted to change a resource. One or more options other than is specified more than once. For the or option, an unavailable resource (allocated to another virtual partition or exceeding the available resource limit) is specified. For the or option, the specified resource is not presently assigned to vp_name. The command and the virtual partition monitor are at different revision levels. When the virtual partition flexible administrative capability is enabled and the local virtual partition is not a Designated-Admin vPar. The state of the modified vPar following an error depends on the following factors: o If the error is detected during syntax and semantic checks of the command line, or if CPU addition is not authorized by iCAP, the vPar is not changed. o If the error is detected while actually modifying the vPar, you are modifying an alternate database, the vPar is not changed. This is because changes are not committed until the end of the command. o If the error is detected while modifying the vPar, you are modifying the database currently loaded into the monitor, then any changes made to the point of the error (working left-to-right on the command line) will remain. This is because changes to the live database are made incrementally, as they are requested. AUTHOR
was developed by the Hewlett-Packard Company. SEE ALSO
insf(1M), rmsf(1M), vparadmin(1M), vparboot(1M), vparconfig(1M), vparcreate(1M), vpardump(1M), vparefiutil(1M), vparenv(1M), vparex- tract(1M), vparreloc(1M), vparremove(1M), vparreset(1M), vparstatus(1M), vparutil(1M), icod(5), vparresources(5), vpartition(5), vpmon(5), intro(7). vparmodify(1M)
