HP Integrity Virtual Machines Release Notes Version A.03.50 HP Part Number: T2767-90170 Published: November 2008, Edition 7.
© Copyright 2008 Hewlett-Packard Company, L.P. Legal Notices Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Table of Contents About This Document.........................................................................................................9 Intended Audience.................................................................................................................................9 New and Changed Information in This Edition.....................................................................................9 Typographic Conventions...................................................................
3.5 Golden Images of Systems with HPVM-Guest Installed Must have HPVM Device Drivers Configured............................................................................................................................................32 3.6 Numbers Reported by Glance 4.6 or above Running on VM Host Might be Incorrect..................32 3.7 Interleaved Memory on Cellular Hosts...........................................................................................32 3.8 hpvmcreate Manpage Incorrect......
.4 The hpvmdevmgmt Command Truncates File Sizes.......................................................................45 5.5 Setting Devices to Sharable Can Lead to Device Conflicts.............................................................45 5.6 Errors on Displaying Guest or Vswitch Information While that Information is Being Modified...45 5.7 Do Not Attempt to Remove Busy Virtual Devices..........................................................................46 5.8 Missing uuid or .vmid Files.........
7.17 Other Issues and Notes..................................................................................................................58 8 Storage Information.....................................................................................................61 8.1 Critical Issue Fixed in HostAVIOStor B.11.23.0803.........................................................................61 8.2 USB 2.0 Now Supported........................................................................................
List of Tables 1-1 2-1 2-2 2-3 2-4 2-5 2-6 2-7 2-8 2-9 3-1 Guest Management Software Kit Locations..................................................................................18 VM Host Patches...........................................................................................................................21 Do Not Install Product or Patch....................................................................................................23 HP-UX Guest Patches..................................
About This Document The HP Integrity Virtual Machines Release Notes document describes the latest enhancements and changes to the HP Integrity Virtual Machines product (Integrity VM), including limitations and guidelines for using the Integrity VM software. Always read the release notes before installing and using the product. For the most current information, obtain the latest version of this document from docs.hp.com.
• • • • • • • • Chapter 3: “Creating Virtual Machines” (page 31) contains information about creating virtual machines. Chapter 4: “Installing Guests” (page 35) contains information about installing guest operating system and management software. Chapter 5: “Using Integrity VM Commands” (page 45) contains information about using Integrity VM commands. Chapter 6: “Guest Administration” (page 49) contains information about guest system administration.
Publication Number Supported VM Host Operating System Supported Integrity VM Version Edition Number Publication Date T2767–90150 HP-UX 11i v2 March 2008 and later HP Integrity Virtual Machines A.03.50 7.0 March 2008 T2767–90170 HP-UX 11i v2 July 2008 and later HP Integrity Virtual Machines A.03.50 7.1 November 2008 HP Encourages Your Comments HP encourages your comments concerning this document. We are truly committed to providing documentation that meets your needs.
1 Introduction Thank you for installing HP Integrity Virtual Machines (also called Integrity VM). This Release Notes document describes the changes in this version of the Integrity VM product. The Integrity VM Version 3.5 release introduces new accelerated storage and networking products to improve the overall I/O performance for Integrity VM.
— Changes to the hpvmnet command. The changes include displaying the adapter type for each port defined on the vswitch and getting port specific statistics. — Changes to the hpvmresources and hpvmstatus manpages to include the new AVIO names for guest creation: avio_lan, and avio_stor. — Change to the hpvmcollect command to add values for AVIO LANs and storage.
• 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.
The guest parameter settings for Linux guests are listed in Table 3-1 (page 31). For information about installing Linux guests, see the HP Integrity Virtual Machines Installation, Configuration, and Administration A.03.50 manual. 1.3 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.
NOTE: The use of cell local memory on Integrity Virtual Machine hosts is an experimental feature for this release. In general, you should see performance improvement by using cell local memory when running on cell based systems. If you encounter performance issues with this feature, you should revert back to using 100% interleaved memory. 1.
Table 1-1 Guest Management Software Kit Locations Guest Operating System Guest Management Software Location HP-UX 11i v2 /opt/hpvm/guest-images/hpux/11iv2 HP-UX 11i v3 /opt/hpvm/guest-images/hpux/11iv3 Linux /opt/hpvm/guest-images/linux Windows /opt/hpvm/guest-images/windows Installing the guest management software kit causes the guest to reboot. Whenever you upgrade Integrity VM, reinstall the guest kit on all the guests.
2 Installation Notes This chapter contains notes about installing and upgrading Integrity VM and associated software on the VM Host system. 2.1 Installing Integrity VM This section describes information about installing the HP Integrity Virtual Machines product and associated software on the VM Host system. HP Integrity Virtual Machines A.03.50 is supported on HP Integrity servers or nPartitions running HP-UX 11i v2 (December 2007 0712 or later).
For VM Hosts that will support guests as Serviceguard packages, the Mission Critical Operating Environment (MCOE) can also be used. 2.1.4 Upgrade HP WBEM Services Integrity VM fails to install if the version of WBEM Services on your VM Host is old. The VM Host system must be running HP WBEM Services A.02.00.10 or later. The HP WBEM Services for HP-UX software bundle (B8465BA) is available as part of the HP-UX operating system, or download the software from www.hp.com.
WBEMServices.WBEM-CORE-COM A.02.00.11 Fileset for hp Integrity servers and hp 9000 servers WBEMServices.WBEM-MAN A.02.00.11 Fileset WBEMServices.WBEM-MX A.02.00.11 fileset WBEM Services COM WBEM Services MAN WBEM Services MX 2.1.7 VMMGR V3.0 Does Not Support Integrity VM V3.5 AVIO Functionality Integrity Virtual Machine Manager Version 3.0 and earlier versions do not support AVIO functionality.
Table 2-1 VM Host Patches (continued) 22 Affected HP-UX (VM Host) Version Affected Integrity VM Version Fix Description/Impact Comment 11i v2 0512 or later A.02.00 or later PHNE_33724 (11.23.0706) Bug fix Fixes a problem of a panic on the VM Host. Likely only on Integrity VM V2.0 as HP-UX guests in V1.0 do not do what the Windows guests do in V2.0 (ping the guest). 11i v2 0505 or later A.02.00 or later PHNE_34474 Bug fix Required when using linkloop over VLANs between guest and VM Host VLAN.
Table 2-1 VM Host Patches (continued) Affected HP-UX (VM Host) Version Affected Integrity VM Version Fix Description/Impact Comment 11i v2 0505 or later A.01.20 or later PHSS_35863 (Serviceguard A.11.16) PHSS_35427 (Serviceguard A.11.17) Bug fix Specific to Serviceguard. If Serviceguard is running on a node with only one CPU, threads can get blocked, and the node will TOC. This happens only on nodes with a single CPU and pthreads patch installed (PHCO_34944, or later).
Table 2-3 HP-UX Guest Patches 24 Affected Guest OS and Affected Integrity VM Version Version Fix Description/Impact Comment 11i v2 0505 A.01.00 or later U320 SCSI MPT driver version B.11.23.03, bundle A7173A Includes fixes for performance and stability. MPT driver update. This patch is included in the 0512 update. 11i v2 0505 or later A.01.00 or later PHKL_34278 Bug fix Resolves panic and system hang symptoms. 11i v2 0505 through 0606 A.01.00 or later PHKL_34589 (11.23.
11i v2 Intel Itanium 9000 (Montecito) A.01.20 or later HPVM A.02.00 11.23.0609 HWE Intel Itanium 9000 hardware support Integrity VM V2.0 or later is strongly recommended for use with Intel Itanium 9000-based systems. See the support statement at http:// wtec.cup.hp.com/ 11i v2 0505 or later A.01.20 or later PHSS_35863 (Serviceguard A.11.16) PHSS_35427 (Serviceguard A.11.17) Bug fix Specific to Serviceguard.
Table 2-4 lists patches and products that you should not install on HP-UX guests. In guests where these patches are installed, degradations and regressions have been observed. Table 2-4 Do Not Install Products or Patches on HP-UX Guests Affected Guest OS and Affected Integrity VM Version Version Fix Description/Impact Comment HP–UX 11i v2 0505 or A.01.00 later A.01.20 PHKL_33361 Cumulative kernel SCSI patch Resolved in Integrity VM A.02.00 and later. HP–UX 11i v2 0505 or A.01.00 later A.01.20 A.02.
Table 2-8 Red Hat Linux Patches Affected Guest OS and Affected Integrity VM Version Version Fix Description/Impact Comment RHEL4U4 through U5 A.03.00 or later SGLX_00190 (Serviceguard or Linux A.11.18.02) Bug fix Serviceguard on Linux SG A.11.18.02 2.1.14 Patches Required for SUSE Enterprise Linux Guests Table 2-9 lists the patches that are required in the guests.
# swinstall -x autoreboot=true -s my.server.foo.com:/depot/path T2767AC vmProvider Installation of the current version of Integrity VM fails on systems that have older versions of the VMProvider bundle. The swinstall session fails and logs messages to /etc/rc.log indicating that a new version of VMProvider must be installed before or at the same time as Integrity VM. The VMProvider bundle is available on the Integrity VM installation media.
at the time the CPU was taken away. For more information about using Glance, see glance(1M). • Using HP Integrity Essentials Global Workload Manager (gWLM) If you use gWLM within VSE to manage virtual machines, when you upgrade the VM Host, make sure the gWLM agent on that host is running gWLM A.02.50 or greater. Also, the managing VSE Central Management Station (CMS) must be running A.02.50 or greater, as described in the VSE Management Software Installation and Update Guide.
2.6 Do Not Install Windows as Alternate Boot on a VM Host System Guest boot disks might become unbootable if the VM Host is restarted as a Windows system. 2.7 Trunking Software Trunking software such as HP Auto Port Aggregation (APA ) is supported only on the VM Host and not on the guest. 2.8 Using EMC PowerPath with AVIO and VIO AVIO and VIO have been tested with the EMC PowerPath product. Note, direct support-related questions on the use of EMC PowerPath with Integrity VM to the EMC Corporation.
3 Creating Virtual Machines This chapter contains notes about creating and configuring virtual machines on the VM Host system. 3.1 Default Guest Settings for HP-UX, Windows, and Linux Table 3-1 lists the default guest settings for HP-UX, Windows, Linux, and Unknown guests. An Unknown guest is a virtual machine that has not booted with any operating system. When an Unknown guest type boots, the appropriate operating system type is applied to the guest configuration.
The VM Host uses this space to start up guests, but guests are never swapped out. (A guest's physical memory is locked down.) By turning off the swapmemon feature on the VM Host, Integrity VM conserves RAM for guest use. 3.4 Do Not Create Golden Images of the VM Host for Guest Installation Do not use the VM Host to create golden images to be used for guest OS installations using Ignite-UX.
3.9 hpvmstop Manpage Incorrect The hpvmstop manpage incorrectly states that the -g option is the default behavior when in fact the -h option is the default. 3.10 New option for hpvmstatus Command The user can now determine whether the VM Host and guests use Cell Local Memory (CLM) interleaved Memory (ILM) with the hpvmstatus -C option. The hpvmstatus -C command provides a list of guests with their memory type. If you do not use CLM at all, then all the guests use Interleaved Memory (ILM).
4 Installing Guests This chapter describes notes pertaining to installing guest software on the virtual machines. 4.1 Windows Guests The following sections contain the release notes specific to installing Windows guests. 4.1.1 Removing Media During Installation Hangs Guest If you begin the installation of the Windows operating system and then eject the media from the virtual console, the guest hangs. To recover from the problem, restart the guest from the virtual console. 4.1.
# hpvmmodify -P guest-name -a dvd:scsi::file:/InstallMedia/Windows.iso # hpvmmodify -P guest-name -a dvd:scsi::disk:/dev/rdsk/c0t0d0 Insert and remove media (for software installation using multiple CDs) using the hpvmmodify command (effectively ejecting and inserting files) or, in the case of a physical drive, actually eject and insert the media in the drive.
# hpvmstop -P winguest # hpvmconsole -P winguest -c "pc -off" These commands do not stop the Windows operating system gracefully. To shut down a Windows guest, use the standard Windows operating system commands. 4.1.11 Do Not Delete EFI Shell Boot Option Do not delete the EFI Shell [Built-in] EFI Boot Manager option. Deleting this option might interfere with the subsequent installation of the guest operating system. To recover if there are no options present on the EFI Boot Manager menu screen: 1.
\EFI\Microsoft\WINNT50\Bootxxxx 4.2 HP-UX Guests The following sections contain release notes specific to installing HP-UX guests. 4.2.1 Installing the Guest Management Software The guest management software is required on each guest. The guest management software ensures that guests have the required patches for optimum performance and manageability. It enables the hpvmcollect and hpvminfo commands on the guest.
Overall system performance may not be optimal. "/sbin/rc3.d/S829hpvmguestlib start" FAILED This issue can be corrected by installing the HPVM-Guest bundle. 4.2.2 HP-UX 11i v3 Guests Might Fail to Configure Interface Cards Due to Lack of Memory Resources HP-UX 11i v3 guests with small memory resources (less or equal to 2 GB RAM) might fail to configure one or more virtual interface cards.
ERROR: 1 of 882 filesets had Errors. * 881 of 882 filesets had no Errors or Warnings. ERROR: The Execution Phase had errors. See the above output for details. These startup messages in /etc/rc.log can be disregarded. iCAP commands cannot be used on virtual machines. iCAP commands are designed to work on the VM Host system. This problem is resolved in guests running HP-UX 11i v2 0706 and later. 4.3 Linux Guests The following sections describe release notes for Linux guests. 4.3.
4.3.
3. • # Allow access only from user 'wbemuser': -: ALL EXCEPT wbemuser pegasus:wbemNetwork • # Allow access by all users: +: ALL EXCEPT :wbemNetwork Start the tog-pegasus package by executing the following command: # /etc/init.d/tog-pegasus start For information on where to download the Utilization Provider for the Red Hat Linux guest, see the VSE Management Software Installation and Update Guide.
4.3.11 Inconsistent “Bogomips” Values between Virtual CPU0 and Other Virtual CPUs “Bogomips” values can be inconsistent between virtual CPU0 and other virtual CPUs. This condition is harmless. To prevent this problem, add the lpj=4000000 boot option in /boot/ efi/efi/redhat/elilo.conf. For example: # cat elilo.conf prompt timeout=20 default=linux relocatable image=vmlinuz-2.6.9-42.EL.img label=linux initrd=initrd-2.6.9-42.EL.
5 Using Integrity VM Commands This chapter contains notes about the Integrity VM commands. 5.1 Accidental Use of -R Option with hpvmmodify Instead of -r The hpvmmodify command supports two options related to guest memory configuration, -r and -R. Accidental confusion of one for the other might create undesired results with your guest configuration. For an explanation of these command options, see the hpvmmodify manpage.
5.7 Do Not Attempt to Remove Busy Virtual Devices Before removing virtual devices with the hpvmmodify command, make sure that the guest operating system is no longer directing I/O to the device. Unmount the device if it is mounted. If you attempt to remove a device that has I/O in progress, the hpvmmodify command incorrectly removes the device from the guest configuration file.
Configuration, and Administration manual. To view the command displays properly, enter the following commands on the Linux guest: # export LANG=en_US.iso88591 # export TERM=vt200 Exporting these environment variables allows you to display the manpage content from a Linux guest console. Some minor differences in the appearance of the manpages as displayed on HP-UX and as displayed on Linux are expected. 5.
6 Guest Administration This chapter contains information about managing Integrity VM guests. 6.1 Administrator Account Names This version of Integrity VM lifts the restriction that the virtual console administrator account names must be the same as the guest name. As a result, the virtual console administrator name can be any valid HP-UX login name.
-d /var/opt/hpvm/guests/testme \ testme1 # useradd -r no -g users -s /opt/hpvm/bin/hpvmconsole \ -c "Console access to guest 'testme'" \> -d /var/opt/hpvm/guests/testme \ testme2 # useradd -r no -g users -s /opt/hpvm/bin/hpvmconsole \ -c "Console access to guest 'testme'" \ -d /var/opt/hpvm/guests/testme \ testme3 The following command creates the virtual machine named testme: # hpvmcreate -P testme -u testme1:admin -u testme2 -u testme3:oper At this point, users testme2 and testme3 both have oper level a
6.7 HP-UX 11i v3 Guests Might Panic with a NaT_hndler: kernel NaT Consumption Fault Under certain situations, an HP-UX 11i v3 guest might panic with a NaT_hndler: kernel NaT Consumption fault when using Logical Volume Manager (LVM) software. To avoid this situation, install the BaseLVM (B.11.31.0712) software from the HP-UX 11i v3 0712 AR media. 6.8 How to Stop Guests To stop a guest, HP recommends that you perform an operating system shutdown from a privileged account on the guest.
6.11.3 Required HP Serviceguard Patches To use Serviceguard to manage HP-UX guests, make sure the required patches are installed. For more information, see Section 2.1.9 (page 21). 6.11.4 Reenter Command to Start Packages The procedure for configuring and starting guest packages includes the cmrunpkg command. This command does not always work the first time you enter it. If the command does not start the package, re-enter the command. 6.11.
This is apparent when using gWLM A.02.50 with Integrity VM A.03.00. You can correct the problem by modifying the guest and specifying processing power in percentage rather than CPU cycles. For example, to modify the guest named compass1 to use 10% of the CPU processing power, enter the following command # hpvmmodify -P compass1 -e 10 You must boot the guest to initiate this setting for gWLM. Alternatively, upgrade gWLM to A.03.00 for use with Integrity VM A.03.00. 6.
7 Networking Information This chapter contains notes about configuring networks for virtual machines. 7.1 Supported Adapters Integrity VM supports only those adapters that are of Ethernet or the IEEE 802.3 CSMA/CD network. Note that AVIO interfaces are supported by a select set of Ethernet host NICs. For a list of the specific AVIO supported NICs, see the HP Integrity Virtual Machines Installation, Configuration, and Administration A.03.50 manual. 7.
mode). Before you stop APA, use the hpvmnet -h command to halt the vswitch. If you do not halt the vswitch first, the hpvmnet command reports an incorrect MAC address for the vswitch. 7.7 VM Manager Does Not Display APA Link Aggregate LAN Device If a VM host system has an APA link aggregate LAN device that is composed of one or more APA link aggregate LAN devices, the VM Manager does not display this APA link aggregate as a possible backing LAN device in the VM dialog.
virtual network interface cards in the guest and any physical network interface cards in the VM Host that are used by vswitches. When TSO is enabled, guest networks are interrupted. To verify whether TSO is turned on, enter the following command: # lanadmin -x vmtu n Where n is the VM Host interface, as displayed by the hpvmnet command.
7.15 Do Not Use TCP Software Packet Reassembly in IGSSN Driver There have been problems with TCP Software Packet reassembly in the igssn driver in a guest HP-UX image. For this release, do not enable it on a guest. By default, software packet reassembly (known with acronyms as drv_pr for driver packet reassembly) is enabled in igssn in the guest.
• or VLAN must match, whether they are physical systems or guests. The VM Host does not check for MTU mismatches for its guests. The lanadmin card specific options that are supported on igssn on the guest are: — -x:speed,fctrl,cko,type,card_info,stats drv,vmtu,and drv_pr. — -X:drv_pr_on,drv_pr_off,stats clear 7.
8 Storage Information This chapter contains information about storage devices used as backing stores for guest virtual devices. 8.1 Critical Issue Fixed in HostAVIOStor B.11.23.0803 A critical issue with AVIO DVD devices that caused guest installation failure on platforms that have USB DVD devices (for example, rx2660, rx3600, rx6600 and so forth), has been fixed. 8.2 USB 2.0 Now Supported Integrity VM now supports the USB 2.0 driver on an HP-UX 11i v2 VM Host. 8.
disk 25 0/0/6/0.4.0 sdisk CLAIMED /dev/dsk/c4t4d0 DEVICE HP /dev/rdsk/c4t4d0 Virtual Disk Workaround: Use the System Management Homepage (SMH) to configure the devices. 8.4 AVIO Current Limitations The following sections describe the current limitations using AVIO. 8.4.
This delay is caused by the retry of failed commands from the nonresponding backing store. There is currently no workaround. 8.4.5 I/O Resource Delete Using hpvmmodify Fails When Guest is at EFI Devices configured under AVIO Stor HBA for a guest cannot be deleted (using the hpvmmodify command) if the guest is at EFI. Workaround: Stop the guest using the hpvmstop command and retry the command. 8.4.
Note the following example: # ioscan -fne disk PciDev | PCIFtn | |(Addr(Target Id) % 16) <-> HP-UX tgt ID PciBus | | |(Addr(Target Id) / 16) <-> HP-UX lun ID | | | | | V V V V V 49 0/0/2/0.6.
8.7 Assigning a Null Device to a Resource When assigning a null device to a resource on a virtual machine, the file name serves as a placeholder. Therefore, if the file does not exist, you will not receive an error message. For example, the following command string will not produce an error message if the file XXXX.iso does not exist: hpvmmodify -P vm1 -a "disk:scsi::null:/opt/XXXX.iso 8.
8.14 Using sam on Guest Cannot Initialize Disk When you create a file system using the sam command on an HP-UX guest, do not initialize the disk. This option returns an error and the file system is not created. 8.15 Extending a Logical Volume Backing Store Corrupts the Guest On the VM Host, do not extend a logical volume (LVM or VxVM) used as a backing store for a guest root disk.
8.19 AVIO Multipathing Support The AVIO storage driver supports both Active-Active and Active-Passive firmware on EVA GL series (3000/5000) starting with HostAVIOStor B.11.23.0712.01. AVIO is now compatible with SCSI with respect to EVA support. The minimum Active-Passive firmware version recommended is VCS v3.110. The EVA XL series (4000/6000/8000) continues to support the Active-Active configuration. SecurePath Active-Passive is now supported in addition to Active-Active on AVIO.
gvsdmgr(1M) NAME gvsdmgr -- A utility to manage HP-UX Mass Storage Core I/O cards or HBAs claimed by Integrity VM Guest AVIO Storage driver (gvsdmgr).
• get_info The following qualifier can be specified with the get_info command: — lun — Shows lun information for a specific LUN or all LUNs. When the get_info command is run without qualifiers, it returns information about the Core I/O card / HBA represented by device_file. • get_stat The following qualifier can be specified with the get_stat command: — lun — Shows statistics for a specific LUN or all LUNs.
9 Migrating Virtual Machines This chapter contains information about migrating virtual machines. 9.1 Do Not Migrate Distributed Guests Guests that are configured as Serviceguard packages cannot be migrated. 9.2 Collect CapAd Data before Migrating If you migrate a virtual machine that is being managed by VSE, use Capacity Advisor to collect utilization data before you migrate the virtual machine. Otherwise, the utilization information for the VM Host prior to the migration is lost. 9.
10 Error Logging This chapter contains information about the way Integrity VM logs messages. 10.1 Guest Log Can Grow Unbounded The guest monitor log file (/var/opt/hpvm/guests/vm_name/log) records guest start and stop information. These log files can grow very large. Use the hpvmconsole command rec -rotate to close the current log file, rename it, and open a new one. 10.2 Log Messages Written to Old Log File Log messages might be written to the command.log.old file instead of the command.log file.
