HP vPars and Integrity Virtual Machines V6.1 Administrator Guide

the activation of the cores on the vPar v6.x guest OS. Similarly, for a deactivation operation,
execute the vparmodify command on the vPar v6.1 guest OS and then execute a
icapmodify command on the VSP OS.
iCAP commands issued from the OA activate or deactivate cores only in the VSP. vparmodify
commands have to be issued in the VSP to move the core to and from a vPar v6.1. If there is
only one core in the VSP and the rest assigned to vPars a deactivation request from the OA
will fail. Cores must first be deactivated from the vPar v6.1 by issuing the vparmodify
command on the VSP followed by an icapmodify command to deactivate the core from the
VSP.
TiCAP is consumed once the core is active at either the VSP or vPar v6.1. If TiCAP is being
used, to stop consuming TiCAP, the core must be deactivated from the vPar v6.1 as well as
the VSP.
1.10 Attributes that can be changed dynamically
A dynamic change does not require a reboot of the virtual environment in question. The following
attributes can be changed dynamically:
Table 1 Attributes changed dynamically
VMsvParsAttribute
1. Yes
2. Yes
3. No
1. N.A.
2. No
3. Yes
CPU
1. Adding or removing vPar/VM
vCPU entitlement. The default is
uncapped mode. In uncapped
mode, this is also automatic based
on overall “free” entitlement.
2. Enabling or disabling vCPUs from
within a vPar/VM.
3. Adding or removing CPUs to and
from a vPar/VM from the VSP.
YesNoMemory
• Adding or removing the memory
in use by a vPar/VM. This can also
be made automatic with AMR
(Automatic Memory Reallocation)
based on overall "free" memory.
YesYesNetwork
• Adding or removing virtual
switches (vswitches) on the VSP.
YesYesStorage
• Adding or removing storage to or
from a vPar/VM.
NOTE: Depending on the type of
storage being used, there may be
additional steps required. See
Section 9.2.1.5 (page 121)
1. Yes
2. Yes
1. No
2. Yes
Migration
1. Migrating online.
2. Migrating offline.
NOTE: Before you add or remove memory, networking, or storage from a vPar or a VM, be sure
you know if further action is required on the vPar or VM.
1.10 Attributes that can be changed dynamically 23