HP-UX HB v13.00 Ch-17 - vPars

HP-UX Handbook – Rev 13.00 Page 17 (of 46)
Chapter 17 Virtual Partitions (vPars)
October 29, 2013
Required Patch Bundles
vPars A.05.xx: There are no patch bundles required for vPars. However, the vPars A.05.01
release requires the patch PHSS_36739 to resolve issues with the vPars dynamic memory
migration feature. This patch fixes JAGag43006 (“Memory got removed from an active partition
during memory OLA”). The patch is available at the HP IT Resource Center (at
http://itrc.hp.com, select “maintenance and support for hp products”).
vPars A.04.xx: From the HP-UX 11i v2 (11.23) Update Release, verify the following
 FEATURE11i (with required patches for vPars install)
 HWEnable11i (with required patches for new hardware)
 QPKAPPS & QPKBASE (with recommended patches)
 OnlineDiag, nPar, iCAP, WBEM, and other bundles (with changes).
See the version specific HP-UX Virtual Partitions Release Notes for further required patches.
vPars A.03.xx: After installing HP-UX 11i v1 (11.11), you should install the latest HP-UX 11i
v1 Support Plus CD or online at http://itrc.hp.com.
Difference between PA-RISC and Integrity Severs
One major difference between PA-RISC and Integrity systems is the LAN card in use, when
using vparboot –I and an Ignite server to install vPars,
On PA-RISC systems, the install kernel WINSTALL and the install file system WINSTALLFS are
transferred to the vPars monitor via the running vPar’s LAN card contacting the Ignite-UX
server. They are then placed into the memory of the target vPar by the vPar monitor. The target
vPar boots up using WINSTALL and WINSTALLFS to communicate with the Ignite-UX server to
continue installation.
On Integrity servers, the vparboot command triggers the monitor to execute a lanboot select
in the EFI shell. It prompts the user to select one of the LAN cards of the target vPar to be used
for installation (it is required to use Ctrl-A to switch to the target console to do this selection).
The difference between vPar mode and nPar mode is also new to Integrity systems. To run vPars
on an Integrity server it is required to set the firmware in vPar mode. This can be done either by
vparenv allowing you to set the mode (vPars or nPars) for the next reboot of the nPar, or by
setting the memory granularity unit size in the firmware. Example: