HP vPars and Integrity Virtual Machines V6.1 Administrator Guide

connections, the SSH client verifies that the host key sent by the server matches the local copy.
If the keys do not match, the SSH client prints an error message.
The virtual iLO Remote Console uses the host system's SSH server host keys. If the guest is
migrated to another host system (using Online VM Migration), these host keys will change.
When an end user does an SSH connection, they will receive an error message. The end user
must manually delete the local copy of the host key. For additional information, see the ssh(1)
manpage .
• Guest Administrator accounts are not migrated during Online VM Migration (OVMM).
Any guest administrator accounts residing on the source VSP system are not automatically
migrated to the target VSP system during Online VM Migration (OVMM). You must manually
add any guest administrator accounts to the target VSP system, using the same useradd
commands performed on the source system. For information about creating guest administrator
and operator accounts, see (page 174).
• The virtual iLO Remote Console does not support rlogin connections.
11.8 Guest configuration files
When the guest is created, the VSP 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.
11.9 Dynamic memory
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.
NOTE: Dynamic memory is not available with vPars at this time.
An example of this feature allows a VM that is a Serviceguard node to be used as a standby server
for multiple Serviceguard packages. When a package fails over to the VM, the VM memory can
be changed to suit the requirements of the package before, during, and after the failover process.
To use dynamic memory, the VM must have the VirtualBase software installed, as described in
Section 8.3 (page 104). Note the management software is installed automatically with HP-UX 11i
v3 March 2012 VMs. If you are using VMs with HP-UX 11i v3 September 2011, you need to
install the VirtualBase software.
11.9.1 Managing dynamic memory from the VSP
On the VSP, the dynamic memory software is included with Integrity VM. Manage dynamic memory
on the VSP 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. Table 27 provides a complete list of -x keywords
used for dynamic memory.
180 Managing vPars/VMs