Example System

Assume our example system is:

an Integrity server
running vPars A.05.01
where the firmware requires 64 MB of cell memory per cell
with 2 cells
containing 8 GB of total memory consisting of:
- 4 GB of ILM
- 4 GB of CLM (2 GB from each cell)
with 2 virtual partitions booted with each virtual partition assigned:
- 2 GB of ILM
- 2 GB of CLM

Then, the memory not available to the virtual partitions’ OS and applications would consist of the following:

From a vPars perspective, this means the following:

The vPars Monitor resides in fpar0.
Virtual partition 1 sees 4064 MB of memory:
4096 - 32 (fpar1) = 4064 MB
Virtual partition 2 sees 3424 MB of memory:
4096 - 32 (fpar2) - 384 (fpar0) - 128 (fpardump) - 128 (nPartition firmware) = 3424 MB
If all the memory in the nPartition is divided among all the virtual partitions, then during vPars Monitor boot, the last virtual partition in the nPartition gets the memory that remains after memory taken by firmware and the vPars Monitor.
Available ILM memory:
4096 (2048 from each cell) - 384 (fpar0) - 128 (fpardump) - 32 (fpar1) - 32 (fpar2) = 3520 MB of available ILM
Available CLM memory:
2048 - 64 (64 from each cell) = 1984 MB of available CLM for each cell

Technical documentation