Reconfiguring vPars v6 memory with zero downtime
14
Using memory deleted from a vPar to start a VM guest
Here, we illustrate the point that memory can be freed from a vPar and be used by the system administrator to start a VM
guest that did not have enough memory initially to start.
# hpvmstatus
[Virtual Machines]
Virtual Machine Name VM # Type OS Type State #VCPUs #Devs #Nets Memory
==================== ==== ==== ===== ======= ===== ===== ===== ========
vPar0003 3 VP HPUX On (OS) 1 1 1 9216 M B
SHVM0005 5 SH HPUX On (OS) 1 1 1 9 GB
SHVM0006 6 SH HPUX On (OS) 1 1 1 9 GB
SHVM0007 7 SH HPUX
Off
1 1 1 4 GB
vPar0001 1 VP HPUX On (OS) 1 1 1 6208 MB
vPar0002 2 VP HPUX On (OS) 1 1 1 10240 M B
vPar0004 4 VP HPUX On (OS) 1 1 1 9216 M B
# hpvmstatus -s
…
Total memory allocated for vPars and VMs = 57280 Mbytes
Memory in use by vPars and VMs = 55104 Mbytes
Available memory for vPars and VMs = 2176 Mbytes
Available memory for 9 (max avail.) CPU VM = 2048 Mbytes
Available memory for 9 (max avail.) CPU vPar = 2048 Mbytes
…
As seen in the above output, currently there is insucient memory to start the VM guest SHVM0007. So, when we try to
start it, it fails as expected.
# hpvmstart -p 7
vPar/VM SHVM0007 conguration problems:
Error 1: There is insufcient free pool memory for this vPar or VM (2048 MB
available, reduce size by 2048 MB to continue).
hpvmstart: Unable to continue.
Now, we will free up some oating memory from one of the vPars and that will then be later used to start this VM guest
successfully.
# vparstatus -v -p 2
[Virtual Partition Details]
Number: 2
Name: vPar0002
RunState: UP
State: Active
…
[Memory Details]
Total Memory(MB): 11264
Floating Memory(MB): 5120
# vparmodify -p 2 -d mem::2G:f
vparmodify: A Memory OLAD operation has been initiated for this vPar. Please
check vparstatus output or syslog for completion status.
Technical white paper | HP-UX vPars and Integrity VM v6.2