Installing and Managing HP-UX Virtual Partitions (includes A.03.03)

How vPars and its Components Work

EFI and Integrity Notes

Chapter 2

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 Unix 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 Unix 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 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)” on page 93.

—using vparenv and granularity, see “Memory: Setting Granularity Values (vPars A.04)” on page 169.

—using vparefiutil, see “EFI Boot Disk Paths, including Disk Mirrors, and vparefiutil (Integrity

only)” on page 98.

• 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

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 incudes 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).