HP Integrity Virtual Machines Release Notes

1.2 Using Linux Guests
This version of Integrity VM introduces support for Linux guests. You can install the RedHat
Linux Enterprise Edition Advanced Server Release 4 update 4 on a virtual machine.
For information about this Linux operating system, see www.redhat.com. Specifically:
• Red Hat Enterprise Linux 4 Installation Guide for x86, Itanium, AMD64
• Intel Extended Memory 64 Technology (Intel EM64T)
• Red Hat Linux Customization Guide
The guest parameter settings for Linux guests are listed in Table 3-1 (page 25).
For information about installing Linux guests, see the HP Integrity Virtual Machines Installation,
Configuration, and Administration manual.
1.3 Dynamic Memory
With this version of Integrity VM, system administrators can set memory parameters that allow
guest memory allocation to be changed dynamically; that is, without rebooting the guest.
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. The VM Host
supports a fixed number of running virtual machines based on the amount of memory in the
VM Host system and the number and size of the virtual machines.
Dynamic memory 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, the dynamic
memory feature is available on HP-UX guests only. In order to use dynamic memory, the guest
must have the guest management software installed.
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.
For information about enabling and using dynamic memory, see the HP Integrity Virtual Machines
Installation, Configuration, and Administration manual.
1.4 Creating Virtual Machine Administrator and Operator Accounts
In versions of Integrity VM prior to A.03.00, only Admin console access is available, and only
one such account per guest is allowed. The administrator account name must match the guest
name. The new version of Integrity VM provides proper access controls and individual
accountability for these accounts. For more information, see Section 6.3 (page 37).
1.5 Using P2V Workload Migration
The P2V assistant allows you to migrate an application from a discrete physical system or nPar
to a virtual machine. The P2V assistant consists of a set of scripts and tools that aid in this
migration. For more information, see p2vassist(1M).
1.6 Integrity VM Command Changes
The Integrity VM commands have changed in the following ways:
• The hpvmresources manpage, which describes the syntax for specifying storage and network
devices when creating or modifying a guest, has been moved from the (1M) volume to the
(5) volume.
• The new p2vassist(1M) manpage describes how to use the physical-to-virtual assistant toolkit
to migrate a workload from a discrete system (server or partition) to a virtual machine.
14 Introduction