Reconfiguring vPars v6 memory with zero downtime

11
Addition of base and oating memory to a live vPar
Depending on the memory usage characteristics of a given vPar, the system administrator may decide to add just base
memory or just oating memory or both at once. In the following example, we add 1 GB of Base memory and 2 GB of
oating memory to vPar0001.
# vparmodify -p 1 -a mem::1G -a mem::2G:f
vparmodify: A Memory OLAD operation has been initiated for this vPar.
Please check vparstatus output or syslog for completion status.
# vparstatus -p 1 -v
[Virtual Partition Details]
Number: 1
Name: vPar0001
RunState: UP
State: Active
…
[Memory Details]
Total Memory(MB): 7232
Floating Memory(MB): 2048
…
[Memory OL* Details]
Operation : MEM change
Base Memory(MB) : 1024
Floating Memory(MB) : 2048
Status: PAS S
# hpvmstatus -s
…
Total memory allocated for vPars and VMs = 57280 Mbytes
Memory in use by vPars and VMs = 57280 Mbytes
Available memory for vPars and VMs = 0 Mbytes
…
Deletion of oating memory from a live vPar
When there is a need to free up some memory from a live vPar, the system administrator could review the memory
requirements and memory usage on various guests (using tools like glance) and choose a vPar from where some oating
memory could be freed up.
NOTE
Care should be taken such that deletion of oating memory from a vPar does not cause a memory pressure situation in
it. So, choose a vPar that is lightly loaded with respect to memory at the time of memory deletion.
Technical white paper | HP-UX vPars and Integrity VM v6.2