HP-UX Virtual Partitions Administrator's Guide (includes A.03.05 and A.04.05)

#vparcreate -p vpar1 -a cpu::1 -a cpu:::1 -a mem::1024 -a io:0.0 -a
io:0.0.2.0.6.0:BOOT
where the I/O assignment is specified using the LBA level (-a io:0.0) and the boot disk
is specified using the full hardware path (-a io:0.0.2.0.6.0).
For an nPartitionable system, the vparcreate command would look like:
# vparcreate -p vpar1 -a cpu::1 -a cpu:::1 -a mem::1024 -a io:0.0.0 \
-a io:0.0.0.2.0.6.0:BOOT
where the I/O assignment is specified using the LBA level (-a io:0.0.0.) and the boot
disk is specified using the full hardware path (-a io:0.0.0.2.0.6.0).
For information on using the LBA level on nPartitionable systems, also see “Planning,
Installing, and Using vPars with an nPartitionable Server” (page 51).
• SBA/LBA versus cell/SBA/LBA When viewing hardware paths, note the following:
1. The explicit specification of an LBA on a non-nPartitionable system consists of two
fields: sba/lba
2. The explicit specification of an LBA on an nPartitionable system consists of three fields:
cell/sba/lba
3. With A.04.xx and A.05.xx, all LBAs under a SBA are implied when explicitly specifying
a SBA without specifying any LBA. Therefore, the path specified on a command line
can have different meanings depending upon the vPars version, the type of server, and
the user intent. For example, the path of x/y can mean any of the following:
— sba=x, lba=y on a non-nPartitionable server running vPars A.03.01 or earlier.
— sba=x, lba=y on a non-nPartitionable server running vPars A.03.02 or later or A.04.xx.
— cell=x, sba=y on an nPartitionable server running vPars A.03.02 or later, A.04.xx,
or A.05.xx.
• Supported I/O Check your hardware manual to verify that your mass storage unit can
be used as a bootable device. If a mass storage unit cannot be used as a boot disk on a
non-vPars server, it cannot be used as a boot disk on a vPars server. vPars does not add any
additional capability to the hardware.
For information on supported I/O interface cards and configurations, see the document
HP-UX Virtual Partitions Ordering and Configuration Guide.
Memory: Topics
The memory topics in this section are:
• “Memory: Concepts and Functionality” (page 178)
• Assigning (Adding) Or Deleting Memory
— “Memory: Assigning (Adding) or Deleting By Size (ILM)” (page 182)
— “Memory: Assigning (Adding) Or Deleting By Size (CLM)” (page 182)
— “Memory: Assigning (Adding) Or Deleting By Address Range” (page 184)
— “Memory, CPU: Canceling Pending Operations” (page 205)
— “Memory: Converting Base Memory to Float Memory” (page 186)
— “Memory: Available and Assigned Amounts” (page 185)
• Granularity
— “Memory: Granularity Concepts ” (page 187)
— “Memory: Granularity Issues (Integrity and PA-RISC)” (page 188)
— “Memory: Setting the Granularity Values (Integrity)” (page 189)
— “Memory: Setting the Granularity Values (PA-RISC)” (page 192)
• “Memory: Notes on vPars Syntax, Rules, and Output” (page 192)
Memory: Topics 177