HP-UX Virtual Partitions Ordering and Configuration Guide (September 2010)

virtual partition is UP). By default, all memory assigned to a virtual partition during vPar
creation or memory addition, is considered base memory. For more information, see the
A.05.01 Resources chapter in the HP-UX Virtual Partitions Administrator Guide.
• Hyperthreading
Hyperthreading can be enabled in a vPars environment if the processor hardware supports
it. Each vPar OS and applications will be able to take advantage of CPU-threading, just as
in an nPartitions environment. Processor assignments and migration will continue to be
supported at the CPU-core level though. For more information, see the “A.05.01 Resources”
chapter in the HP-UX Virtual Partitions Administrator Guide.
• Mixed HP-UX 11i v2/v3 vPars Environments
You can now have a vPars A.05.01 monitor and database that simultaneously supports
virtual partitions running vPars A.05.01 on HP-UX 11i v3 (11.31) and virtual partitions
running vPars A.04.02 or above on HP-UX 11i v2 (11.23). For detailed information, see the
“Mixed HP-UX 11i v2/v3 vPars” section in the “Planning” chapter of the HP-UX Virtual
Partitions Administrator Guide.
• Obsolescence Notes
vPars A.03.02 is no longer supported. See “Obsolescence of vPars Releases” (page 20).
Servers that are not nPartitionable are not supported under A.05.01. These servers are the
rp5470/L3000, rp5405, and rp7400/N4000. See “Servers” (page 25). These servers remain
supported for A.03.xx and A.04.xx.
vPars A.04.xx Releases
vPars A.04.07 There are no new or changed features in the vPars A.04.07 release.
vPars A.04.06 The following features are new with the vPars A.04.06 release:
• Enhanced dynamic vPars support with Oracle Real Application Clusters (RAC) on HP 9000
PA-RISC servers
NOTE: This functionality is already available on vPars A.04.04 for Integrity servers.
• PCIe SAS support and tape recovery feature on Integrity servers
vPars A.04.06 on HP Integrity platforms enables you to use SAS disks as boot devices in
vPars environment.
IMPORTANT: In certain situations while using vPars with SAS disks as boot disk on HP
Integrity platforms, the vparstatus -v and setboot commands may show different
boot disk paths in vPars mode. This behavior is normal, and is due to the disks being scanned
in a different sequence at boot time. This behavior also occurs when you boot into nPars
mode and then boot back in vPars mode.
For example:
1. A virtual partition is ignited from a SAS disk and booted in vPars mode, and the
vparstatus -v command displays the boot disk path as A.
2. If the system is booted back to nPars mode, the boot path may change to B, which is
different from A due to a different scan order. This would also change the boot path to
B in the vPars database (/stand/vpdb).
3. After booting back to vPars mode, the vparstatus -v command for this virtual
partition shows B as the boot path and the setboot command still shows A. Both boot
paths (A and B) refer to the same SAS disk path.
vPars A.04.05 vPars A.04.05 adds support for the following:
14 Overview of Virtual Partitions