HP Integrity Virtual Machines 4.3: Installation, Configuration, Administration

— PHCO_41595
— PHNE-41452
• The virtual iLO Remote Console's SSH server host keys can change.
When an SSH client connects to an SSH server, the client downloads the server's host keys
and keeps a local copy (usually in a file such as ~/.ssh/known_hosts). On subsequent
connections, the SSH client verifies that the host key sent by the server matches the local
copy. If the keys does 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 VM Host system are not
automatically migrated to the target VM Host system during Online VM Migration (OVMM).
You must manually add any guest administrator accounts to the target VM Host system,
using the same useradd commands performed on the source system. For information about
creating guest administrator and operator accounts, see (page 152).
• The virtual iLO Remote Console does not support rlogin connections.
8.9 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.
8.10 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. In this
release of Integrity VM, dynamic memory is available on HP-UX guests only.
An example of this feature allows a guest that is a Serviceguard 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 use dynamic memory, the guest must have the guest management software installed, as
described in Section 4.4 (page 76).
8.10.1 Managing Dynamic Memory from the VM Host
On the VM Host, the dynamic memory software is included with Integrity VM. 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. Table 8-4 provides a complete list
of -x keywords used for dynamic memory.
8.9 Guest Configuration Files 159