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

System Configuration
=====================
Locality Domain Count: 4
Processor Count : 15
Domain Processors
------ ----------
0 0 2 4 6
1 8 10 12 14
2 16 18 20
3 24 26 28 30
5.2.1 Online CPU migration
vPars V6.1 and later supports online migration of CPUs. This means you can add and delete CPU
from a live vPar without having to reboot it. During addition, free CPUs from the vPar and Integrity
VM guest pool are added to the vPar. When deleted from the vPar, the CPUs return to the vPar
and Integrity VM guest pool. You can use the vparmodify command to change the number of
CPU cores assigned to the vPar.
The vPars V6 product supports dynamic CPU addition and deletion. The selection criteria for CPU
addition are performed from within the VSP based on LORA CPU OLD policy policies. The selection
criteria for CPU deletion is performed from within the HP-UX instance that is target of the CPU
deletion. The following criteria are used to select the CPU cores to be deleted:
• Only cores in the default pset (see psrset(1M)) can be dynamically removed.
• The monarch core can never be deleted.
• If the default pset does not contain enough cores to satisfy a full request to reduce the number
of cores, the processor assignments will remain unchanged.
• Processors can be moved to the default pset and then deleted.
For more information about illustration of the feature, see Section 13.16 (page 245).
5.2.2 Transforming vPar to a VM guest
For better flexibility, you could transform a vPar into a VM guest offline. Use the hpvmmodify
-x vm_type=shared command to transform a VM guest into a vPar. For more information about
transforming vPar to a VM guest, Section 13.5 (page 221).
5.2.3 Hyperthreading for vPars
Hyperthreading is supported in individual vPars. By default, the VSP has the hyperthreading
(firmware setting) ON in the npartition or server, whereas the lcpu_attr tunable is OFF in the
VSP. The setboot command, when run on an individual vPar shows that HT is ON. You can turn
on lcpu_attr in an individual vPar using the kctune command. By default, lcpu_attr is OFF
in the vPar (default behavior of HP-UX). Note that even when lcpu_attr is OFF in the VSP, each
vPar can have its individual lcpu_attr enabled to use the hyperthreading functionality in the
vPar.
5.2.4 Handling Local MCA
For a general overview of MCAs on Itanium based systems, see Section 5.1.6 (page 54).
vPars V6.x operate with actual processor and related hardware. Consequently, MCAs encountered
by vPars are handled by the hardware, VSP (host) operating system, and system virtualization
components, working together.
On a system running vPars V6.0, any MCA encountered in an individual vPar (or the VSP) results
in a system crash that brings down all of the vPars. Starting vPars V6.1.5, a certain class of
56 CPU and Memory