HP Integrity Virtual Machines Release Notes Version A.03.50

• Change to the hpvminfo command to display the information returned by the supported
public interfaces defined in /opt/hpvm/include/hpvm_api_public.h. For example,
when running on a VM host:
hpvminfo -S
HPVM Server information
VERSION: HPVM A.03.50 BL10 clearcase opt Wed Aug 01 2007 12h20m34s EDT
MY UUID: 58d03f5d-79ed-11d9-b720-17c097e9e0d0
When running on a guest:
hpvminfo -S
HPVM Guest information
VERSION: HPVM A.03.50 BL06 clearcase opt Mon Jun 11 2007 13h32m14s
SERVER HOSTNAME: test.case.com
• Storage used by the VM Host system is now better protected in this release. The new
hpvmhostrdev command identifies disks, LUNs, and logical volumes used by the VM
Host for its operating system, file system, and swap storage as "restricted devices" in the
Integrity VM device database. This prevents their use by virtual machines as storage, avoiding
inadvertent corruption or destruction of the VM Host's environment. When Integrity VM
starts on the VM Host system, it invokes the hpvmhostrdev command, automatically
adding these restricted devices to the Integrity VM device database. The hpvmhostrdev
command is based on the same storage analysis tools used by HP System Management
Homepage (HP SMH) and other Virtual Server Environment (VSE) management tools,
maintaining consistency across HP management products.
The hpvmhostrdev command can also be used by privileged users on the VM Host system
to update the Integrity VM device database. By default, the command forces a full hardware
scan on the VM Host system. Depending on storage and network configuration, the scan
might take several minutes to complete. This use might be prudent whenever new hardware
is added to the VM Host system. The hpvmhostrdev command also accepts the -u option,
which does not force a new HW scan, using the latest HW configuration information to
update the device database. The only other option accepted by hpvmhostrdev is -h,,
which provides a brief summary of the available options and their use.
Existing virtual machines using deprecated storage for virtual disks, partitions created with
idisk(1M) in particular, might not start after installing the latest release of Integrity VM.
You can alleviate this condition by removing the restricted device entry corresponding to
the base path of the disk that has been partitioned from the Integrity VM device database.
For example, if the disk /dev/rdsk/c2d3t4 has one or more partitions being used as
virtual storage, execute the command hpvmdevmgmt -d rdev:/dev/rdsk/c2t3d4 to
delete the device from being used as virtual storage. Note that the use of such partitions for
Integrity VM storage has been deprecated.
1.2 Using Linux Guests
This version of Integrity VM introduces support for SUSE Linux SLES 10 update 1 guests and
Red Hat Linux Enterprise Edition Advanced Server Release 4 update 5 and update 6. You can
install the SUSE Linux or the Red Hat Linux on a virtual machine.
For information about this Red Hat Linux operating system, see www.redhat.com. Specifically:
• Red Hat Enterprise Linux 4 Installation Guide for x86, Itanium, AMD64 and Intel Extended Memory
64 Technology (Intel EM64T)
• Red Hat Linux Customization Guide
NOTE: To use Red Hat Linux 4 update 6, you must install a patch on the guest. See Table 2-8
(page 27).
For information about the SUSE Linux operating system for HP Integrity servers, see http://
h20341.www2.hp.com/integrity/cache/342574–0–0–0–121.html
1.2 Using Linux Guests 15