HP Integrity Virtual Machines Installation, Configuration, and Administration Version A.03.50

Table 3-5 Options to the hpvmmodify Command (continued)
DescriptionOption
Specifies whether the virtual machine is managed by Serviceguard or gWLM
(or both). For the argument, specify one or more of the following parameters:
• SG indicates that the VM Host is a Serviceguard cluster node.
• SG_pkgname indicates that the VM Host is a Serviceguard package.
• GWLM indicates that the VM Host is managed by gWLM.
• NONE indicates there are no external managers.
For a node that is managed by both Serviceguard and gWLM, parameters are
separated with a comma. For example: SG_compass1,gWLM. Do not specify
this option. This option is used internally by Integrity VM.
-i package-name
Specifies whether the virtual machine is a distributed guest (that is, managed
by Serviceguard) and can be failed over to another cluster member running
Integrity VM. Do not specify this option. This option is used internally by
Integrity VM.
-j [0|1]
Specifies values for dynamic memory setting associated with the guest,
including:
• dynamic_memory_control
• ram_dyn_type
• ram_dyn_min
• ram_dyn_max
• ram_dyn_target_start
For more information about dynamic memory, see Section 9.6 (page 130).
-x keyword=parameter
For example, to modify the characteristics of the problematic virtual machine compass1 to
remove vCPUs and memory, enter the following command:
# hpvmmodify -P compass1 -c 1 -r 2G
This command changes the following characteristics of the virtual machine named compass1:
• The -c 1 option specifies one vCPU.
• The -r 2G option specifies two GB of memory.
The hpvmmodify command generated no warnings, so the VM Host system is ready to start the
virtual machine.
After you make the necessary modifications, use the hpvmstart command to start the virtual
machine. For example:
# hpvmstart -P compass1
(C) Copyright 2000 - 2007 Hewlett-Packard Development Company, L.P.
Initializing System Event Log
Initializing Forward Progress Log
Opening minor device and creating guest machine container
Creation of VM, minor device 2
Allocating guest memory: 2048MB
allocating low RAM (0-40000000, 2048MB)
/opt/hpvm/lbin/hpvmapp (/var/opt/hpvm/uuids/8ba249f2-3399-11db-aacc-00306ef392e0
/vmm_config.next): Allocated 1073741824 bytes at 0x6000000100000000
locking memory: 0-40000000
allocating firmware RAM (ffaa0000-ffab5000, 84KB)
/opt/hpvm/lbin/hpvmapp (/var/opt/hpvm/uuids/8ba249f2-3399-11db-aacc-00306ef392e0
/vmm_config.next): Allocated 86016 bytes at 0x6000000140000000
locked SAL RAM: 00000000ffaa0000 (4KB)
locked ESI RAM: 00000000ffaa1000 (4KB)
locked PAL RAM: 00000000ffaa4000 (4KB)
locked Min Save State: 00000000ffaa5000 (1KB)
RAM alignment: 40000000
Memory base low : 6000000100000000
Memory base FW : 6000000140000000
Loading boot image
Image initial IP=102000 GP=62C000
Initialize guest memory mapping tables
3.4 Changing Virtual Machine Configurations 43