There are several commands used to create and work with Virtual Partitions in Figure 2-1 that we have not yet covered. Table 2-1 is provides an overview of many commonly used Virtual Partitions-related commands. This is the same information that is on the tear-out Overture Partitions Command Summary.
Table 2-1. Virtual Partition Command Summary
| Command | Description |
|---|
| ISL> Initial System Load prompt. | Virtual Partitions Monitor is loaded from ISL> with: ISL> hpux /stand/vpmon MON> To load Virtual Partitions directly from ISL>, use: ISL> hpux /stand/vpmon vparload -p vPar_name |
| MON> Virtual Partitions Monitor prompt. (Also see vparload command.) | This is loaded from ISL with: ISL> hpux /stand/vpmon MON> To load an alternate database from ISL, use: ISL> hpux /stand/vpmon -D db_file To load one vPar from MON ,use: MON> vparload vPar_name Many other commands can be issued from MON. Type help or ? to list. (Commands include: scan, vparinfo, ls, log, getauto, lifls, cbuf, cat.) |
| vparload Load Virtual Partitions from MON> prompt only. | form1: vparload -all form2: vparload -auto form3: vparload -p vp_name [-b kernelpath] [-o "boot_options"] [-B hardware_path] To boot a Virtual Partition from MON>: MON> vparload -p vPar_name To boot all Virtual Partitions from MON>: MON> vparload -all To boot a Virtual Partition in single-user mode from MON>: MON> vparload -p vPar_name -o "-is" Some other options to issue at MON> include: "-lq" (low quorum,) "-lm" (maintenance mode) |
| vparboot Boot a Virtual Partition from the command line only. | form1: vparboot -p vp_name [-b kernel_path] [-o boot_opts] [-B boot_addr] form2: vparboot -p vp_name -I ignite_kernel To boot a Virtual Partition from the command line: # vparboot -p vPar_name To boot a Virtual Partition from the command line in single-user mode: # vparboot -p vPar_name -o -"is" |
| vparcreate Create a Virtual Partition. | form: vparcreate -p vp_name [-B boot_attr] [-D db_file] [-S static_attr] [-b kernel_path] [-o boot_opts] [-a rsrc] [-a...] To create a Virtual Partition with three processors (num) total, two bound (min), 2048MB RAM, all components on 0/0, boot disk at 0/ 0/1/1.2.0, with a kernel of /stand/vmunix, autoboot on, and console at 0/0/4/0: # vparcreate -p vPar_name -a cpu::3 -a cpu:::2:4 -a mem::2048 -a io:0/0 -a io:0/0/1/1.2.0:boot -b /stand/vmunix -B auto Notes: - HP-UX 11i must be loaded on volume before or after Virtual Partition is created. If HP-UX 11i is loaded after vPar is created, vparboot -p vp_name -I ignite_kernel is used to load 11i. - /stand/vmunix is default and does not need to be specified. -vPar was not set to static, meaning that it can be modified later. -CPUs are three total (num), two bound (min), and as many as two unbound (max). |
| vparmodify Modify the attributes of a Virtual Partition. (Note that CPUs are added relative to the current number with -a. -a cpu::2 adds two CPUs to the current number of CPUs. -m cpu::3 specifies an absolute number of CPUs of three.) | 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] [-a...] [-m rsrc] [-m...] [-d rsrc] [-d...] To add processor at path 109 (adds this proc to those already assigned): # vparmodify -p vPar_name -a cpu:109 To specify an absolute number of three processors: # vparmodify -p vPar_name -m cpu::3 |
| vparremove Delete a Virtual Partition. | vparremove -p vp_name [-D db_file] [-f] To delete a Virtual Partition in the currently running database: # vparremove -p vPar_name |
| vparreset Reset a Virtual Partition. | vparreset -p vp_name [-h|-t] [-q] [-f] To reset a Virtual Partition simulating the TOC operations at the Ctrl-B prompt. Without the -h option the default command simulates only a TOC. # vparreset -p vPar_name To force a hard reset of a Virtual Partition: # vparreset -p vPar_name -h -f |
| vparresources(5) man page Provides description of Virtual Partitions and their resources. | This is a manual page that describes Virtual Partition resources in general and how resources are specified in other commands, such as vparmodify. |
| vparstatus Display the status of Virtual Partitions. | form1: vparstatus [-v | -M] [-p vp_name] [-p...] [-D db_file] form2: vparstatus -A [-M] (available resources) form3: vparstatus -w (name of current vPar) form4: vparstatus -e (event log of Virtual Partition Monitor) fomr5: vparstatus -R [-p vp_name] (PIM data from most recent reset) To display the status of a Virtual Partition in verbose mode: # vparstatus -v -p vPar_name To display the status of all Virtual Partitions in verbose mode: # vparstatus -v To display the available or unused resources: # vparstatus -A |
| vpartition man page Display information about the Virtual Partition Command Line Interface. | Provides the following brief description of Virtual Partitions commands: vparboot Boot (start) a virtual partition. vparcreate Create a new virtual partition. vparmodify Modify an existing virtual partition. vparremove Remove (delete) an existing virtual partition. vparreset Simulate a TOC or hard reset to a virtual partition. vparstatus Display virtual partition and available resources information. |
| Specify CPU Resources by: Types of CPUs: (See vparresources man page for more detail on all types of resources.) | Number of bound and unbound CPUs: cpu::num CPU hardware path(s): cpu:path Minimum and maximum number: cpu:::[min][:[max]] Bound: CPU is tied to a Virtual Partition when vPar is active. Allocation is done at the time of vPar creation. Lowest number bound CPU is monarch for the vPar. Interrupts are handled by bound CPUs. Unbound: CPU that can be dynamically reassigned. Do not handle interrupts. |
| Specify Memory by: | Size mem::size Base and range: mem:::base:range combination of both above. |
| Specify I/O: | Use path: io:path[:attr1[,attr2[...]]] (see man page vparresources for details). |
| To add resources use: (This adds component relative to what already exists if running vparmodify.) | -a cpu:path -a cpu::num (can be done with vPar running) [-a cpu::num] [-a cpu:::[min]:[max]] -[a cpu:path] (::: is vparcreate only) -a io:path[:attr1[,attr2[...]] -a mem::size -a mem:::base:range |
| To delete resources use (This deletes component relative to what already exists if running vparmodify.) | -d cpu:path -d cpu::num (can be done with vPar running) -d io:path[:attr1[,attr2[...]] -d mem::size -d mem:::base:range |
| To modify resources use: (This modifies to absolute number rather than relative.) | -m cpu::num (can be done with vPar running) -m cpu:::[min][:max]] -m io:path[:attr1[,attr2[...]] -m mem::size |
| vPars setboot Options: -a -b -p -s no options | Changes the alternate boot path of the Virtual Partition. Sets the autoboot attribute of the Virtual Partition. Changes the primary boot path of the Virtual Partition. No effect. Displays information about boot attributes. To set Autoboot on: # setboot -b on To set the primary boot path: # setboot -p 0/0/1/1.2.0 To set the alternate boot path: # setboot -a 0/8/0/0.8.0.5.0.0.0 |
| vPars States: load boot up shut down crash hung | The kernel image of a Virtual Partition is being loaded into memory. This is done by the Virtual Partition monitor. The Virtual Partition is in the process of booting. The kernel image has been successfully loaded by the Virtual Partition monitor. The Virtual Partition has been successfully booted and is running. The Virtual Partition is in the process of shutting down. The Virtual Partition is not running and is down. The Virtual Partition has experienced a panic and is crashing. The Virtual Partition is not responding and is hung. |
We'll use some of the commands shown in Table 2-1 in the upcoming section on creating virtual partitions. There is more detail on the Virtual Partition commands in Appendix A, which contains the online manual pages for the commands.
Let's now move on to creating our virtual partitions.
