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

NOTE: You can achieve higher guest performance for HP-UX 11i v3 guests older than the March
2011 release by configuring as many AVIO storage adapters as the number of virtual CPUs in
the guest. The pcibus, pcislot, and aviotgt portions must be explicitly specified for each
device. For example, a resource statement for a 4–vCPU guest takes the following form:
-a disk:avio_stor:1,0,0:disk:/dev/rdisk/disk1
-a disk:avio_stor:1,1,0:disk:/dev/rdisk/disk2
-a disk:avio_stor:1,2,0:disk:/dev/rdisk/disk3
-a disk:avio_stor:1,4,0:disk:/dev/rdisk/disk4
These are not the requirements for guests that are at the March 2011 or later releases.
NOTE: A DMP device can be added to a vPar or a VM guest only when the vPar or VM guest
is offline. If you attempt the operation while the vPar or VM guest is online, the addition fails and
the new device addition does not get saved to the guest configuration to be applied when the
guest is next restarted. You have to repeat the device addition after the vPar or VM guest is shut
down.
6.5.2.2 Deleting storage devices
A VSP administrator deletes or detaches vPar or VM guests storage using the hpvmstatus and
hpvmmodify or vparmodify commands. vPar or VM guests storage devices can be deleted or
detached while the VM is powered on or off. A vPar or VM storage adapter can only be removed
when it is off. The vPar or VM guests storage adapter is automatically removed when the last vPar
or VM guests storage device connected to the adapter is removed.
NOTE: Devices configured under legacy AVIO virtual HBAs cannot be deleted (using the
hpvmmodify or vparmodify commands) if the vPar or VM guest is at EFI.
To delete or detach a virtual storage device from a vPar or VM guest:
1. Use the hpvmstatus command to locate the resource to verify whether the vPar or VM is
powered on. If the vPar or VM is on, consult with the guest administrator to obtain permission
to remove the resource before proceeding. If the vPar or VM is on, the following must be done
before the deletion of the device if it is under a legacy AVIO vHBA.
a. Run ioscan —kfNC tgtpath or ioscan —kfNC lunpath in the vPar or VM to obtain the
tgtpath or lunpath hardware path for the device to be deleted.
b. Remove the device in the vPar or VM by using the rmsf -H on the lunpath or tgtpath
hardware path.
2. Use the hpvmmodify command to delete or detach the resource.
The resource statement for deleting a vPar or VM guest storage device does not require virtual
hardware addressing. For example:
# hpvmstatus -P myvmm
...
[Storage Interface Details]
...
disk avio_stor 0 1 0 0 0 disk /dev/rdisk/disk5
disk avio_stor 0 1 0 1 0 disk /dev/rdisk/disk7
disk avio_stor 0 1 0 2 0 disk /dev/rdisk/disk9
disk avio_stor 0 5 0 0 0 disk /dev/rdisk/disk11
# hpvmmodify -P myvmm -d disk:avio_stor::disk:/dev/rdisk/disk7
# hpvmstatus -P myvmm
...
[Storage Interface Details]
disk avio_stor 0 1 0 0 0 disk /dev/rdisk/disk5
disk avio_stor 0 1 0 2 0 disk /dev/rdisk/disk9
To delete an AVIO storage device, specify the following:
6.5 Using vPars and Integrity VM storage 95