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

Example 14 Create a VM 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 VM 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”
# hpvmcreate -P Oslo r 2048 c 2 -a lan:dio::hwpath: 0/0/0/4/0/0/0
For more information about configuring VM guests with DIO functions, see Section 8.5 (page 127).
9.1.7 Specifying dynamic memory parameters
Specifies whether the new VM (shared VM type only) uses dynamic memory and the values
associated with it by including the following keywords:
dynamic_memory_control={0|1}
ram_dyn_type={none|any|driver}
ram_dyn_min=amount
ram_dyn_max=amount
ram_dyn_target_start=amount
ram_dyn_entitlement=amount
amr_enable={0|1}
amr_chunk_size=amount
For more information about using dynamic memory for guests, see Section 13.14.2 (page 235).
9.1.8 Configuration limits
Table 18 (page 137) lists the configuration limits for Integrity VM V6.3. For NPIV supported limits,
see Table 14 (page 102).
Table 18 Integrity VM V6.3 configuration limits
Support limitConfiguration item
32# vCPUs/VM — Maximum
20# vCPUs/pCPU — Maximum
254# VMs per VSP — Maximum
HP-UX limit# pCPUs in VSP
1 GBMemory per VM — Minimum (HP-UX 11i v2)
2 GB or the minimum required for HP-UX 11i v3 to bootMemory per VM — Minimum (HP-UX 11i v3)
256 GBMemory per VM — Maximum (HP-UX)
256 AVIO# virtual AVIO storage devices / VM or vPar— Maximum
62# virtual NICs / VM or vPar— Maximum
50# virtual switches — Maximum
511# virtual NICs / vswitch
30# file backing store devices / VM or vPar — Maximum
> 2TBMaximum size of backing store for AVIO (disk, lvol, file)
16Maximum # PCI functions per vPar/VM for DIO
9.1 Specifying VM attributes 137