HP Integrity Virtual Machines 4.3: Release Notes HP Part Number: 5900-2265 Published: May 2012, Edition 17.
© Copyright 2012 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.
Publication Number Supported VM Host Operating System T2767–90181 Supported Integrity VM Version Edition Number Publication Date HP-UX 11i v3 March 2009 and later HP Integrity Virtual Machines B.04.10 8.3 March 2009 T2767–90186 HP-UX 11i v3 April 2009 and later HP Integrity Virtual Machines B.04.10 8.4 April 2009 T2767–90191 HP-UX 11i v3 April 2009 and later HP Integrity Virtual Machines B.04.10 8.5 July 2009 T2767–90797 HP-UX 11i v3 April 2009 and later HP Integrity Virtual Machines B.
Contents 1 Introduction...............................................................................................9 1.1 New Features and Enhancements in This Version of Integrity VM..............................................11 1.2 Guest and VM Host Support...............................................................................................13 1.3 Changes in Support..........................................................................................................13 1.
7 Networking Information.............................................................................29 7.1 Changes and Issues in V4.3 January 2012 Patch Release........................................................29 7.1.1 Maximum Length for vswitch Names..............................................................................29 7.2 Changes and Issues in the V4.3 Release..............................................................................29 7.2.1 IPv6 Support and Exceptions.................
10.2.3 10.2.4 10.2.5 10.2.6 Log Messages Written to Old Log File........................................................................45 Saved MCA or INIT Register State Can Be Inaccurate..................................................45 Modifying the Size of the Monitor Log File..................................................................45 Virtual Console Event Logs Different from Physical Machine Logs....................................46 11 Integrity VM Support Policy.........................
Tables 1 2 3 4 5 6 7 8 9 Guest and VM Host Support..............................................................................................13 Guest Management Software Kit Locations..........................................................................14 NPIV Configuration Limits..................................................................................................34 Host AVIO and Guest AVIO Storage Versions......................................................................
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 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.
• On both HP-UX 11i v3 March 2011 and September 2011 Fusion release VM Hosts and guests: ◦ PHKL_41967 11.31 fs_select cumulative patch This patch provides significant performance improvements for Data Protector and some other applications. • On all HP-UX 11i v3 guests: ◦ PHKL_42464 — 11.31 boot loader cumulative patch This patch prevents boot failures on HP-UX 11i v3 guests with error Integrity of LABEL not met; not a valid label. • • • If you are running Symantec VxVM 5.0.
• This introductory chapter contains a list of the new features provided in the new release, as well as a description of the manual organization. It also may contain information of general interest to the release, like Section 1.4 (page 14) and documentation issues. • Chapter 2 through 10 provide release notes, relevant to the V4.3 May 2012 Patch Release, and they also include the release notes from the following releases: ◦ V4.3 March 2011 Release ◦ V4.3 August 2011 Patch Release ◦ V4.
• NVRAM Edit Utility — Displays, creates, edits and removes EFI variables in NVRAM files from a VM Host. • HP Integrity VM virtual iLO Remote Console for HP–UX guests — Allows access to the guest console by logging into a specific IP address. • Serviceguard 11.20 • Serviceguard A.11.19 is supported with Integrity VM V4.
• hpvmhostgdev script utility • Integrity VM is now fully supported with HP Insight Dynamics - VSE (ID−VSE) 6.2. Logical Server Management (LSM) and HP Insight Orchestration include support for Integrity VM Virtualization Provider Version 2.0 (VirtProvider), which is used with logical server features in Insight Dynamics to manage Integrity VM Hosts and HP-UX guests. For information about the new support in ID-VSE, see the HP Integrity Virtual Machines 4.
• Integrity VM V4.3 does not support Microsoft Windows and Linux guests. Version 4.2.5 was the last version to support Microsoft Windows and Linux guests. For information about V4.2.5 support, see the HP Integrity Virtual Machines 4.2.5: Release Notes on the BSC website at: http://www.hp.com/go/hpux-hpvm-docs • Use of legacy device special files (DSFs) to define virtual storage is deprecated starting in V4.3.
Whenever you upgrade Integrity VM, reinstall the guest kit on all the guests. This ensures that guests run well and continue to be manageable and supportable. Failure to install and upgrade the guest management software on each guest can cause problems that are difficult to diagnose and solve. 1.5 Documentation Issues • The HP Integrity Virtual Machines 4.3: Installation, Configuration, Administration manual states the dynamic memory is not enabled by default, however, beginning with the V4.2.
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 B.04.30 is supported on HP Integrity servers or nPartitions running HP-UX 11i v3 March 2011 Fusion release and HP-UX 11i v3 September 2011 Fusion release.
kctune base_pagesize=64 Note that changing this tunable requires a reboot of the system. 2.3 HP-UX Patches Required in the VM Host The following HP-UX patches are required on the VM Host: • • From V4.3 May 2012 Patch release kit: ◦ PHSS_42973 HPVM B.04.30 CORE PATCH ◦ PHSS_42974 HPVM B.04.30 HPVM-VMSGTK From V4.3 January 2012 Patch release kit: ◦ PHSS_42543 HPVM B.04.30 VMMIGRATE PATCH ◦ PHSS_42545 HPVM B.04.30 vmProvider PATCH (11.31) ◦ PHSS_42547 HPVM B.04.
• On both HP-UX 11i v3 March 2011 and September 2011 VM Hosts and guests: ◦ PHKL_41967- 11.31 fs_select cumulative patch This patch provides significant performance improvements for Data Protector and some other applications. • On all HP-UX 11i v3 guests: ◦ PHKL_42464 —11.31 boot loader cumulative patch This patch prevents boot failures on HP-UX 11i v3 guests with error Integrity of LABEL not met; not a valid label. • • • If you are running Symantec VxVM 5.0.
3 Creating Virtual Machines This chapter contains notes about creating and configuring virtual machines on the VM Host system. 3.1 Changes and Issues in the V4.3 Release This section describes virtual machine creation or configuration issues in the V4.3 release. 3.1.
4 Installing Guests This chapter describes notes pertaining to installing guest software on the virtual machines. 4.1 HP-UX Guests The following sections contain release notes specific to installing HP-UX guests in the V4.3 release. 4.1.1 Do Not Use the iomap(7) Mechanism on HP-UX Guests The iomap(7) mechanism allows you to map physical I/O addresses into the user process address space. Do not use this command on HP-UX guests. 4.
5 Using Integrity VM Commands This chapter contains notes about the Integrity VM commands. 5.1 Changes and Issues in the V4.3 Release The following sections describe changes, issues, and new information pertaining to the V4.3 release. 5.1.1 Integrity VM Command Changes The Integrity VM commands have changed in the following ways: • The resource syntax for hpvmclone, hpvmcreate, and hpvmmodify commands has changed to include support for NPIV, which is new in the v4.3 January 2012 patch release.
◦ -F Displays Integrity VM core Memory Metrics activity by Guest Display for the sample interval. The –M option displays all counts by vCPU. ◦ -G Displays the Guest Dynamic Memory, Swapping, and Paging Activity for the sample interval. ◦ -H Reports the Memory usage for various Integrity VM components, including dynamic memory. ◦ -I Reports Guest Interrupt Activity. The –M option displays all counts by vCpu. ◦ -N Displays Guest Network traffic by vswitch Activity Display.
6 Guest Administration This chapter contains information about managing Integrity VM guests. 6.1 Changes and Issues in the V4.3 Release There are no new guest administration issues in the V4.3 release. 6.1.1 Using HP Serviceguard to Manage Guests This section lists release notes specific to using Serviceguard in the Integrity VM environment. You can install HP Serviceguard A.11.20 on the VM Host or on the HP-UX guest running HP-UX 11i v3.
#hpvmdevmgmt -m env:HPVM_ENV_GROUP_ENTRY:attr:UUID=uuid 3. After creating the environment, list the environment: # hpvmdevmgmt -l env HPVM_MSE_GROUP_ENTRY:CONFIG=env,EXIST=NO,DEVTYPE=UNKNOWN,SHARE=NO,UUID=ee3a9a9c-ae14-11e0-8d01-001560de3a20,GROUPNAME=HPVM-SG-xylo_cluster::WWID_NULL # The following example adds the servers and their attributes to the MSE: Node1 (Jet1) # hpvmdevmgmt -l server jet1:CONFIG=server::WWID_NULL # #hpvmdevmgmt -m server:jet1:attr:SERVERID=1,attr:SERVERADDR=192.168.1.
7 Networking Information This chapter contains notes about configuring networks for virtual machines. 7.1 Changes and Issues in V4.3 January 2012 Patch Release The following section provides new information about V4.3 January 2012 patch release. 7.1.1 Maximum Length for vswitch Names The maximum length of a vswitch name has been increased from 8 characters to 64 characters. 7.2 Changes and Issues in the V4.3 Release The following sections contain networking information for the V4.3 release. 7.2.
With the virtual iLO Remote Console, captive accounts are not supported. The guest administrator should be created with the default shell: # useradd -g users \ -c "Console access to guest 'testme'" \ testme1 The hpvmmodify -P -u testme1:admin [-u testme1:oper] is still required, as well as the setting of a password for the user testme. 7.2.
7.2.8 Vswitch Use Disables TSO and CKO Capabilities on the IP Address on the Backing LAN Interface When a LAN interface has IP addresses configured and used by a vswitch, Integrity VM disables the TSO and CKO capabilities on the interface’s IP addresses. Consequently, poorer than expected performance is experienced from these IP addresses.
8 Storage Information This chapter contains information about storage devices used as backing stores for guest virtual devices. 8.1 Changes included in V4.3 January 2012 Patch Release The following section provides information about V4.3 January 2012 patch release. 8.1.1 NPIV Support January 2012 Patch Release NPIV allows the creation of multiple virtual Fibre Channel ports (VFCs) over one physical port (PFC) on a VM Host.
With the V4.3 January 2012 patch release installed, NPIV can have the following configuration limits: Table 3 NPIV Configuration Limits Description Limits NPIV HBAs per guest 8 NPIV HBAs per physical HBA 8 Lunpaths per NPIV HBA 2048 Lunpaths per NPIV LUN 8 LUNs per NPIV HBA 2048 NPIV LUNs per guest 2048 Lunpaths per guest 16384 Integrity VM V4.
Class I H/W Path Driver S/W State H/W Type Description ================================================================= ext_bus 7 0/1/3/0 gvsd CLAIMED INTERFACE HPVM AVIO Stor ext_bus 8 0/1/4/0 gvsd CLAIMED INTERFACE HPVM AVIO Stor … ext_bus 36 0/7/3/0 gvsd CLAIMED INTERFACE HPVM AVIO Stor ext_bus 37 0/7/4/0 gvsd CLAIMED INTERFACE HPVM AVIO Stor 2. 3.
The change to the enumeration policy has been made to reduce the time to boot to EFI in the cases of guest configurations with large amounts of AVIO storage devices configured. This policy change affects only the devices enumerated or configured at the EFI level, not at the guest operating system level. As a result of the default enumeration policy change, some attempted operations within EFI (such as boot management, or new guest installations) may fail because of non-present AVIO storage devices.
Changing the policy to enumerate all AVIO storage devices might result in longer guest boot times (to the EFI level), depending on the guest's configuration. If you need to boot from a tape device attached to an NPIV (such as performing tape-based Ignite-UX recovery), change the enumeration policy to "Enumerate all FC LUNs". As mentioned previously, enumerating all FC LUNs can result in a long guest boot time.
Table 4 Host AVIO and Guest AVIO Storage Versions AVIO Product Version Operating System Other Software HostAVIOStor B.11.31.1201 HP-UX 11i v3 PHKL_38604, PHKL_38605 and PHKL_38750 PHSS_40152 and Serviceguard for support of migration of shared LVMs GuestAVIOStor B.11.23.0903 HP-UX 11i v2 None GuestAVIOStor B.11.31.
8.2.5 Agile DSFs Change in HP-UX 11i v3 Guest When Migrating Disks Between scsi and avio_stor GuestAVIOStor version B.11.31.0810 or higher version fixes the change of agile device names in the guest OS when HBA is migrated between scsi (VIO) and AVIO storage. Follow these steps while changing the configuration of a guest HBA between VIO and AVIO. This is to ensure that agile disk device files under the modified HBA remain the same.
• Problem: Devices configured under AVIO Stor HBA for a guest cannot be deleted (using the hpvmmodify command) if the guest is at EFI. Solution: Stop the guest using the hpvmstop command and retry the hpvmmodify command. • Problem: Devices configured under AVIO Stor HBA for an HP-UX 11i v3 guest cannot be deleted (using the hpvmmodify command) if the guest is online.
9 Migrating Virtual Machines This chapter contains information about migrating virtual machines. 9.1 Changes included in V4.3 May 2012 Patch Release The following section provides information about the V4.3 May 2012 Patch Release. 9.1.1 Issue with V4.2.5 VM Suspended then Migrated to V4.3 VM Host A VM running on a V4.2.5 system with the V4.2.5 HPVM-Guest kit installed and then suspended and online or offline migrated to a V4.3 VM Host, fails to resume on a V4.3 VM Host.
The command line interface for migrating VMs is still the same for VMs that include NPIV AVIO devices. The hpvmmigrate command is used to perform both online and offline migration.
9.2.3 Disk Space Required for Suspend File When using hpvmsuspend to suspend a virtual machine, the amount of disk space required to accommodate the suspend file is the size of the virtual machine plus 250 MB. If enough disk space is not allocated, the hpvmsuspend command will not suspend the virtual machine. 9.3 Changes and Issues in the V4.3 Release The following sections discuss issues that apply to in the V4.3 release. 9.3.
10 Error Logging This chapter contains information about the way Integrity VM logs messages. 10.1 Changes and Issues in This Release There are no new error logging issues in the V4.3 release. 10.2 Known Issues and Information The following sections describe known issues and information from previous releases that still apply to V4.3. 10.2.1 Old Version of /etc/rc.config.d/hpvmconf Not Overwritten When you install the new version of Integrity VM, a new version of the /etc/rc.config.
10.2.6 Virtual Console Event Logs Different from Physical Machine Logs The virtual console allows you to use the sl command to list the System Event log and the Forward Progress log. The displays from the virtual console differ from those generated on a physical machine in the following ways: 46 • Event numbering is inconsistent for different lines. • Although the command menu allows you to specify a cell number, virtual machines are not cellular. Therefore, this option is not functional.
11 Integrity VM Support Policy This chapter describes the HP Integrity Virtual Machine support policies and software version requirements for Integrity VM Host and guest operating system environments. 11.1 Integrity VM Minimum Support Life The following table shows the support dates for Integrity VM versions. Integrity VM Version Release Date Expected End of Support Date Current Status A.03.50 December 2007 Same as HP-UX 11i v2 Supported B.04.20 March 2010 March 2013 Supported B.04.20.
their virtual storage devices. HP recommends the use of persistent DSFs (for example, those with pathnames such as /dev/rdisk/disk##) for better storage availability and reliability. To check for the use of legacy DSFs, use the following command: # hpvmstatus -P guestname -d | grep -w rdsk 11.3 VM Host OS and Server Support Integrity VM Host or Server Support Integrity VM Version A.03.50 Integrity VM Version B.04.20 Integrity VM Version B.04.20.05 Integrity VM Version B.04.
11.4 HP-UX Guest Support Type of Guest OS Integrity VM Support Version A.03.50 Integrity VM B.04.20 Integrity VM B.04.20.05 Integrity VM B.04.
11.5 Windows and Linux Guest Support Type of Guest OS Windows Linux Integrity VM Version A.03.50 Integrity VM Version B.04.20 Integrity VM Version B.04.20.
11.7 HP Serviceguard Support The version of Serviceguard must be supported with the version of HP-UX on which the VM Host is running. Integrity VM V4.3 supports Serviceguard 11.20. For specific support information, see the Serviceguard documentation. Packages or Nodes Integrity VM Version A.03.50 Integrity VM Version B.04.20 Integrity VM Version B.04.20.05 Integrity VM B.04.
11.8 Storage Interface Support Integrity VM Version A.03.50 (Both VIO and AVIO unless explicity excluded) Integrity VM Version B.04.20, B.04.20.05, Notes and B.04.
NOTE: Starting with HP-UX 11i v3 0909, LV Mirroring is supported on HP-UX 11i v3 guests with Integrity VM V4.0 or later using AVIO. Backing Store Integrity VM Version B.04.
11.10 Online and Offline Migration Support The following list provides the supported online and offline migration paths for HP-UX and OpenVMS guests: • Support: ◦ Forward migration — Supported between two VM Hosts running the same or subsequent Integrity VM version (see Table 7 (page 54)).
NOTE: When migrating across versions (Integrity VM 4.2 and later), be aware of the guest OS versions that are supported on the target host. If the guest is not supported by the target host, the guest must be updated immediately after migrating to maintain support on the target host. Before booting B.11.31.1103 GuestAVIOStor on Integrity VM V4.2.5 (or earlier) and migrating this guest from the source host with Integrity VM V4.2.5 (or earlier) to a target host with Integrity VM V4.
• AD386A — Add-in (10GbE) • HBA's AM225A, AM232A, AM233A • NC360m — C-class Mezz card • NC364m — C-class Mezz card • HP NC551m Dual Port FlexFabric 10Gb Converged Network Adapter Integrity VM Support Policy
12 Support and other resources 12.1 Contacting HP 12.1.1 Before you contact HP Be sure to have the following information available before you call contact HP: • Technical support registration number (if applicable) • Product serial number • Product model name and number • Product identification number • Applicable error message • Add-on boards or hardware • Third-party hardware or software • Operating system type and revision level 12.1.
integrated with HP Systems Insight Manager. A dedicated server is recommended to host both HP Systems Insight Manager and HP Insight Remote Support Advanced. Details for both versions are available at: http://www.hp.com/go/insightremotesupport To download the software, go to Software Depot: http://www.software.hp.com Select Insight Remote Support from the menu on the right. NOTE: HP recommends using Insight Remote Support on the VM Host system.
12.3 Typographic conventions This document uses the following typographical conventions: %, $, or # A percent sign represents the C shell system prompt. A dollar sign represents the system prompt for the Bourne, Korn, and POSIX shells. A number sign represents the superuser prompt. audit(5) A manpage. The manpage name is audit, and it is located in Section 5. Command A command name or qualified command phrase. Computer output Text displayed by the computer. Ctrl+x A key sequence.
13 Documentation feedback HP is committed to providing documentation that meets your needs. To help us improve the documentation, please send any errors, suggestions, or comments to Documentation Feedback (docsfeedback@hp.com). Include the document title and part number, version number, or the URL when submitting your feedback.
