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

Example 26 Create a vPar with virtual network interface backed by a DIO function
Add the DIO function “0/0/0/4/0/0/0” to the direct I/O pool using the hpvmhwmgmt command:
# hpvmhwmgmt -p dio -a 0/0/0/4/0/0/0
Create a vPar named Oslo in the local system, specifying memory of 2 GB, 2 CPUs, and virtual
network interface backed by a DIO function “0/0/0/4/0/0/0”.
# vparcreate -p Oslo -a mem::2048 -a cpu::2 -a lan:dio::hwpath:
0/0/0/4/0/0/0
For more information about configuration of guests with DIO functions, see Section 8.5 (page 127).
10.2 Booting a vPar
You can boot and manage vPars using the same storage media and procedures that you would
use if the vPar operating system were running on its own dedicated physical hardware platform.
You can allocate administration privileges to specific vPar administrators.
To boot a vPar, the vPar must be in the DOWN run state. To boot a vPar, you must run the
vparboot command or provide the -c “pc –on” parameters to the vparconsole command.
Each vPar has a console, and you can access the console from the VSP using the vparconsole
command. Start the console before you run the vparboot command if there is a need to interact
with EFI. You can also provide the -f -i-c “pc –on” parameters to the vparconsole command
to start, and enter the console in interactive mode right after the start.
Example 27 Boot the vPar called Oslo
# vparboot -p Oslo
OR
# vparconsole -P Oslo -f -i -c 'pc -on'
For more information about installation of guest OS on vPar, see Chapter 2 (page 29).
10.3 Modifying a vPar
You can modify all the attributes that you specify while creating a vPar. You can rename the vPar,
modify the resources, and change group and user level authorization. Some attributes can be
modified dynamically, that is, a reboot is not required, while others require a reboot.
The vparmodify command must be run from the VSP just as the vparcreate command.
The same options used for creating a vPar are applicable for modifying the vPar.
10.3.1 Modifying CPU and Memory resources dynamically
Since vPars and Integrity VM V6.2, you can modify CPU cores and memory dynamically. You can
change the CPU core count of a vPar while it is running. Do not reboot the vPar after you modify
the CPU core count. You can add base and floating memory to vPar while it is running. You cannot
change CPU and MEM online at the same time. For more information about base and floating
memory, see Section 5.6.3.3 (page 60).
NOTE: Base memory can be removed only when the vPar is DOWN.
10.3.2 Modifying I/O resources statically
Starting with vPars and Integrity VM V6.3, IO devices can be added to a vPar dynamically.
For more information about IO devices, see Chapter 6 (page 63).
158 Administering vPars