HP-UX Virtual Partitions Administrator Guide - Hewlett Packard

EFI and Integrity Notes
• EFI Shell Accessibility After the vPars Monitor (/stand/vpmon) is booted, the EFI shell
will not be accessible. This includes using hpux.efi and other EFI commands.
If you need to perform any EFI functions, you will need to shut down all the virtual partitions
and reboot the nPartition to access the EFI shell.
• New vPars Commands The vPars commands introduced in vPars A.04.01 for use on only
Integrity systems are vparenv, vparconfig, and vparefiutil:
vparenv HP-UX shell command that allows you to set the mode (vPars or nPars)
for the next reboot of the nPartition or to set the memory granularity unit
size in firmware.
vparconfig EFI command that allows you to set the mode (vPars or nPars) and
forces a reboot of the nPartition.
Note that vparconfig is not a built-in EFI command; you will need to
go to the fsN:\> disk prompt to execute this command.
vparconfig is installed in the EFI partition of the root disk when vPars
is installed. Specifically, the file is vparconfig.efi and is installed in
\efi\hpux.
vparefiutil HP-UX shell command to display or manage the HP-UX hardware path
to EFI path mappings of bootable disks within the vPars database.
When booting the vPars Monitor from EFI (boot /stand/vpmon), the backspace key
sometimes is not parsed correctly; if the command fails, try again without backspacing.
For more information on:
— using vparenv or vparconfig to switch modes, see “Modes: Switching between
nPars and vPars Modes (Integrity Only)” (page 126).
— using vparenv and granularity, see “Memory: Granularity Concepts” (page 226).
— using vparefiutil, see “EFI Boot Disk Paths, including Disk Mirrors, and
vparefiutil (Integrity Only)” (page 130).
• CPUs and Deconfiguration If a CPU is marked for deconfiguration using an EFI command
and the nPartition is not rebooted (for example, the vPars Monitor is immediately booted),
the vPars Monitor will not know or indicate (including with vparstatus) that the CPU
has been marked for deconfiguration and will use the CPU like any other working CPU.
• EFI Variables and Switching Modes
NOTE: The following EFI settings behavior does not occur when using vPars A.05.01 or
later, vPars A.04.04 or later, and the system firmware required for those vPars releases. See
the HP-UX Virtual Partitions Ordering and Configuration Guide for minimum firmware version
details.
The default EFI settings in nPars mode will be inherited when switched to vPars mode.
However, when switching back to nPars mode, any EFI settings will be reset to the
nPartition defaults, unless otherwise noted (for example, memory granularity). This includes
the primary and alternate paths (HAA (High-Availability Alternate) is not supported).
Even if you use parmodify to change the paths, parstatus will show them as set; however,
once the system is booted into nPars mode, those changes by parmodify are not retained.
For more information on switching modes, see the manpage vparenv(1M).
Also, while running in vPars mode, the EFI device path of a boot device, specifically the
vPars Monitor boot device, can be changed when the boot device is reformatted due to an
installation (either cold or Ignite-UX). The associated EFI boot path is updated to use the
EFI and Integrity Notes 37