Realize new workload migration and consolidation possibilities

7
Review the Virtual Partition command changes
The following changes have been made to the vPar commands. Please review these changes and make any necessary
adjustments to your system administration scripts and procedures that are necessary:
As of v6.1, all commands must be executed from the VSP. No vPar commands are available from the individual vPars.
As a result of this, there is no need for secure administration command options for the vPars.
As of v6.1, only HP-UX 11i v3 virtual partitions are supported. It is possible to maintain HP-UX 11i v2 environments if
you are willing to migrate to a standard Integrity VM guest. See the documentation at hp.com/go/hpux-hpvm-docs.
All vPartition commands and command flags that directly manage or interact with Extensible Firmware Interface (EFI)
and the system firmware have been removed. Examples include vparenv, vparefiutil, and the options used to manage
the EFI variables.
All command flags related to memory granularity have been removed. Memory is allocated to a vPar in multiples
of 64 MB.
Memory migration, and therefore, the base/floating memory concept, is not supported on v6.1 at this time.
The Integrity VM commands may also be used to manage the vPars (if desired).
The Integrity Virtual Server Manager GUI may be used instead of the command line interface (CLI).
The following list contains all of the supported commands:
vparboot
vparcreate
vparmodify
vparremove
vparreset
vparstatus
vparhwmgmt (new)
manages the pool of CPU resources dedicated for use by the virtual partitions
vparnet (new)
creates and manages the virtual network switches (vswitches)
vparconsole (new)
connects the user to the console of a virtual partition
The format of the I/O specifications in the commands has changed from hardware path to the Accelerated Virtual I/O
(AVIO) format used with Integrity VM:
[tape|change|burner|disk|hba|network]:[avio_stor|avio_net]:pcibus:pcislot:aviotgt: \
{physical device type}:{physical device path}
For more information, see the HP vPars and Integrity Virtual Machines V6.1 Administrator Guide available at
hp.com/go/hpux-vpars-docs.
On the Superdome 2, vPars v5 supports operations launched from the Onboard Administrator (OA). When interacting
with vPars in this manner, you must specify which nPartition you wish to work in. On vPars v6, all operations are run
from the VSP, which is inside of an nPartition, so the options used to specify the nPar ID have been removed.
In version 6, the vPars are automatically optimized for locality, thus there is neither need nor support for socket local
command options and output.
Command output format has been altered when necessary to adjust for the altered I/O format and capabilities, and
the removal of socket local specifications.
The
getconf
command will no longer return different values for
PARTITION_IDENT
and
MACHINE_IDENT
.