HP-UX vPars and Integrity VM V6.3 Administrator Guide

boot on the VSP. The memory used by HP-UX to boot depends on the size of the system, including

total memory, number of cores, and the I/O devices on the system.

This equation indicates the following:

The overall VSP memory overhead = Amount of memory HP-UX requires to boot up + Free memory

remaining in the VSP for optimal functioning of VSP

VSP memory overhead = ~1500 MB + 8.5% of total physical memory

To see how much memory is available for vPars and Integrity VM memory pool size, enter the

following command:

# hpvmhwmgmt -p memory -l

NOTE:

• The calculation for how much memory is in VSP versus what is available for vPars and VM

guests is done at product start time.

• In addition to the VSP memory overhead, individual vPars and VM have a memory overhead

depending on their size. For more information about memory, see Chapter 5 (page 53).

3.4 Reserving VSP devices

HPVM protects all the VSP system resources during the product start automatically, by marking

them as restricted devices. This helps to protect storage and networking resources used by the VSP

against unintended usage and corruption by vPars or VM guests. Any additional resources added

to the VSP can be similarly protected against vPar or VM guest access.

The hpvmdevmgmt command allows you to mark the restricted devices.

Example 1 Example of restricting a device

You can reserve the disk storage on which the VSP operating system and swap space reside. This

prevents guests from accessing the same disk storage devices.

For a sample device /dev/rdisk/disk1, enter the following command:

# hpvmdevmgmt –a rdev:/dev/rdisk/disk1

To complete the restriction of volumes, each device included in the volume must also be restricted.

3.5 Configuring storage space for diagnostic data

It is necessary to provide sufficient storage space on the VSP to gather crucial diagnostic data, if

problems are encountered. Table 7 (page 40) lists the major types of diagnostic data for which

sufficient storage space must be allocated.

Table 7 Types of diagnostic data

Storage locationDiagnostic data type

/var/tombstones/Firmware diagnostic data for the VSP

/var/adm/crash/HP-UX system diagnostic data, which consists of several

log files and crash-dumps

/var/opt/hpvm/common/hpvm_mon_logHPVM Monitor Log file records diagnostic information from

the Virtual Machine Monitor

/var/opt/hpvm/guests/<Guest-Name>/vm.coreHPVM Monitor Dump files created when a guest encounters

a fatal situation

The size of monitor dump file for any specific guest is roughly twice the value obtained from running

the following command:

40 Configuring VSP