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

HP-UX Handbook – Rev 13.00 Page 10 (of 46)
Chapter 17 Virtual Partitions (vPars)
October 29, 2013
 Minimum Requirements for each vPar:
 One processor;
 enough physical memory to run HP-UX 11i and applications; recommended 1GB of
memory available per each installed CPU;
 one unique LAN card recommended (on a PCI bus/Local Bus Adapter LBA uniquely
owned by the vPar), because each vPar has an independent kernel and works as a separate
system;
 one unique boot device (connected through SCSI or Fiber Channel card, on a PCI
bus/Local Bus Adapter uniquely owned by the vPar).
Each virtual partition requires its own installation.
The partitions should run the same HP-UX revision, but they may have different patch levels.
Starting with vpars Version 5.0, different HP-UX releases and vPars versions are supported. In
some cases, vPars software is sensitive to firmware revisions.
Comparison between vPars on PA-RISC and Integrity
Booting
 Mode: vPars or nPars mode has to be set on Integrity to be able to boot the nPartition into
standalone (nPars) or vPars environment (see below “Switching between vPar and nPar mode -
Integrity only”). PA-RISC does not require setting a mode.
 LAN card: Performing vparboot -I on Integrity uses the LAN card of the target
partition to obtain the bootable kernel. On PA-RISC, the LAN card of the source partition is
used. See also “Installing and Managing HP-UX Virtual Partitions”, section “Ignite-UX, the
LAN, the LAN card, and vparboot -I”, p. 65.
 Boot string: On Integrity platforms, the boot string used at the hpux.efi prompt (hpux>)
is “boot vpmon”. On PA-RISC, the boot string at the boot prompt (HPUX>) is “hpux
/stand/vpmon”.
vPars Commands
Integrity only
 vparefiutil: Unix shell command to display or manage the HP-UX hardware path
to EFI path mappings of bootable disks within the vPars database.