Examples of Using the Calculations

Changing Dynamic Tunables

If you have already migrated to a vPars server and are adjusting the dynamic tunables of a kernel, check that there is an available memory range under the 2 GB boundary to accommodate the adjusted kernel. You should do this check after adjusting the dynamic tunables but before rebooting the partition.

For example, suppose you calculated the size of an adjusted kernel to be 64 MB. Using vparstatus -A, you can check whether there is an available memory range below the 2 GB limit to accommodate the kernel size:

# vparstatus -A
...
[Unbound memory (Base/Range)]:  0x40000000/256
                (bytes) (MB)

The output from vparstatus -A shows the following:

an available 256 MB memory range that can accommodate the 64 MB kernel and
an available memory range beginning at 0x40000000, which is below the 2 GB limit.

Therefore, the criteria will continue to be met after you reboot the partition.

Migrating OSs from non-vPars Servers to a vPars Server

If you are migrating from multiple non-vPars servers to one vPars server, sum up the results for all the kernels and ensure that the result is under 2 GB.^[5]

For example, if we calculated the size of the kernel of the first OS to be 64 MB and the second OS to be 128 MB, the sum is 192 MB. 192 MB is below the 2 GB limit, so we have met the criteria and can migrate the OSs from the multiple non-vPars servers to the single vPars server.




	NOTE: For vPars A.04 and later, you will need to accommodate for your granularity setting by rounding memory usage to the granularity boundary.

^[5]Because the vPars Monitor uses 64 MB, the actual number is 1984 MB.

Examples of Using the Calculations

Technical documentation

» Table of Contents

» Glossary

» Index

Changing Dynamic Tunables

Migrating OSs from non-vPars Servers to a vPars Server