HP-UX vPars and Integrity VM V6.3 Administrator Guide

Total Memory (MB): 2048
Floating Memory (MB): 0
.......
The overall memory available in the guest pool for memory allocation can be viewed by the
following vparstatus command:
# vparstatus -A
........
[Available Memory]: 411968 Mbytes
........
Now, the vpar1 guest is booted.
# vparboot -p 1
(C) Copyright 2000 - 2012 Hewlett-Packard Development Company, L.P.
Mapping vPar/VM memory: 2048MB
......
vparboot: Successful start initiation of vPar or VM 'vpar1'
At this point, you will notice that the overall memory available in the guest pool is reduced as some
memory is used for booting the vpar1 guest.
# vparstatus -A
......
[Available Memory]: 409792 Mbytes
.......
The following shows the vparmodify command that is used to add 4 GB of base memory and
4 GB floating memory to the vpar1 guest online.
# vparmodify -p 1 -a mem::4G -a mem::4G:f
vparmodify: A Memory OLAD operation has been initiated for this vPar.
Please check vparstatus output or syslog for completion status.
You can verify the Memory OL* completion status as follows:
# vparmodify -p 1 -v
[Virtual Partition Details]
Number: 1
Name: vpar1
RunState: UP
State: Active
.......
[Memory Details]
Total Memory (MB): 10240
Floating Memory (MB): 4096
......
[Memory OL* Details]
Operation: MEM change
Base Memory (MB): 4096
Floating Memory (MB): 4096
Status: PASS
........
You can also find information about the completion status in the guest log file:
# tail /var/opt/hpvm/guests/vpar1/log
......
Trying to add Base: 4096 MB, Float: 4096 MB
Added Base 4096 MB, Float: 4096 MB
You can verify the new size of the vpar1 guest by using the vparstatus command.
# vparstatus
........
[Virtual Partition Resource Summary]
Virtual Partition CPU Num Num Total MB Floating MB
Num Name Min/Max CPUs IO Memory Memory
244 Managing vPars and VMs using CLI