HP Integrity Virtual Machines Installation, Configuration, and Administration

HElp - Display this screen
Q - Quit help
For more information about using the hpvmconsole command, see hpvmconsole(1M).
9.5 Guest Configuration Files
When the guest is created, the VM Host creates the guest configuration file
/var/opt/hpvm/guests/guestname.
Integrity VM creates up to three guest configuration files:
• The vmm_config.current file contains the current guest configuration currently set.
• The vmm_config.prev file contains the last known guest configuration settings.
• The vmm_config.next file contains the configuration settings that have changed since the
guest was started. To initiate these changes, you must reboot the guest.
Never modify the guest configuration files manually. Always use the appropriate Integrity VM
command (hpvmmodify or hpvmdevmgmt) to modify guest configuration parameters. Directly
modifying the guest configuration files can cause guests to fail in unexpected ways.
9.6 Dynamic Memory
Integrity VM allows you to dynamically modify the memory that the virtual machine can use.
Normally, guests use a fixed amount of memory. That memory is allocated when the virtual
machine is started and locked down so it cannot be paged or swapped. Once the memory is
locked down, the VM Host cannot make it available to other virtual machines. Therefore, the
VM Host supports a fixed number of virtual machines based on the amount of memory in the
VM Host system and the number and size of the virtual machines.
Dynamic memory is an optional feature of Integrity VM that allows you to change the amount of
physical memory in use by a virtual machine without rebooting the virtual machine. In this
release of Integrity VM, dynamic memory is available on HP-UX guests only. In order to use
dynamic memory, the guest must have the guest management software installed, as described
in Section 9.3: “Installing the Guest Management Software” (page 117).
For example, this feature allows a guest that is a Servicegard node to be used as a standby server
for multiple Serviceguard packages. When a package fails over to the guest, the guest memory
can be changed to suit the requirements of the package before, during, and after the failover
process.
To manage a guest's memory dynamically on the VM Host, see Section 9.6.1: “Managing Dynamic
Memory from the VM Host” (page 120).
To manage a guest's memory dynamically on the guest, see Section 9.6.2: “Managing Dynamic
Memory from the Guest” (page 124).
9.6.1 Managing Dynamic Memory from the VM Host
Manage dynamic memory on the VM Host using the —x option with the hpvmcreate,
hpvmmodify, or hpvmclone command. The —x option associates a variety of configuration
parameters with the guest, including dynamic memory and network management for the guests.
For a complete list of —x keywords used for dynamic memory, see Table 9-4.
By default, dynamic memory is not enabled. To manage a guest's memory dynamically, enter
the hpvmcreate, hpvmmodify, or hpvmclone command. Include the —x ram_dyn_type
option. Specify either any or driver as the argument to the option. For example, to use any
available dynamic memory support for the guest named compass1, enter the following command
on the VM Host:
# hpvmmodify -P compass1 -x ram_dyn_type=any
120 Managing Guests