Reconfiguring vPars v6 memory with zero downtime

12
In the following example, we delete 1 GB of oating memory from vPar0001. Before the operation, we check the
memory conguration of vPar0001.
# 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
Now, we issue the command to delete 1 GB of oating memory from it.
# vparmodify -p 1 -d mem::1G:f
vparmodify: A Memory OLAD operation has been initiated for this vPar. Please
check vparstatus output or syslog for completion status.
The progress of the operation can also be monitored from the vPar using evmget | evmshow commands as follows:
# evmget | evmshow
…
OLAD: The olad infrastructure is locked and ready to accept parameters for the
operation. No other olad operations may be initiated on this nPartition until the
operation is complete. The sequence number for this operation is 3.
OLAD: The olad infrastructure has set the parameters for the operation. The
sequence number is 3 and the parameters are “MemSize=0x40000000, Loc=-2,
NumReq=1”.
OLAD: The olad infrastructure has started the requested operation with sequence
number 3.
…
OLAD: The olad infrastructure has completed the kernel portion of the requested
operation.
OLAD: The olad infrastructure is now unlocked and able to perform a new online
operation.
Now, looking at vparstatus output from the VSP for this guest, we see the updated conguration.
# vparstatus -v -p 1
[Virtual Partition Details]
Number: 1
Name: vPar0001
RunState: UP
State: Active
…
[Memory Details]
Total Memory(MB): 6208
Floating Memory(MB): 1024
…
[Memory OL* Details]
Operation : MEM change
Base Memory(MB) : 0
Floating Memory(MB) : 1024
Status: PAS S
Technical white paper | HP-UX vPars and Integrity VM v6.2