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

Use the hpvmdevinfo command to display the hardware device mapping between vPar or VM
and the VSP. You can run this command on the VSP or the vPar or VM:
VSP:
# hpvmdevinfo
Virtual Device Bus,Device,Target Backing Store Host Device Name Virtual Machine
Machine Name Type Type Name Device Name
============ ====== =================== ============= ================ ================
atcvpar2 disk [0,0,0] disk /dev/rdisk/disk13 /dev/rdisk/disk3
atcvpar2 disk [0,0,2] disk /dev/rdisk/disk21 /dev/rdisk/disk5
atcvpar2 hba [0,5] npiv /dev/fcd0 /dev/gvsd2
atcvpar2 lan [0,6,0x7E06F5393261] hwpath 0/0/0/4/0/0/0 0/0/0/6/0 (lan3)
vPar or VM:
# hpvmdevinfo
Device
Type Bus,Device,Target Backing Store Type Host Device Name Virtual Machine Device Name
===== ================= ================= ================ ===========================
disk [0,0,0] disk /dev/rdisk/disk13 /dev/rdisk/disk3
disk [0,0,2] disk /dev/rdisk/disk21 /dev/rdisk/disk5
hba [0,5] npiv /dev/fcd0 /dev/gvsd2
lan [0,6] hwpath 0/0/0/4/0/0/0 0/0/0/6/0 (lan3)
A.4 VSP (Virtualization Services Platform)
A.4.1 CPU or memory info in machinfo output on VSP could be confusing
The machinfo command displays system information from the HP-UX view of the system
configuration. The machinfo command might show different values based on when the command
is executed. If executed on the VSP after installing HP-UX and before installing the Integrity VM
software, machinfo shows all the sockets and logical processors. The logical processor count
represents cores if the kernel tunable lcpu_attr value is 0 and threads when lcpu_attr value
is 1. You can obtain the value of lcpu_attr by using the kctune command.
Note that lcpu_attr is set to zero in the VSP by default for optimal VSP performance, and so,
the logical processor count is always the CPU core count.
After the Integrity VM software is installed, the logical processor count of machinfo represents
the number of VSP logical processors and the logical processors in the vPar/VM pool, but not yet
activated in a vPar.
When a vPar is started, the logical processors in the vPar/VM pool assigned to the vPar are
deallocated from the VSP and the machinfo output in the VSP will reflect that reduction in logical
processor count.
When a vPar is stopped, the processor count shown in the VSP machinfo output will increase by
the number of CPUs assigned to the vPar.
The memory value displayed by the machinfo command shows the amount of memory that was
available to HP-UX when booted on the VSP. This memory value includes memory that is allocated
to the vPars and the memory used by the VSP. Unlike the logical processor count, the memory
amount does not change with the installation of the Integrity VM software.
As workaround, use the vparhwmgmt —p cpu —l command to view the number of processor
cores that are allocated to the VSP and to the vPar pool.
A.5 Performance
A.5.1 CPU intensive applications may not be responsive when the VSP is servicing
high I/O load for guests
Applications like SMH (which needs significant CPU bandwidth) are not likely to be very responsive
when the VSP cores are already under heavy load servicing vPar or VM I/O requests. HP
recommends that you increase the number of VSP CPU-cores under such circumstances.
272 Troubleshooting