Reconfiguring vPars v6 memory with zero downtime
Rate this documentShare with colleagues
Sign up for updates
hp.com/go/getupdated
© Copyright 2013 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. The only
warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein
should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors or omissions contained herein.
UNIX is a registered trademark of The Open Group.
4AA4-6165ENW, April 2013
Comparison with vPars A.05.xx
The following table lists some dierentiating points between the memory migration feature oered in the vPars v5
release and vPars v6.2 release.
vPars A.05.xx vPars v6.2
When not explicitly stated, the new memory for memory
addition is selected from ILM locality.
New memory is selected by the virtualization software based on
the locality proximity of the vPar and available free memory in the
vPar/VM memory pool.
Default memory granule size is 128 MB. The user has the
exibility to change it, but requires system reboot.
Memory granules size is xed at 64 MB.
User has the ability to specify: locality, memory ranges, base or
oating attribute for the memory migration operation.
User can only specify the required size and base or oating
attribute.
No limit on the amount of memory that can be added/deleted in
a single transaction.
Maximum memory that can be added or deleted is 16320 MB per
operation, when the vPar is online.
Memory migration operation can be initiated from any vPar
targeting any vPar on the same system.
Memory migration operation can be initiated from VSP targeting
any vPar on the VSP.
Learn more at
hp.com/go/vpars
Technical white paper | HP-UX vPars and Integrity VM v6.2