Migrating vPar Systems to Integrity VM

5 of 13
technical support for advice in addressing your particular configuration. (Note that lvlnboot will
fail if you did not specify a ‘boot’ volume group.)
Key to Smooth Transition – Collecting Root Volume Group Configuration
Collecting and saving the root volume group information is critical to an
easy transition from virtual partitions to virtual machines (and vice-versa).
Collect the volume group map and physical volume information. In the case of the root volume
group, be sure to save the output files to the root file system – having them there for single user mode
access will be critical to successfully booting the virtual machine later.
# vgexport -p -m /mapfile.vg00 /dev/vg00
vgexport: Volume group "/dev/vg00" is still active.
# vgexport -p -f /pvs.vg00 /dev/vg00
vgexport: Volume group "/dev/vg00" is still active.
File System Information
Finally, collect information useful in correlating file systems to volume groups. Either bdf or df will
suffice for this.
# bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 524288 283336 239088 54% /
/dev/vg00/lvol1 327680 161328 165104 49% /stand
/dev/vg00/lvol8 4718592 1984688 2719576 42% /var
CPU and Memory Information
Other critical pieces of information needed are the memory size and the number of CPUs. Both of
these can be easily obtained from the output of vparstatus. For example,
# vparstatus
[Virtual Partition]
Boot
Virtual Partition Name State Attributes Kernel Path Opts
======================== ===== ============ ==================== =====
vpolyd02 Up Dyn,Auto,Nsr /stand/vmunix
[Virtual Partition Resource Summary]
CPU Num Num Memory
Granularity
Virtual Partition Name Min/Max CPUs IO ILM CLM
======================== ======= ==== ==== ========== ==========
vpolyd02 1/ 12 1 2 128 128
Memory (MB)
ILM CLM
# User # User
Virtual Partition Name Ranges/MB Total MB Ranges/MB Total MB
======================= ====================== ======================
vpolyd02 0/ 0 1024 0/ 0 0
From this, one can clearly determine that the virtual partition ‘vpolyd02’ has 1 CPU and 1024 MB of
memory allocated to it.