Reconfiguring vPars v6 memory with zero downtime

13
Cancelling a memory delete operation on a live vPar
As mentioned earlier, if a vPar is heavily loaded, the memory migration operation could take a long time to complete. In
such cases, you may choose to cancel the operation.
In the following example, we start a delete operation on a heavily loaded vPar and then successfully cancel it.
# vparstatus -p 3 -v
[Virtual Partition Details]
…
[Memory Details]
Total Memory(MB): 9216
Floating Memory(MB): 5120
Now, we initiate the deletion of 4 GB of oating memory from this vPar.
# vparmodify -p 3 -d mem::4G:f
vparmodify: A Memory OLAD operation has been initiated for this vPar. Please
check vparstatus output or syslog for completion status.
# vparstatus -p 3 -v
[Virtual Partition Details]
Number: 3
Name: vPar0003
RunState: UP
State: Active
…
[Memory OL* Details]
Operation : MEM change
Base Memory(MB) : 0
Floating Memory(MB) : 4096
Status: PENDING
…
As it is still in PENDING state, we can try to cancel the operation by using the vparmodify command.
# vparmodify -p 3 -C
vparmodify: A Memory OLAD cancel operation has been initiated for this vPar.
Please check hpvmstatus or vparstatus output for cancellation status.
# vparstatus -p 3 -v
[Virtual Partition Details]
Number: 3
Name: vPar0003
RunState: UP
State: Active
…
[Memory OL* Details]
Operation : MEM change
Base Memory(MB) : 0
Floating Memory(MB) : 4096
Status: CANCELLED
As seen above, we were able to cancel the delete operation successfully.
Technical white paper | HP-UX vPars and Integrity VM v6.2