| The commands for working with Virtual Partitions appear in every chapter in this book. Many examples are provided in the chapters. In addition, the Quick Reference Tear Out card has on it summaries and examples of all of the commands. There is, however, nothing like the command detail that appears in the man pages for a command. The man pages for Virtual Partitions commands are well written and thorough. This appendix consists of the manual pages for Virtual Partitions commands only. The following is a list of the commands: vparboot - Boots (starts) a virtual partition. vparcreate - Creates a new virtual partition. vparmodify - Modifies an existing virtual partition. vparremove - Removes (deletes) an existing virtual partition. vparreset - Sends a TOC or hard reset to a virtual partition. vparresources - Provides description of Virtual Partitions and their resources. vparstatus - Displays virtual partition and available resources information. vpartition - Displays information about the vPars Command Line Interface. vparutil - Works with SCSI information of disks in vPar. vparboot -  Boots (starts) a virtual partition. vparboot(1M) vparboot(1M) NAME vparboot - boot a virtual partition SYNOPSIS vparboot -p vp_name [-b kernel_path] [-o boot_opts] [-B boot_addr] vparboot -p vp_name -I ignite_kernel DESCRIPTION The vparboot command causes the virtual partition monitor to boot the specified virtual partition. The monitor must be running. The virtual partition must exist in the monitor configuration and be in the Down state. For example, not running. For this reason, it is not possible to boot the current partition using this command. The partition in which the command is executing is called the current partition. Only a superuser can execute the vparboot command. Options vparboot recognizes the following command line options and arguments: -p vp_name Specifies the unique name of the virtual partition which is to be booted. The virtual partition must exist in the monitor's database, must be in the Down state, and must have a configured boot device. Required. -b kernel_path Specifies the absolute path to a bootable kernel for the virtual partition. 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 omitted, the value is taken from any -b kernel_path specified during virtual partition creation or its most recent modification, or /stand/vmunix if -b kernel_path has never been specified. -o boot_opts Specifies the command-line options applied when the virtual partition 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 in this case will be -iS. Note that if any whitespace is included in the string, the string must be quoted. Refer to the virtual partitions administration guide and the chapter titled "Monitor and Shell Commands" for a full list of supported boot option strings. If the -o option is omitted, the value is taken from any -o boot_opts specified during virtual partition creation or its most recent modification, or the empty string if -o boot_opts has never been specified. -B boot_addr Specifies the device from which the virtual partition kernel image is read. It must be one of the following three forms: bo[ot] | pri[mary] (case-insensitive). This is the default if the -B option is omitted. vparboot attempts to boot vp_name from the device previously configured with the BOOT attribute. It is an error if no device has been so configured. alt[ernate|boot] (case-insensitive). vparboot attempts to boot vp_name from the device previously configured with the ALTBOOT attribute. It is an error if no device has been so configured. Boot From Hardware Path: Any other string is assumed to be the hardware path (for example, 10/6.0) to the desired boot device. vparboot does not check any part of such a specification. If it is not a proper path, the path does not exist, the virtual partition does not own the device at that path, or there is no bootable device at that path, the command either fails with an error, or the boot attempt fails with no error indication. -I ignite_kernel Specifies a path to a cold-install kernel such as /opt/ignite/boot/WINSTALL. This form of the command is used to cold-install an instance of HP-UX on a virtual partition. Most often, this is done on a newly-created virtual partition, one that has a completely unwritten disk. However, it can be used to cold-install HP-UX over an existing instance. ignite_kernel can reside either on the current virtual partition (the one on which vparboot is run) or on any other networked system or virtual partition accessible from that partition. The syntax for ignite_kernel is: [Server name or IP addr,]cold-install_kernel If cold-install_kernel begins with a slash, "/", you are specifying an absolute path and vparboot looks for it at that location. If cold- install_kernel does not begin with "/", the default path /opt/ignite/boot/ is prepended to cold-install_kernel. If the Server name or IP address, is not specified, vparboot loads the cold-install kernel from the filespace of the current virtual partition. Otherwise the command loads it from the filespace of the specified server. The comma is a required part of the server name syntax. RETURN VALUE The vparboot command exits with one of the following values: 0 Successful completion. 1 One or more error conditions occurred. EXAMPLES Boot the virtual partition called Oslo vparboot -p Oslo Boot the virtual partition Bergen specifying an alternate kernel vparboot -p Bergen -b /stand/vmunix_debug Cold-install the virtual partition Trondheim from a file on a remote server vparboot -p Trondheim -I mysys.myserver.mydomain.com,/mypath/myinst Cold-install the virtual partition Sandefjord from a file at the default path /opt/ignite/boot on the current virtual partition vparboot -p Sandefjord -I WINSTALL ERRORS vparboot displays error messages on stderr for any of the following conditions: vp_name does not exist in the monitor. vp_name is in some state other than Down, and so cannot be booted. Use the vparreset(1M) command instead. An error occurs while trying to access an Ignite server or cold- install file. You have specified the BOOT or ALTBOOT device, but the corresponding device has not been configured in vp_name. NOTE: If the boot device has not been configured properly the vparboot command will complete without error, but the virtual partition will not boot. Two possible reasons for this could be: + The BOOT or ALTBOOT attribute was assigned to a device other than a disc or tape. + The file at the default or configured kernel path does not exist or is not a bootable image. AUTHOR vparboot was developed by the Hewlett-Packard Company. SEE ALSO vparcreate(1M), vparmodify(1M), vparremove(1M), vparreset(1M), vparstatus(1M), vparresources(5), vpartition(5). vparcreate -  Creates a new virtual partition. vparcreate(1M) vparcreate(1M) NAME vparcreate - create a virtual partition SYNOPSIS vparcreate -p vp_name [-B boot_attr] [-D db_file] [-S static_attr] [-b kernel_path] [-o boot_opts] [-a rsrc]... DESCRIPTION The vparcreate command creates a new virtual partition (vPar) using the specified hardware resources. vp_name is a symbolic name for the virtual partition and must be used in all references to it. If the -D option is specified, the virtual partition is created in db_file. Otherwise it is created in the virtual partition monitor database. In either case, a virtual partition named vp_name must not already exist in the database.Any error terminates the command without creating a virtual partition. Only a superuser can execute the vparcreate command. Options No option except -a (add resource) may be specified more than once. Resources allocated with the -a option must be available, that is, not already allocated to a virtual partition, nor exceeding the overall limits of the resources.Resources assigned with multiple -a options must not conflict. Violation of any condition is a command error. The vparcreate command recognizes the following command line options and arguments: -p vp_name Specifies the symbolic name of the virtual partition. The name can consist of alpha-numeric characters A-Z, a-z, 0-9, the underbar character (_), and the period (.). The maximum length of the name is 239 characters. Required. -B boot_attr Specifies the autoboot attribute of the virtual partition. boot_attr can have the following (case-insensitive) values: auto sets the autoboot attribute. manual clears the autoboot attribute. If the autoboot attribute is set to auto, the virtual partition is rebooted after a successful vparreset command or when the virtual partition monitor is first loaded, if appropriate monitor options have been specified. If the attribute is set to manual, the virtual partition halts after a vparreset, and does not boot when the monitor is loaded. It must then be booted manually with the vparboot command. If the -B option is omitted, the attribute defaults to auto. -D db_file Create the virtual partition in the virtual partition database contained in db_file. If db_file does not exist, it is created by this command. This option should be used when creating a new virtual partition database. The virtual partition monitor need not be running. If it is, it is not notified of the new virtual partition. 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 virtual partition monitor as its live database. If the -D option is omitted and the virtual partition monitor is running, the virtual partition is created in the virtual partition monitor's live database. If the monitor is not running, the virtual partition is created in the default database file /stand/vpdb, which is itself created if it does not exist. -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. virtual partitions set to static 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 virtual partition 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 partition. 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 omitted, 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 virtual partition 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 any whitespace, the string must be quoted. Refer to the virtual partitions administration guide and the chapter titled "Monitor and Shell Commands" 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. 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. Table 1. Resource syntax summary ________________________________________________________ |Resource | Forms | # times/command | |________ _|_________________________|_________________| |CPU | cpu:path | Multiple | | | cpu::num | Once | | | cpu:::[min][:[max]] | Once | |__________|_________________________|_________________| |I/O | io:path[:attr1[,attr2]] | Multiple | |__________|_________________________|_________________| |Memory | mem::size | Once | | | mem:::base:range | Multiple | |__________|_________________________|_________________| Certain tasks can affect the outcome of others. To avoid errors, see the detailed description of the dependencies in the vparresources(5) manpage. RETURN VALUE The vparcreate command exits with one of the following values: 0 Successful completion. 1 One or more error conditions occurred. EXAMPLES Create the virtual partition called Oslo in the virtual partition monitor database, but do not assign any resources: vparcreate -p Oslo Create the virtual partition Bergen in the virtual partition monitor database, setting the autoboot attribute and specifying five processors, two of which are bound, 2 Gb of physical memory, and a boot disk: vparcreate -p Bergen -a cpu::5 -a cpu:::2:6 \ -a mem::2048 -a io:1/0/2/0.6.0:boot -B auto Since the -b option was not specified, the default kernel path /stand/vmunix will be used at boot time. ERRORS vparcreate displays error messages on stderr for any of the following conditions: An invalid option is specified. An invalid value is specified for an option or a value is omitted. vp_name already exists in the monitor database or specified db_file. Use the vparmodify command instead. One or more options other than -a has been specified more than once or the same resource was allocated more than once. An unavailable resource (allocated to another virtual partition or exceeding the available resource limit) was specified. A value was omitted for an argument that requires one, or a value was supplied for an argument which does not take one. AUTHOR vparcreate was developed by the Hewlett-Packard Company. SEE ALSO vparboot(1M), vparmodify(1M), vparremove(1M), vparreset(1M), vparstatus(1M), vparresources(5), vpartition(5). vparmodify -  Modifies an existing virtual partition. vparmodify(1M) vparmodify(1M) NAME vparmodify - modify the attributes of a virtual partition SYNOPSIS vparmodify -p vp_name [-B boot_attr] [-D db_file] [-S static_attr] [-b kernel_path] [-o boot_opts] [-P new_vp_name] [-a rsrc]... [-m rsrc]... [-d rsrc]... DESCRIPTION The vparmodify command modifies attributes and resources of the specified virtual partition. The command can also rename the virtual partition. vp_name is a symbolic name for an existing virtual partition and must be used in all references to it. vparmodify cannot create a virtual partition. Use the vparcreate command for that purpose. Only a superuser can execute the vparmodify command. If the -D option is specified, vp_name in db_file is modified; otherwise vp_name in the virtual partition monitor database is modified. If the static attribute has been configured in vp_name, none of its resources may be added, modified, or deleted. Attributes (all options except -a, -m, and -d) may be modified. Refer to the -S option description. Options Only the -S, -a, -m, and/or -d options may be specified more than once in a command. Resources allocated with the -a option must be available, that is, not already allocated to a virtual partition. They must also not exceed the overall limits of the resources. Resources to be modified (-m) or deleted (-d) must be owned by vp_name.Violation of any condition is a command error. vparmodify recognizes the following command line options and arguments. The options are processed from left to right. -p vp_name Specifies the symbolic name of the existing virtual partition which is to be modified. Required. -B boot_attr Specifies the autoboot attribute of the virtual partition. boot_attr can have the following case-insensitive values: auto sets the autoboot attribute. manual clears the autoboot attribute. If the autoboot attribute is set to auto, the virtual partition is rebooted after a successful vparreset command or when the virtual partition monitor is first loaded, if appropriate monitor options have been specified. If the attribute is set to manual, the virtual partition halts after a vparreset and does not boot when the monitor is loaded. It must then be booted manually with the vparboot command. If the -B option is omitted, the attribute is not changed. -D db_file Apply changes to the vp_name contained in db_file. The virtual partition monitor need not be running. If it is, it is not notified of the modification. 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 virtual partition monitor as its live database. If the -D option is omitted, the virtual partition monitor must be running. Changes are applied to vp_name in the monitor's database. A vp_name in the monitor database must be in the Down state, with one exception: Unbound 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. -S static_attr Specifies the static virtual partition attribute. static_attr can have the following values: static sets the static attribute. dynamic resets the static attribute. If the -S option is omitted, the attribute is not changed. No hardware resource changes can be made to a static virtual partition, that is, the -a, -m, and -d 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 -S dynamic on the command line before any resource options, then specifying -S static after all resource options to prevent further resource modifications. -b kernel_path Specifies the absolute path to a bootable kernel for the partition. If the option is omitted, the kernel_path is not changed. -o boot_opts 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: ISL> hpux -iS /stand/vmunix the boot_opts string is the -iS portion of this string. Note that if the string includes any whitespace, the string must be quoted. Refer to the virtual partitions administration guide and the chapter titled "Monitor and Shell Commands" for a full list of supported boot option strings. If the -o option is omitted, the boot_opts is not changed. -P new_vp_name Specifies the 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 or specified alternate database file. The name can consist of alpha-numeric characters A-Z, a-z, 0-9, the underbar character (_), and period (.). The maximum length of the name is 239 characters. -a rsrc -a adds resources to a virtual partition. -d rsrc -d deletes resources from a virtual partition. -m rsrc -m modifies existing resources in a virtual partition. rsrc is a hardware resource specification, as described in detail in the vparresources(5) manpage. A summary of resource syntax forms is shown in Table 1 below. 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 | |_________|_________________________|____________|_________________| |I/O | io:path[:attr1[,attr2]] | -a, -m, -d | Multiple | |_________|_________________________|____________|_________________| |Memory | mem::size | -a, -m, -d | Once | | | mem:::base:range | -a, -d | Multiple | |_________|_________________________|____________|_________________| Certain tasks can affect the outcome of others. To avoid errors, see the detailed description of the dependencies in the vparresources(5) manpage. RETURN VALUE The vparmodify command exits with one of the following values: 0 Successful completion. 1 One or more error conditions occurred. EXAMPLES Change the name of the virtual partition called Oslo to Bergen vparmodify -p Oslo -P Bergen Turn off the autoboot attribute for the virtual partition Oslo vparmodify -p Oslo -B manual Add two processors to the virtual partition Bergen in alternate database file /stand/Norway vparmodify -p Bergen -D /stand/Norway -a cpu::2 ERRORS vparmodify displays error messages on stderr 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 -S, -a, -m, -d is specified more than once. For the -a or -m option, an unavailable resource (allocated to another virtual partition or exceeding the available resource limit) is specified. For the -m or -d option, the specified resource is not presently assigned to vp_name. The state of the modified vPar following an error depends on the following factors: + If the error is detected during syntax and semantic checks of the command line, the vPar is not changed. + If the error is detected while actually modifying the vPar, AND you are modifying an alternate database, the vPar is not changed. This is because changes are not committed until the end of the command. + If the error is detected while modifying the vPar, AND 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 vparmodify was developed by the Hewlett-Packard Company. SEE ALSO vparboot(1M), vparcreate(1M), vparremove(1M), vparreset(1M), vparstatus(1M), vparresources(5), vpartition(5). vparremove -  Removes (deletes) an existing virtual partition. vparremove(1M) vparremove(1M) NAME vparremove - remove a virtual partition SYNOPSIS vparremove -p vp_name [-D db_file] [-f] DESCRIPTION The vparremove command deletes a virtual partition previously created using the vparcreate(1M) command. All resources associated with the virtual partition are made available for allocation to other partitions. Only a superuser can execute the vparremove command. Unintentional use of this command has serious consequences; therefore the user is prompted to confirm the operation unless the -f (force) option is specified. Options vparremove recognizes the following command line options and arguments: -p vp_name Specifies the unique name of the virtual partition which is to be removed. Required. -D db_file Removes a virtual partition from the partition database contained in db_file. If this option is omitted, the virtual partition is removed from the monitor's database. In this case, the partition must be in the Down state to be removed. Thus it is an error to try to remove the current virtual partition, the one in which the command is executing. -f Specifies the force option. Omits the confirmation dialog before removing the virtual partition. This option is intended for use by scripts and other non-interactive applications. RETURN VALUE The vparremove command exits with one of the following values: 0 Successful completion. 1 One or more error conditions occurred. EXAMPLES Destroy the virtual partition Oslo in the partition database currently running in the monitor: vparremove -p Oslo Remove virtual partition Oslo? [n]: y Destroy the virtual partition Oslo in the partition database currently running in the monitor using the force option: vparremove -f -p Oslo Delete partition Bergen in partition database file Norway vparremove -f -D /stand/Norway -p Bergen ERRORS vparremove displays error messages on stderr for any of the following conditions: + db_file does not exist, cannot be accessed, is not a virtual partition database file, or is corrupt. + vp_name does not exist in the monitor's database or in db_file. + vp_name in the monitor's database is in some state other than Down. AUTHOR vparremove was developed by the Hewlett-Packard Company. SEE ALSO vparboot(1M), vparcreate(1M), vparmodify(1M), vparreset(1M), vparstatus(1M), vparresources(5), vpartition(5). vparreset -  Sends a TOC or hard reset to a virtual partition. vparreset(1M) vparreset(1M) NAME vparreset - reset a virtual partition SYNOPSIS vparreset -p vp_name [-h|-t] [-q] [-f] DESCRIPTION The vparreset command simulates, at the virtual partition level, the RS and TOC operations at a Control-B prompt on the system console. Only a superuser can execute the vparreset command. vparreset causes the virtual partition monitor to simulate a hard (RS) reset or soft (TOC) reset of the specified virtual partition. Either operation gathers new Processor Information Module (PIM) data, which is displayed unless the -q (quiet) option is also specified. Unintentional use of the vparreset command has serious consequences; therefore the user is prompted to confirm the operation unless the -f (force) option is specified. Options vparreset recognizes the following command line options and arguments: -p vp_name Specifies the unique name of the virtual partition to be reset.The virtual partition must be in a state other than Down or Crashing. Required. -t Simulates a TOC reset. Displays current PIM data before resetting unless the -q option is also specified. The TOC reset is also the default operation of the command, applied if neither the -h nor -t option is specified. The -t and -h options cannot both be specified in the same command. -h Simulates a hard (RS) reset instead of a TOC. Displays current PIM data before resetting unless the -q option is also specified. -q Bypasses the display of current PIM data when resetting the virtual partition. -f The force option. Omits the confirmation dialog before resetting the virtual partition. This option is intended for use by scripts and other non-interactive applications. RETURN VALUE The vparreset command exits with one of the following values: 0 Successful completion. 1 One or more error conditions occurred. EXAMPLES Perform a TOC reset on the virtual partition called Oslo, dumping the PIM data: vparreset -p Oslo -t Reset virtual partition Oslo? [n] y Perform a hard reset on virtual partition Bergen skipping the confirmation dialog: vparreset -p Bergen -h -f ERRORS vparreset displays error messages on stderr for any of the following conditions: + A required option is omitted. + A nunknown option is specified. + A value is omitted for an argument that requires one, or a value is specified for an argument which does not take one. + vp_name does not exist in the monitor database, or is in the wrong state. + Both the -h and -t options are specified. AUTHOR vparreset was developed by the Hewlett-Packard Company. SEE ALSO vparboot(1M), vparcreate(1M), vparmodify(1M), vparremove(1M), vparstatus(1M), vparresources(5), vpartition(5). vparresources -  Sends a TOC or hard reset to a virtual partition. vparresources(5) vparresources(5) NAME vparresources - description of virtual partition resources and their requirements DESCRIPTION Hardware resources are the most important property of a virtual partition (vPar). These resources are divided into three major categories: + CPUs, or processors + Memory + I/O devices, such as disks, terminals, and printers. CPUs are further subdivided into bound and unbound processors. A bound processor is interrupt-enabled and, at initial release, cannot be de-configured while the vPar is running. An unbound, or floating, processor cannot process interrupts, but can be de-configured from a running vPar, and assigned to another running vPar. Each vPar can configure a subset of total system hardware resources such that a given physical resource is assigned to at most one vPar. This job is managed by two of the six virtual partition commands: + vparcreate(1M), used when creating a new vPar. Resources can only be added. + vparmodify(1M), used when modifying an existing vPar configuration. Resources can be added, modified, or deleted. Each command has specific resource syntax and semantic requirements. For example, some resource changes can only be made if the target vPar is not running. Some syntax forms can be specified multiple times in one command. Others can only be specified once.All of these conditions are described in the tables below. The general form of a resource specification is up to five positional fields delimited by colons (":"). No whitespace is allowed within any field. Table I summarizes the three categories and all the allowable forms for each. Table II specifies which forms are allowed for each of the three tasks (add, modify, or delete). Table III is a detailed description of each syntax form and the conditions required for its use. Table I. Resource syntax summary ______________________________________________________ |Resource | Form | # times/command | |_________|_________________________|_________________| |CPU | cpu:path | Multiple | | | cpu::num | Once | | | cpu:::[min][:[max]] | Once | |_________|_________________________|_________________| |I/O | io:path[:attr1[,attr2]] | Multiple | |_________|_________________________|_________________| |Memory | mem::size | Once | | | mem:::base:range | Multiple | |_________|_________________________|_________________| The first field is always one of the (case-insensitive) strings cpu, io, or mem. The second field, when used, is a hardware path, for example, 10/12/6. num, min, and max are all positive integers. size and range are positive 64-bit integers in units of megabytes. base is an unsigned 64-bit integer in units of bytes. The commands round each of them upward as required to 64 megabyte boundaries. size, range, and base may each be specified in decimal or in hexadecimal. A hex specification should be preceded by 0x, as in 0x8000000. The attributes for the I/O specification are zero, one, or both of the following (case-insensitive) strings: ALTBOOT and BOOT. If both are specified, separate them with a comma. Each of the attributes can be assigned to no more than one I/O device. If it is already assigned to a device, a new assignment silently de- assigns it from its present device. However, one device can associate both attributes.This means it is possible for one device to own both the ALTBOOT and BOOT attributes, but it is not possible for two or more devices to own BOOT. Users must guard against assigning an attribute to an inappropriate device, for example, assigning BOOT to a tty. The commands do not check for this, nor do they prevent it. Table II. Allowed forms for each task ______________________________________________________ | | | Allowed with | | Task | Form | vPar running | |____________|_________________________|______________| |-a (add) | cpu:path | No | | | cpu::num | Yes | | | cpu:::[min][:[max]] | N/A | | | (vparcreate only) | | | | io:path[:attr1[,attr2]] | No | | | mem::size | No | | | mem:::base:range | No | |____________|_________________________|______________| |-m (modify) | cpu::num | Yes | | | cpu:::[min][:[max]] | No | | | io:path[:attr1[,attr2]] | No | | | mem::size | No | |____________|_________________________|______________| |-d (delete) | cpu:path | No | | | cpu::num | Yes | | | io:path[:attr1[,attr2]] | No | | | mem::size | No | | | mem:::base:range | No | |____________|_________________________|______________| The forms above are subject to the following semantic rules enforced by the commands.Note that according to Table II, except for the cpu::num form, a vPar must be in the Down state (or in an alternate database) to apply any of the changes described below. This requirement may be relaxed or removed in a future release. + CPUs + The total number of CPUs assigned to a vPar, specified by cpu::num, must always be within the range specified by the cpu:::min:max specification. min of these are bound; (num-min) are unbound. + Any or all bound CPUs can be specified by explicit path, the cpu:path form. Any that are not so specified are allocated from the available pool and bound by the vPar monitor. A corollary to this is that you cannot specify more than the min CPUs by explicit path. If you wish to specify more, you must first increase the min, which in turn may require you to increase the max, num, or both. When you use -a cpu:path or -d cpu:path you do not change the total number of CPUs in your vPar.Instead, you replace a monitor-assigned bound CPU with one that you specify (-a) or replace a CPU that you specified with a monitor-assigned CPU (-d). Hewlett-Packard recommends that users configure specific CPUs only when required for performance reasons. In other situations, specify only the total number of CPUs (num) and how many of these should be bound (min), and allow the monitor to manage the actual CPUs allocated. + Since the monitor is not consulted when you are configuring a vPar in an alternate database (it need not even be running), you can specify any value for min (but <= max) in this case. When this database is loaded into the monitor, the monitor adjusts min downward as required if the specified number of CPUs is not available. + Defaults: When a vPar is created, the following defaults are in effect: + min: Platform dependent, usually 1 + num: 1 + max: If the vPar is created in an alternate database, 32767. If it is created in the live monitor database, max is equal to the total number of CPUs on the entire hardware system. You can modify these defaults with command line options to the vparcreate or vparmodify command. + Memory + The total amount of memory specified in explicit memory ranges, using the mem:::base:range specification, must be less than or equal to the total memory assigned to the vPar using the mem::size specification. When you specify a specific range of memory (whether adding or deleting), you do not change the total amount of memory assigned to the vPar. When adding, you merely specify that the particular range you specify be one part of the total amount assigned to your vPar. When deleting, the specific range is returned to the pool of unspecified total memory assigned to the vPar. Hewlett-Packard recommends that users configure specific memory ranges only when required for performance reasons. In other situations, specify only total memory and allow the monitor to manage the actual ranges allocated. EXAMPLES If more than one task is specified in a command, they are processed in the order (left-to-right) in which they are encountered on the command line. Some tasks will affect the outcome of others. Here is an example of correct usage, as well as counterexamples within the description. vparcreate -p winona2 -a cpu::2 -a cpu:::2:4 -a cpu:41 -a cpu:45 -a mem::1280 -a mem:::0x40000000:128 -a io:0/8 -a io:1/10 -a 0/8/0/0.5.0:boot At creation time, before any options are processed, min is equal to 1, as does num. Assume that the default max is sufficiently high, and that the specified resources are available for allocation. + -a cpu::2 succeeds because num(2) is within the range of the min and the max. + -a cpu:::2:4 then succeeds because num(2) is still within the required range. Note that if the two options were reversed the command would return an error due to left-to-right option processing, and the desired min would exceed the default num. + Finally, the specification of the two CPUs at explicit paths 41 and 45 succeeds because such assignments create bound CPUs. Since we have set min equal to 2, they can be accommodated. Note that without the first two -a options, the -a cpu:45 option would fail, because there would only be room for one (the default) bound CPU. + The allocation of 128 MB of specific memory at address 0x40000000 succeeds only because the total allocated memory was first set to 1280 MB. The 128 MB is taken from that 1280 MB; no new memory is added as a result of the -a mem:::0x40000000:128 option. The following vparmodify(1M) command adds two floating (unbound) CPUs to a vPar that has the Static attribute set. The Static attribute is then restored. vparmodify -p winona3 -S dynamic -a cpu::2 -S static Table III. Detailed resource specifications Task: -a cpu:path _________________________________________________________________ |Explanation | Assigns a CPU resource at a specific path (bound | | | CPU) to the vPar's configuration. The CPU | | | replaces a monitor-assigned bound CPU. Bound | | | CPUs are able to process interrupts. | |_____________|__________________________________________________| |Value | A text string of the form returned by the | | | ioscan(1M) command, such as "10/12/6" | |_____________|__________________________________________________| |Usage | The vPar must not be running. This restriction | |Restrictions | may be removed in a future release. | | | | | | The total number of CPUs at a specific path | | | must be <= min | | | | | | In addition, if the vPar is in the monitor | | | database: | | |o A CPU must exist at path, | | |o It must be available (not assigned to | | | a vPar, including the target vPar). | |_____________|__________________________________________________| |Usage | The addition does not increase either the number | |Guidelines | of total CPUs or bound CPUs allocated to | | | the vPar. Instead, it replaces a previously | | | bound CPU whose path had been selected by | | | the monitor. To increase total CPU allocation, | | | specify an appropriate new num. To | | | increase the number of bound CPUs, specify a | | | new min. | | | | | | Hewlett-Packard recommends that users configure | | | specific CPUs only when required for performance | | | reasons.In other situations, specify only the | | | total number of CPUs (num) and how many of these | | | should be bound (min), and allow the monitor | | | to manage the actual CPUs allocated. | |_____________|__________________________________________________| Task: -a cpu::num ___________________________________________________________________ |Explanation | Adds num unbound CPUs to the vPar's configuration. | | | The CPUs are drawn from a systemwide pool of | | | available CPUs. | |_____________|____________________________________________________| |Value | A positive integer | |_____________|____________________________________________________| |Usage | If the vPar is in an alternate database file or | |Restrictions | is in the live monitor database but not running: | | |o Total number of CPUs <= max | | | | | | In addition, if the vPar is running: | | |o num CPUs must exist on the system, | | |o They must have been available (not bound to | | | any vPar) at the time the vPar was booted. | | | | | | If another vPar is deleted with the | | | vparremove command, its bound CPUs cannot | | | be added as floaters to a running vPar. | |_____________|____________________________________________________| Task: -a cpu:::[min][:[max]] __________________________________________________________________ |Explanation | 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. | | | | | | 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. If creating a vPar in the | | | monitor database, the default max is the total | | | number of CPUs on the entire hardware system. | |_____________|___________________________________________________| |Value | If specified, min and max must be positive | | | integers such that min <= max. | |_____________|___________________________________________________| |Usage | This option is allowed only in the vparcreate | |Restrictions | command. | | | | | | min cannot exceed the total number of CPUs. The | | | default total when the vPar is created is 1. Use | | | the -a cpu::num option to change the total before | | | setting a min other than 1. | | | | | | max cannot be less than the total. | | | | | | min cannot be less than the total number | | | of CPUs configured by explicit path. | |_____________|___________________________________________________| Task: -a io:path[:attr1[,attr2]] ______________________________________________________________________ |Explanation | 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. | | | | | | This option only adds specified attributes. The | | | state of unspecified attributes is not changed. | |_____________|_______________________________________________________| |Value | path: A text string of the form returned | | | by the ioscan(1M) command, | | | such as "10/12/6" | | | | | | attr: One or both of the case-insensitive | | | attribute strings ALTBOOT and BOOT. If | | | both are specified, they are separated | | | by a comma (","). | |_____________|_______________________________________________________| |Usage | The vPar must not be running. | |Restrictions | | | | The I/O resource must either be unassigned or (when | | | adding attributes to an already assigned resource) | | | be assigned to the target vPar. | |_____________|_______________________________________________________| |Usage | At most one device can be assigned the ALTBOOT | |Guidelines | and BOOT attributes. Assigning one of these | | | attributes to a device silently deletes it from its | | | former device, if any. | | | | | | Caution:You should assign attributes to appropriate | | | devices, but this is not checked. For example, | | | ALTBOOT and BOOT should be assigned to a disk or | | | tape. Failure to do this may result in an unbootable | | | partition. | |_____________|_______________________________________________________| Task: -a mem::size ______________________________________________________________ |Explanation | Specifies the increase, in megabytes rounded | | | upward to a 64 megabyte boundary, in the | | | total amount of memory to be allocated to the | | | vPar. This memory is taken from unspecified | | | ranges of memory available to the system when | | | the partition boots. | |_____________|_______________________________________________| |Value | A positive 64-bit integer <= 17592186044352 | |_____________|_______________________________________________| |Usage | The vPar must not be running. | |Restrictions | | | | If the vPar is in the monitor database, this | | | memory must physically exist and be available | | | after the memory requirements of all other | | | vPars have been satisfied. | | | | | | If the vPar is in an alternate database file, | | | the assignment always succeeds. The amount | | | of memory actually allocated if the database | | | is loaded into the monitor may be less if | | | some or all of it is needed in other vPars. | |_____________|_______________________________________________| Task: -a mem:::base:range ________________________________________________________________________ |Explanation | Specifies 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 64 megabyte | | | boundaries. | |__________________|____________________________________________________| |Values | Base: An unsigned 64-bit integer <= 0xfffffffffc000000 | | | Range: A positive 64-bit integer <= 17592186044352 | |_____________|_________________________________________________________| |Usage | The vPar must not be running. | |Restrictions | | | | No part of the range may be already owned by this | | | or another vPar. | | | | | | If the vPar is in the monitor database, the entire | | | range must exist in the system. | | | | | | The total memory allocated in specific ranges must | | | not exceed the vPar's memory size specification. | |_____________|_________________________________________________________| |Usage | Addition of specific memory ranges does not increase | |Guidelines | the total amount of memory allocated to the vPar. | | | Any such memory is a part of that total amount. | | | | | | Caution:It is possible to specify memory ranges | | | and sizes such that none of the vPars will launch. | | | Hewlett-Packard recommends that users configure | | | specific memory ranges only when required for | | | performance reasons. In other situations, specify | | | only total memory and allow the monitor to manage | | | the actual ranges allocated. | |_____________|_________________________________________________________| Task: -m cpu::num __________________________________________________________________ |Explanation | Sets the total number of CPUs (bound and | | | unbound) to num. | |_____________________|___________________________________________| |Value | A positive integer | |_____________|___________________________________________________| |Usage | If the vPar is in an alternate database file | |Restrictions | or is in the live monitor database but not | | | running: | | |o num must be between min and max. | | | | | | In addition, if the vPar is in the live | | | monitor database and num increases the total: | | |o num CPUs must exist on the system, | | |o They must have been available (not bound to| | | any vPar) at the time the vPar was booted. | | | | | | If another vPar is deleted with the | | | vparremove command, its bound CPUs cannot | | | be added as floaters to a running vPar. | |_________________|_______________________________________________| Task: -m cpu:::[min][:[max]] ______________________________________________________________ |Explanation | 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. | | | | | | You can change only min or max by not | | | specifying the other field. | |_____________|_______________________________________________| |Value | If specified, min and max must be positive | | | integers such that min <= max. | |_____________|_______________________________________________| |Usage | The vPar must not be running. | |Restrictions | | | | min cannot exceed the total number of CPUs. | | | | | | max cannot be less than the total. | | | | | | min cannot be less than the total number | | | of CPUs configured by explicit path. | |_____________|_______________________________________________| Task: -m io:path[:attr1[,attr2]] ______________________________________________________________________ |Explanation | 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. | |_____________|_______________________________________________________| |Value | path: A text string of the form returned | | | by the ioscan(1M) command, | | | such as "10/12/6" | | | | | | attr: One or both of the case-insensitive | | | attribute strings ALTBOOT and BOOT. If | | | both are specified, they are separated | | | by a comma (","). | |_____________|_______________________________________________________| |Usage | The vPar must not be running. | |Restrictions | | | | The I/O resource must be assigned to the | | | target vPar. Only attributes may be modified. | |_____________|_______________________________________________________| |Usage | At most one device can be assigned the ALTBOOT | |Guidelines | and BOOT attributes. Assigning one of these | | | attributes to a device silently deletes it from its | | | former device, if any. | | | | | | Caution:You should assign attributes to appropriate | | | devices, but this is not checked. For example, | | | ALTBOOT and BOOT should be assigned to a disk or | | | tape. Failure to do this may result in an unbootable | | | partition. | |_____________|_______________________________________________________| Task: -m mem::size ___________________________________________________________________ |Explanation | Specifies the total amount of memory, in megabytes | | | rounded upward to a 64 megabyte boundary, to be | | | allocated to the vPar. Any memory in excess of | | | that specifically allocated by base and range | | | is taken from unspecified ranges of memory | | | available to the system when the partition boots. | |_____________|____________________________________________________| |Value | A positive 64-bit integer <= 17592186044352 | |_____________|____________________________________________________| |Usage | The vPar must not be running. | |Restrictions | | | | A decrease in total memory allocation must not | | | result in a total less than that of all memory | | | allocated in specific memory ranges. | | | | | | If the vPar is in the monitor database and the | | | specification results in an increased memory | | | allocation, the memory must physically exist | | | and be available after the memory requirements | | | of all other vPars have been satisfied. | | | | | | If the vPar is in an alternate database file | | | and total memory is increased, the assignment | | | always succeeds.The amount of memory actually | | | allocated if the database is loaded into the | | | monitor may be less if some or all of it is | | | needed in other vPars. | |_____________|____________________________________________________| Task: -d cpu:path _________________________________________________________________ |Explanation | De-assigns the bound CPU at the specified | | | hardware path from the vPar and replaces | | | it with a bound CPU of the monitor's choice. | | | Depending on availability, this may be the same | | | CPU that was de-assigned. | |_____________|__________________________________________________| |Value | A text string of the form returned by the | | | ioscan(1M) command, such as "10/12/6" | |_____________|__________________________________________________| |Usage | The vPar must not be running. | |Restrictions | | | | The resource at the specified path must be a | | | CPU resource. | | | | | | The vPar must own the resource. | |_____________|__________________________________________________| |Usage | The deletion does not reduce either the number | |Guidelines | of total CPUs or bound CPUs allocated to | | | the vPar. Instead, it replaces the explicitly | | | specified CPU with a bound CPU selected by the | | | monitor.To reduce total CPU allocation, | | | specify an appropriate new num. To reduce | | | the number of bound CPUs, specify a new min. | | | | | | Hewlett-Packard recommends that users configure | | | specific CPUs only when required for performance | | | reasons.In other situations, specify only the | | | total number of CPUs (num) and how many of these | | | should be bound (min), and allow the monitor | | | to manage the actual CPUs allocated. | |_____________|__________________________________________________| Task: -d cpu::num _______________________________________________________ |Explanation | Deletes num CPUs from the vPar's total | | | configuration. | |_____________|________________________________________| |Value | A positive integer | |_____________|________________________________________| |Usage | The vPar must own at least num CPUs. | |Restrictions | | | | The new total number of CPUs >= min | |_____________|________________________________________| Task: -d io:path[:attr1[,attr2]] ______________________________________________________________________ |Explanation | Removes the specified attributes of the | | | resource leaving any previously assigned | | | attributes unchanged and the resource itself | | | assigned to the vPar. If no attribute is | | | specified, removes the resource and all its | | | attributes. | |_____________|_______________________________________________________| |Value | path: A text string of the form returned | | | by the ioscan(1M) command, | | | such as "10/12/6" | | | | | | attr: One or both of the case-insensitive | | | attribute strings ALTBOOT and BOOT. If | | | both are specified, they are separated | | | by a comma (","). | |_____________|_______________________________________________________| |Usage | The vPar must not be running. | |Restrictions | | | | The I/O resource must be assigned to the | | | target vPar. | |_____________|_______________________________________________________| |Usage | Deleting an attribute from an I/O device does | |Guidelines | not cause it to be assigned to another. You | | | must do that in a separate option or command. | | | | | | At most one device can be assigned the ALTBOOT and | | | BOOT attributes. | | | | | | Caution:You should assign attributes to appropriate | | | devices, but this is not checked. For example, | | | ALTBOOT and BOOT should be assigned to a disk or | | | tape. Failure to do this may result in an unbootable | | | partition. | |_____________|_______________________________________________________| Task: -d mem::size ______________________________________________________________ |Explanation | Specifies the decrease, in megabytes rounded | | | upward to a 64 megabyte boundary, in the | | | amount of total memory allocated to the vPar . | |_____________|_______________________________________________| |Value | A positive 64-bit integer <= 17592186044352 | |_____________|_______________________________________________| |Usage | The vPar must not be running. | |Restrictions | | | | The vPar must own at least the specified | | | amount (after rounding) of non-specific | | | memory. | | | | | | The decrease must not result in a total less | | | than that of all memory allocated in specific | | | memory ranges. | |_____________|_______________________________________________| Task: -d mem:::base:range ________________________________________________________________________ |Explanation | 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 64 megabyte | | | boundaries. | |_____________|_________________________________________________________| |Values | Base: An unsigned 64-bit integer <= 0xfffffffffc000000 | | | Range: A positive 64-bit integer <= 17592186044352 | |_____________|_________________________________________________________| |Usage | The vPar must not be running. | |Restrictions | | | | The vPar must own the entire range. | | | | | | Either the start or end point of the | | | specified range must match the start or end | | | point of an existing range. | |_____________|_________________________________________________________| |Usage | De-assigning specific memory ranges does not decrease | |Guidelines | the total amount of memory allocated to the vPar. | | | | | | Caution:It is possible to specify memory ranges | | | and sizes such that none of the vPars will launch. | | | Hewlett-Packard recommends that users configure | | | specific memory ranges only when required for | | | performance reasons. In other situations, specify | | | only total memory and allow the monitor to manage | | | the actual ranges allocated. | |_____________|_________________________________________________________| SEE ALSO vparboot(1M), vparcreate(1M), vparmodify(1M), vparremove(1M), vparreset(1M), vparstatus(1M), vpartition(5). vparstatus -  Displays virtual partition and available resources information. vparstatus(1M) vparstatus(1M) NAME vparstatus - display information about one or more virtual partitions SYNOPSIS vparstatus [-v | -M] [-p vp_name]... [-D db_file] vparstatus -A [-M] vparstatus -w vparstatus -e vparstatus -R [-p vp_name] DESCRIPTION The various forms of the vparstatus command display: + The attributes and hardware resources associated with one or more virtual partitions (vPars) in either summary (the default) or detailed format. The -M option presents the same data in machine- readable format. + Resources currently available, that is, not assigned to any virtual partition. The -M option presents the same data in machine- readable format. + The name of the current virtual partition, that is, the virtual partition from which the command is run. + The virtual partition monitor's event log. + Processor Information Module (PIM) data from the most recent resetting of a virtual partition. Only a superuser can execute the vparstatus command. If no arguments are supplied, vparstatus displays a summary format of all attributes and resources of all virtual partitions in the monitor database. One or more virtual partitions may be specified explicitly in order to restrict the output to information about the selected virtual partitions. The -D option lists similar information from an alternate database file, but with a major difference. See the description of the -D option for further details. There are three major listing formats. The format chosen depends on command options and forms: + The summary format lists name, attributes, and resource totals. It is displayed if neither the -v nor -M option is used. + The detailed format lists name, attributes, and detailed resource assignments, one per line with annotative headings. The -v option produces this format. + The machine readable format displays the same information as the detailed format, except that field descriptive headers are omitted, and the information is all on one line. Individual fields are separated from each other by four delimiters.These are all described below. Three additional formats are provided for the -w, -e and -R options. Information displayed by vparstatus includes the following: + The name of the virtual partition (limited to 30 characters in summary format) + The state of the virtual partition, from the list below: Up: The virtual partition has notified the monitor that it is up. This is the normal state of a running virtual partition, however it does not necessarily mean that the virtual partition has completed its initialization and is fully operational. Down: The virtual partition is fully halted. This could be the result of a normal /etc/shutdown -h command, or a vparreset of a partition with its autoboot attribute set to manual. It is also the initial state of a virtual partition immediately after the virtual partition monitor is started. Load: The monitor is loading the kernel image of the virtual partition. This state precedes the Boot state. Boot: The virtual partition has been launched, but has not completely booted. Crash: The virtual partition is shutting down ungracefully (either a panic or a reset) Shut: The virtual partition is shutting down gracefully Hung: The virtual partition has stopped sending heartbeat messages to the monitor. N/A: The virtual partition is in an alternate database file, and so has no state. + The static/dynamic resource attribute + The auto/manual boot attribute + The path to the kernel (limited to 25 characters in summary format) + The boot options (limited to 5 characters in summary format) + Summary or detailed CPU, I/O, and memory resource allocations Options vparstatus recognizes the following command line options and arguments: -p vp_name Restricts the command display to information about vp_name.By default, information about all virtual partitions in the monitor database or specified alternate partition database is displayed. Multiple vp_names may be specified, except when used to display PIM data. -D db_file Displays information from the alternate partition database file db_file rather than from the monitor database. The attributes and resources of a vPar in an alternate database file were specified in either the vparcreate or vparmodify command, but have not necessarily been checked for existence on a running system. They are referred to as "requested" information. Existence of the attributes and resources of a vPar in the live monitor database have been verified; they are referred to as "effective" information. -v Presents a detailed display, one attribute or resource per line. Each attribute and resource type is identified. CPU resources are identified by path when path information is available. Some CPU resources may not be known when displaying the status of alternate database vPars or vPars in the Down state. In this case, "<no path>" is displayed. -A Displays information about available resources (that is, those not assigned to any virtual partition) in the virtual partition monitor's database. The monitor must be running.Resources are displayed one per line. -M Displays information in a machine readable format. Individual fields are separated by one of four delimiters: + The colon (:) separates each field and resource type.For example, the state, attribute information, and kernel path would be displayed as: Up:Static,Autoboot:/stand/vmunix + The semicolon (;) separates subfields of a resource type.For example, CPU resources are shown as: 5/10;33,37;51,53,55;<>,<>,<> where the first subfield shows the minimum and maximum CPUs configured for the virtual partition; the second subfield lists the bound, or specified path, CPUs specifically configured by the user; the third subfield lists the remaining bound CPUs, which are assigned by the monitor; and the final subfield lists the unbound, or floating, CPUs. In the example above, the paths of the unbound CPUs are not known. This could be the case because the example vPar is in an alternate database, or the vPar is in a Down state for which unbound CPUs are not assigned.In this case, "<>" is displayed in place of the path. + The comma (,) separates individual items in a list of similar items, such as the fixed path CPUs in the previous example. + The slash (/) separates all other related items, such as the CPU minimum and maximum in the same example. Elements in the display are in the same order as the corresponding non-machine-readable display (-v or -A). -w Displays the name of the current virtual partition (the one in which the command is executed). The monitor must be running. -e Displays the monitor's event log, a circular file roughly 4K bytes long. Once the file is full, new entries overlay old ones to the nearest character. As a result, the first entry displayed may be missing some leading characters.The monitor must be running. -R Displays Processor Information Module (PIM) data from the most recent reset of the specified virtual partition. If a virtual partition is not specified, PIM data from the current virtual partition, that is, the one in which the command is executed, is displayed. If the virtual partition has not been reset, or if PIM data has been cleared since then, no PIM data is available so a message to that effect is displayed. The monitor must be running. RETURN VALUE The vparstatus command exits with one of the following values: 0 Successful completion. 1 Syntax error or invalid option. EXAMPLES These examples assume the existence of an N-class hardware system, Europe, on which the virtual partition database Norway is currently loaded in the virtual partition monitor.Norway has two configured virtual partitions: Oslo, and Bergen. The vparstatus command is run from Oslo. Europe has eight CPUs, two System Bus Adapters (SBAs), each with six Local Bus Adapters (LBAs), and 2 Gbytes of main memory. These resources are allocated among Oslo and Bergen as follows: Oslo: + Two bound CPUs at hardware paths 33 and 37. The CPU at 33 was specified by the user with the -a cpu:path resource specification. The CPU at 37 was assigned by the monitor from the pool of CPUs available when Oslo was booted. + One floating (unbound) CPU at hardware path 41. + One SCSI boot disk at SBA/LBA/path 0/0/2/0.6.0. + One terminal at 0/0/4/0. + One LBA (0/4) to which are attached several LAN adapters. + Specific memory addresses 0x4000000 to 0xc000000 (Range = 64 MB) and 0x20000000 to 0x40000000 (Range = 128 MB). These specific ranges are part of a total memory allocation of 704 MB. Bergen: + Two bound CPUs at hardware path 97 and 101, both assigned by the monitor. + Two unbound CPUs at hardware paths 93 and 99. + One SCSI boot disk at 1/4/0/0.5.0. + One LBA (1/10) to which are attached several LAN adapters + Specific memory 0x44000000 to 0x50000000 (Range = 192 MB) and 0x60000000 to 0x80000000 (Range = 512 MB).These specific ranges are part of a total memory allocation of 768 MB. Display a summary format of all attributes and resources in all virtual partitions: # vparstatus [Virtual Partition] Boot Virtual Partition NameState Attributes Kernel Path Opts ============================== ===== ========== ========================= ===== OsloUp Stat,Auto /stand/vmunix BergenUp Dyn,Manl /stand/vmunix [Virtual Partition Resource Summary] CPU Num Memory (MB) CPU Bound/ IO # Ranges/ Virtual Partition Name Min/Max Unbound devs Total MB Total MB ============================== ================ ==== ==================== Oslo 2/ 4 21 3 2/640 704 Bergen 2/ 4 22 2 2/704 768 Display detailed attributes and resources of partition Oslo: # vparstatus -p Oslo -v [Virtual Partition Details] Name: Oslo State: Up Attributes: Static,Autoboot Kernel Path: /stand/vmunix Boot Opts: [CPU Details] Min/Max: 2/4 Bound by User [Path]:33 Bound by Monitor [Path]: 37 Unbound [Path]: 41 [IO Details] 0.0.2.0.6.0 BOOT 0.0.4.0 0.4 [Memory Details] Specified [Base /Range]: 0x4000000/64 (bytes) (MB) 0x20000000/128 Total Memory (MB): 704 Display Bergen's CPU resources in machine-readable format: # vparstatus -p Bergen -M Bergen:Up:Dynamic,Manual:/stand/vmunix::2/4;;97,101;93,99:1.4.0.0.5.0 BOOT,1.10 :0x44000000/192,0x60000000/512;768 Display the name of the current virtual partition: # vparstatus -w The current virtual partition is Oslo. AUTHOR vparstatus was developed by the Hewlett-Packard Company. SEE ALSO vparboot(1M), vparcreate(1M), vparmodify(1M), vparremove(1M), vparreset(1M), vparresources(5), vpartition(5). vpartition -  Displays information about the vPars Command Line Interface. vpartition(5) vpartition(5) NAME vpartition - display information about the Virtual Partition Command Line Interface SYNOPSIS vpartition DESCRIPTION This manpage gives a listing and brief description of the commands which are used to manage virtual partitions. Command | Description ______________|_________________________________________________________ vparboot | Boot(start) a virtual partition. | vparcreate | Create a new virtual partition. | vpardump | Manage monitor dump files. | vparextract | Extract memory images from a running virtual partition | system. | vparmodify | Modify an existing virtual partition. | vparreloc | Relocate the load address of a vmunix file, determine | if a vmunix file is relocatable, or promote the scope of | symbols in a relocatable vmunix file. | vparremove | Remove (delete) an existing virtual partition. | vparreset | Send a TOC or hard reset to a virtual partition. | vparresources | Description of virtual partition resourcs and | their requirements. | vparstatus | Display virtual partition and available resources | information. | vparutil | Get and set SCSI parameters for disk devices from | a virtual partition. AUTHOR vpartition was developed by the Hewlett-Packard Company. SEE ALSO vparboot(1M), vparcreate(1M), vpardump(1M), vparextract(1M), vparmodify(1M), vparreloc(1M), vparremove(1M), vparreset(1M), vparstatus(1M), vparutil(1M), vparresources(5). vparutil -  Works with SCSI-related information of disks in a vPar. vparutil(1M) vparutil(1M) NAME vparutil - get and set SCSI parameters for disk devices from a virtual partition SYNOPSIS vparutil -g dev_path vparutil -s dev_path [id] [rate] DESCRIPTION The vparutil command gets and sets SCSI paramaters for a specified SCSI device from a running virtual partition system. Only a superuser can execute the vparutil command. Options vparutil recognizes the following command-line options: -g Gets the SCSI parameters for the specified SCSI disk device, dev_path. -s Sets the SCSI parameters for the specified SCSI disk device, dev_path. vparutil recognizes the following command-line operands: dev_path The device path of the SCSI disk device. id The SCSI ID for the specified disk device. rate The SCSI rate for the specified disk device. EXAMPLES Set the SCSI ID for disk at 0/0/2/0.6.0 to 3: # vparutil -s 0/0/2/0.6.0 3 RETURN VALUE 0Successful. 1Could not communicate with virtual partition monitor. >1Other error. AUTHOR vparutil was developed by the Hewlett-Packard Company. |
