HP Integrity Virtual Machines 4.2: Release Notes HP Part Number: 5900-0827 Published: June 2010, Edition 11.
© Copyright 2010 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.......................................................................................................11 Intended Audience................................................................................................................................11 New and Changed Information in This Edition...................................................................................11 Typographic Conventions.....................................................................
3 Creating Virtual Machines..........................................................................................39 3.1 Changes and Issues in this Release.................................................................................................39 3.2 Known Issues and Information.......................................................................................................39 3.2.1 Failed API Access to Local Running Guest......................................................................
4.3.2.3 TC INIT Dump Messages Fail to Appear in SUSE Linux Guest Consoles Running Multi CPUs.................................................................................................................................48 4.3.2.4 SLES10 SP2 Guests Supported on Integrity Servers.......................................................48 4.3.2.5 Before Installing the SUSE Linux Guest..........................................................................49 4.3.2.
Guest Administration...................................................................................................61 6.1 Changes and Issues in this Release.................................................................................................61 6.2 Known Issues and Information.......................................................................................................61 6.2.1 Specifying Maximum Entitlements...........................................................................
.2.10 Integrity VM V4.1 Does not Support Gelan Drivers.............................................................71 7.2.11 MAC Address Validation Can Be Enhanced.........................................................................71 7.2.12 Auto Port Aggregation (APA) is Supported on the VM Host, Not on the Guest.................71 7.2.13 Do Not Run Applications that Set Network Devices into Promiscuous Mode....................71 7.2.14 Guest and Host Communication.....................................
9.2.3 NR Guest State........................................................................................................................84 9.2.4 A Guest Might be Marked Disabled After Failed Offline Migration......................................84 9.2.5 Do Not Migrate Serviceguard Cluster Nodes.........................................................................84 9.2.6 Unpresenting SAN Devices to Integrity VM Hosts................................................................84 9.2.
List of Tables 1-1 2-1 2-2 2-3 2-4 2-5 2-6 2-7 2-8 2-9 Guest Management Software Kit Locations..................................................................................17 VM Host Patches...........................................................................................................................28 Do Not Install Product or Patch....................................................................................................32 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 Integrity Virtual Machines documentation.
Document Organization This document contains information that supplements the information in the Integrity Virtual Machines Version 4.2: Installation, Configuration, and Administration and includes the following chapters: • • • • • • • • • • • Chapter 1: “Introduction” (page 15) describes some of the enhancements and quality improvements in the current release of the HP Integrity Virtual Machines product.
Publication Number Supported VM Host Operating System Supported Integrity VM Version Edition Number Publication Date T2767–90014 HP-UX 11i v2 May 2005 and later HP Integrity Virtual Machines A.01.20 2.3 April 2006 T2767-90043 HP-UX 11i v2 May 2005 and later HP Integrity Virtual Machines A.01.20 2.4 June 2006 T2767–90033 HP-UX 11i v2 May 2005 and later HP Integrity Virtual Machines A.02.00 3.0 October 2006 T2767–90076 HP-UX 11i v2 September 2006 and later HP Integrity Virtual Machines A.
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 4.2 release introduces several new features including support for the HP-UX 11i v3 1003 as a VM Host.
— — — HP-UX 11i v3 VM Host — HP-UX 11i v3 1003 HP-UX 11i v3 guests — HP-UX 11i v3 0903 through 1003 HP-UX 11i v2 guests — HP-UX 11i v2 0712 The following patches are required for 11i v2 and 11i v3 guests running on Intel® Itanium® 9300 Processor Series systems: — — HP-UX 11i v2: PHCO_40685 and PHKL_40684 HP-UX 11i v3: PHKL_39482 and PHCO_38777 • Support for the following VM Host and guests: — HP-UX 11i v3 VM Host — HP-UX 11i v3 1003 — HP-UX 11i v3 guests — HP-UX 11i v3 0709, 0803, 0809, 0903, 0909, and
kit for each type of guest operating system. The instructions for installing the guest management software are provided in README.txt files in these directories. 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 and /opt/hpvm/guest-images/ windows2008 NOTE: kit.
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.20 is supported on HP Integrity servers or nPartitions running HP-UX 11i v3 March 2010 1003).
# /sbin/init.d/ovpa stop # /sbin/init.d/ovpa start To stop and restart the scopeux process, use the following commands: # /sbin/init.d/ovpa stop # /sbin/init.d/ovpa start 2.2.2 Compatibility of VSE V4.1 with Integrity VM V4.2 You can use Version 4.1 of the VSE Suite with Integrity VM Version 4.2, but this version of the VSE Suite does not support the new features in Integrity VM Version 4.2. 2.
• You might receive a read error while reading filesets from the OE media, with a “Bad Address (14)” wording in the error message. Workaround: Install the PHKL_39114 patch. • The update might hang while installing the filesets from the March 2009 OE media. Installing PHKL_39114 does NOT fix this critical problem. This problem results when you update the OE from 0809 to 0903 using physical (DVD) media.
NOTE: Patch PHKL_37815 contains the new USB driver delivered with HP–UX 11i v3 (0903). Consequently, if you install this patch on an HP–UX 11i v3 system that is older than 0903, you might experience the same problem. You can use a single hpvmdevmgmt to modify all guests to use the new USB DVD device.
2.3.2.5 Failures in Key Applications Some applications fail when run on HP-UX with large pages configured (larger than 8K).
NOTE: Be sure to completely specify T2767CC.VMCONVERT, so that you do not accidentally transform your host to a VM Host that is left in an unknown state. 2.3.5 Limitations When using HP Integrity Virtual Machines Manager with Integrity VM V4.2 HP Integrity Virtual Machines Manager (VMMgr) Version 3.5 or Version 4.0 can be used with Integrity VM V4.2. Earlier versions of VMmgr (V3.0 and earlier) do not install or run on an HP-UX 11i v3 VM Host and cannot be used with Integrity VM V4.2.
using a persistent device file as a backing device to a new virtual machine, use the hpvmcreate command. To add such an I/O device to an existing VM, use the hpvmmodify command. Beginning with VMMgr V4.0, you can display persistent device files (and their associated LUN hardware paths) as backing device choices when adding a storage device. • In V3.
used for the volume group. As a workaround, define LVM volume groups to be used as backing storage for VMs using legacy device files. NOTE: This issue does not occur with disks used for VxVM volume groups. VxVM does not yet completely support the new agile addressing, but that may change with future versions of VxVM. The VMMgr product V4.
be backed up regularly on the VM Host system. Do not use the VM Host system as a backup server. For more information, see the HP-UX 11i v2 Installation and Update Guide. • Using HP GlancePlus/iX to monitor guests You can use Glance on the VM Host to monitor guest data, but recorded measurements can be misleading. Glance receives the CPU accounting information from the guest kernel.
Windows guests in the HP Integrity Virtual Machines Installation, Configuration, and Administration manual. • Using HP Instant Capacity with Integrity VM You can use HP Instant Capacity solutions on the VM Host system as you would on any other HP-UX system. 2.3.6.3 Do Not Install Integrity VM on a Virtual Partition HP does not support running Integrity VM in a vPar. If you override the Integrity VM installation warnings and force this installation, you receive errors during the start of Integrity VM. 2.
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.00 or later Cimserver 02.00.09 PHSS_34429 Bug fix Resolves potential corruption of guest configuration, cimserver, or other WBEM files when under extreme load. Download HP WBEM Services for HP-UX Product Bundle B8465BA from the HP software depot. 11i v2 0505 thru 0606 A.02.00 or later PHKL_33604 (11.23.0609) PHKL_33605 (11.23.
Table 2-1 VM Host Patches (continued) 30 Affected HP-UX (VM Host) Version Affected Integrity VM Version Fix Description/Impact Comment 11i v2 0505 or later A.03.00 or later PHSS_36997 (Serviceguard A.11.18) Bug fix Serviceguard support for 11i v2. 11i v2 0712 A.03.50 PHSS_37306 Bug fix Mandatory Integrity VM patch 11i v2 0712 A.03.50 PHSS_37845 Bug fix Enables users to create Red Hat 4.6 guests. 11i v2 0712 A.03.50 PHSS_38297 Bug fix Mandatory patch: HPVM A.03.
Table 2-1 VM Host Patches (continued) Affected HP-UX (VM Host) Version Affected Integrity VM Version Fix Description/Impact Comment 11i v3 0809 or later B.04.00 or later PHSS_39094 Bug fix 11i v3 Linker and fdp cumulative patch. 11i v3 0809 or later B.04.00 or later PHKL_38750 Bug fix 11i v3 estape cumulative patch (Recommended for working with multipath tape devices.) 11i v3 0903 B.04.10 PHSS_39342 Bug fix HPVM B.04.10 CORE PATCH 11i v3 0903 B.04.10 PHSS_39354 Bug fix HPVM B.04.
Table 2-1 VM Host Patches (continued) Affected HP-UX (VM Host) Version Affected Integrity VM Version Fix Description/Impact Comment 11i v3 0903 and later B.04.10 PHSS_40277 Bug fix and enhancements HPVM B.04.10 vmProvider: Virtprovider, Attached AVIO Tape Boot, OVMM support for Shared LVM 11i v3 0903 and later B.04.10 PHSS_40152 (Serviceguard A.11.19) Enhancements SG 11.19: Support for Shared LVM 11i v3 0903 and later B.04.10 B.11.31.0910.
Table 2-3 HP-UX Guest Patches Affected Guest OS and Version Affected Integrity VM 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. 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.
Table 2-3 HP-UX Guest Patches (continued) 11i v2 A.04.10 PHSS_39786 Bug fix and enhancements HPVM A.04.10 vmProvider — Windows Server 2008 * Attached AVIO Tape Support 11i v2 A.04.10 PHSS_39807 Bug fix HPVM A.04.10 HPVM-Guest – Windows Server 2008 * Attached Tape Support 11i v3 B.04.10 PHSS_39785 Bug fix HPVM B.04.10 vmProvider — Windows Server 2008 * Attached AVIO Tape Support 11i v3 B.04.10 PHSS_39806 Bug fix HPVM B.04.
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.00 PHKL_35739 PHKL_35891 VxVM 4.1 Kernel Patch 04 or 05 Installing VxVM 4.1 Kernel Patch 04 onto HP-UX 11i v2 guest with VxVM boot disk results in an unbootable system.
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.9 Patches Required for SUSE Enterprise Linux Guests Table 2-9 lists the patches that are required in the guests.
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 this Release There are no new virtual machine creation or configuration issues in the V4.2 release. 3.2 Known Issues and Information The following sections describe known issues and information from previous releases that still apply to V4.2. 3.2.1 Failed API Access to Local Running Guest A Failed API access to local running guest.
3.2.4 Do Not Run hpvmstart in Background When Starting Multiple Guests With Resource Conflicts Do not run the hpvmstart command in the background when starting multiple guests that have resource conflicts. The locking that would normally catch and report the resource conflicts does not always work properly in this situation. 3.2.5 Numbers Reported by Glance 4.6 or Later Running on VM Host Depend on Context Glance 4.
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 Changes and Issues in This Release The following sections describe changes, issues, and new information pertaining to this release. 4.1.1.1 Windows Server 2003 Guests No Longer Supported Starting with Integrity VM V4.2, the Windows Server 2003 guest is not supported. 4.1.
version. Installing the other (wrong) version of the Windows guest kit into either version of the Windows operating system results in incorrect operation of the Windows guest. 4.1.2.6 Palhaltlight in Windows Server 2008 Guests The use of palhaltlight is enabled by default in a Windows 2008 guest, which allows the VM Host to be notified when the guest is idle, so that the VM Host avoids spinning the physical processor.
is automatically ejected when the virtual machine is stopped and started during software installation. To complete Windows installation from removable media, follow these steps: • After the automatic reboot, Windows controls the console. When you see the SAC> prompt, use Esc-Tab to change the channel to the product key prompt. • Stop and start the virtual machine and interrupt the automatic boot sequence.
4.1.2.16 Restoring the NVRAM for Windows Guests When a guest has been terminated unexpectedly due to a panic or another critical condition, the guest's boot settings (which are stored in a per-guest NVRAM file on the VM Host) can become corrupted. This can cause problems with subsequent reboots of that guest. To correct the problem, copy the file /opt/hpvm/guest-images/common/nvram to /var/opt/hpvm/guests/vm_name/nvram on the VM Host system.
• • HP-UX 11i v2: PHCO_40685 and PHKL_40684 HP-UX 11i v3: PHKL_39482 and PHCO_38777 You can download these patches from the ITRC website, http://itrc.hp.com 4.2.2 Known Issues and Information The following sections describe known issues and information from previous releases that still apply to V4.2. 4.2.2.
4.2.2.3 Do Not Run Live Kernel Debuggers Inside a Guest Do not run tools that write kernel text, such as live kernel debuggers and performance tools such as kgmon and ktracer inside a guest. Under rare circumstances, these tools cause the guest to panic. 4.2.2.4 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.2.2.
• • • Red Hat Enterprise Linux 4 Installation Guide for x86, Itanium, AMD64 Intel Extended Memory 64 Technology (Intel EM64T) Red Hat Linux Customization Guide For information about the SUSE Linux operating system for HP Integrity servers, see http:// docs.hp.com/en/linuxsuse.html The guest parameter settings for Linux guests are listed in the HP Integrity Virtual Machines 4.2: Installation, Configuration, and Administration manual.
3. Edit the elilo configuration file, /boot/efi/SuSE/elilo.conf, and the fstab file, /mnt/ etc/fstab, to update all entries of the guest boot disk SCSI WWID with the cloned guest boot disk's SCSI WWID. NOTE: The cloned guest's boot disk SCSI WWID can be copied from the /dev/disk/ by-id/ device names.
4.3.2.5 Before Installing the SUSE Linux Guest You must install the tog-pegasus RPM kit prior to installing the SUSE Linux RPM guest; however, the SUSE Linux installation media does not contain the tog-pegasus RPM kit. This RPM kit is available in the “HP Integrity Essentials Foundation Pack for Linux” (also known as HPIEFL for Linux). The SUSE Linux RPM guest kit is actually two parts, a guest kit and a provider kit. The Hpvm.*.
These warnings, errors, and exceptions occur because some optional elements are not provided by the Integrity VM ACPI table. These messages are printed because the SUSE startup/initialization code is trying to reference these optional elements, particularly for configured guest CPUs. The messages do not impede the SUSE boot process; the boot/startup process completes.
Starting: Red Hat Enterprise Linux AS- - - - - - - - - - - ELILO boot: Uncompressing Linux... done Loading initrd initrd-2.6.9-42.EL.img...done i8042.c: i8042 controller self test timeout. Red Hat nash version 4.2.1.8 starting mptbase: ioc0: ERROR - Doorbell ACK timeout (count=4999), IntStatus=80000000! mptbase: ioc0: ERROR - Doorbell ACK timeout (count=4999), IntStatus=80000000! Reading all physical volumes. This may take a while...
Solution Partner Program (DSPP)” webpage on http://www.hp.com, and search for “floating-point assist fault”. 4.3.2.17 Serviceguard in VM Host Configuration The default KILLTIME of 10 seconds (in hpvmsg_stop for a legacy package) and a wait of 10 seconds (in hpvmsg_ext for a modular package) might be too aggressive in some environments and can result in a file system corruption on Linux guests.
… Crash dump information follows this output. Use one of the following solutions to fix either of these issues: • Set the VM Host base_pagesize = 64K (See the base_pagesize(5) manpage for details of determining and setting the VM Host’s base_pagesize.) • Set the guest preferred pagesize to 8K: # hpvmmodify -P vm-name -x tunables=ptsz=13 4.4.4 Guest Device Placement and Adapter Limitation The OpenVMS guest utilizes the PKDRIVER SCSI port driver and the DKDRIVER SCSI class driver.
$len=f$len(uuid) $if (len .eq.
5 Using Integrity VM Commands This chapter contains notes about the Integrity VM commands. 5.1 Changes and Issues in This Release The following sections describe changes, issues, and new information pertaining to this release. 5.1.1 Integrity VM Command Changes The Integrity VM commands have changed in the following ways: • The following new commands have been added: — The hpvmdevinfo command — Reports storage information about a virtual machine.
— — — — — — — — — — — DynMem Min: The minimum memory that can be dynamically allocated to this virtual machine with the dynamic memory allocation capability or automatic memory reallocation (AMR). Memory EntitleDynMem Target: The value of the desired memory allocation for the virtual machine. It may be set manually or automatically (by AMR). The amount of memory entitlement this virtual machine is guaranteed to have allocated to it, provided it has memory demand.
5.2.3 The hpvmdevmgmt -r Command Might Report an Error When a Device is Marked as EXIST=NO On HP-UX 11i v3 VM Hosts, the device management report and repair function hpvmdevmgmt -r might successfully complete, but generate one or more instance of the following error message (one for each legacy device without a corresponding agile device name): # hpvmdevmgmt -r INFO - Analyzing all devices in /dev/rdsk for their device identification strings. This may take a while.
These ERROR messages can often be ignored, because they relate to devices like network adapters (lan0, lan1) or vswitches (localnet, hostnet) that have no unique identifiers. However, when these ERROR messages reference device backing storage items like a disk, volume, file, or directory; check to see if they really do reference the correct device, volume, file, or directory. If they do not, then the guest that uses these devices might not be fully functional.
5.2.11 Errors on Displaying Guest or Vswitch Information While that Information is Being Modified The hpvmstatus, hpvmmodify, hpvmcreate, hpvmclone, and hpvmremove commands might return the following error when another command accesses the same guest's configuration files at the same time: hpvm_guest_get_state:103:No Guest by that name or number If you receive this error when you try to display a guest or vswitch configuration, enter the command again. 5.2.
5.2.17 Manpages Display on Linux Guests The hpvmcollect and hpvminfo commands are available on Linux guests after installing the Linux guest management software kit, as described in the HP Integrity Virtual Machines Installation, Configuration, and Administration manual. To view the command displays properly, enter the following commands on the Linux guest: # export LANG=en_US.
6 Guest Administration This chapter contains information about managing Integrity VM guests. 6.1 Changes and Issues in this Release There are no new guest administration issues in the V4.2 release. 6.2 Known Issues and Information The following sections describe known issues and information from previous releases that still apply to V4.2. 6.2.
For example, using a guest named compass1 (and therefore a user account named compass1), the home directory for user compass1 must be /var/opt/hpvm/guests/compass1. To ensure that the user continues to have administrative console access, use the following command: # hpvmmodify -P compass1 -u compass1:admin 6.6 Creating Virtual Machine Administrator and Operator Accounts In prior versions of Integrity VM, only admin console access is available, and only one such account per guest is allowed.
> -d /var/opt/hpvm/guests/testme \ > testme4 '/var/opt/hpvm/guests/testme' is not a valid directory To enter the command correctly, include the entire directory path. For example: # > > > # # useradd -r no -g users -s /opt/hpvm/bin/hpvmconsole \ -c "Console access to guest 'testme'" \ -d /var/opt/hpvm/guests/testme/. \ testme4 hpvmmodify -P testme -u testme4 passwd testme4 Note the addition of the slash and period (/.
6.13 How to Stop Guests To stop a guest, HP recommends that you perform an operating system shutdown from a privileged account on the guest. If the guest is not responding, use the hpvmstop -g command on the VM Host. Do not stop a guest by killing the hpvmapp process. 6.
6.16.3 File Permission Errors When Checking or Applying Integrity VM Serviceguard Packages to the Cluster Configuration Depending on the system configuration, you might see an error similar to the following when running cmcheckconf or cmapplyconf to the virtual machine packages: # cmapplyconf -P /etc/cmcluster/hpvm-sg1-g4/hpvm-sg1-g4.conf Incorrect permissions for /etc/cmcluster/hpvm-sg1-g4 (40777). Directory must be executable for owner, and not writable by group and others on node hpvm-sg1-h1.
hpvmstop, and hpvmconsole) to start and stop these types of guests. For more information about using Serviceguard to manage virtual machines, see the HP Integrity Virtual Machines 4.2: Installation, Configuration, and Administration manual. 6.16.11 Different Cluster Nodes Report Virtual Machine Status Differently Integrity VM commands can receive different warnings and errors from guests running on different Serviceguard nodes.
7 Networking Information This chapter contains notes about configuring networks for virtual machines. 7.1 Changes and Issues in This Release The following sections provide new information and describe new networking issues in the V4.2 release. 7.1.1 AVIO LAN Devices Left Unclaimed by OpenVMS Guest if vswitch is Down at Boot If you boot an OpenVMS guest while the vswitch is not UP, AVIO interfaces associated with the vswitch might not be claimed in the guest.
• • Attempting to start an OpenVMS guest that is using two different localnet vswitches on the same guest Using a different localnet vswitch than an already active OpenVMS guest is using 7.2 Known Issues and Information The following sections describe known issues and information from previous releases that still apply to V4.2. 7.2.
After configuring the Host's /etc/ntp.conf file, assuming the NTP is already enabled, (that is, the XNTPD variable in /etc/rc.config.d/netdaemons is set to 1, as in export XNTPD-1), you can execute /sbin/init.d/xntpd start to restart xntpd on the HP-UX VM Host. NTP Configuration on a VM Guest Because NTP was not designed to run inside a virtual machine, using NTP on VM guests requires special configuration to be stable.
• • • • • • • • • • • • • • • • • • • • A9784A — Combo Add-in AB352 — Core AB545A — Networking Add-in A7011A — Networking Add-in A7012A — Networking Add-in AB290A — Combo Add-in AB287A — Add-in (10GbE) AD331A — Add-in AD332A — Add-in AD193A — Combo Add-in AD194A — Combo Add-in AD221A — Add-in AD222A — Add-in AD337A — Add-in AD338A — Add-in AD339A — Add-in AD385A — Add-in (10GbE) AD386A — Add-in (10GbE) NC360m — C-class Mezz card NC364m — C-class Mezz card 7.2.
7.2.9 Do Not Use the HP A5506B PCI 10/100Base-TX 4 Port Interface for Virtual Networking Host to guest connectivity might not be reliable when using the HP A5506B PCI 10/100Base-TX 4 Port interface for guest networking. 7.2.10 Integrity VM V4.1 Does not Support Gelan Drivers Gelan drivers are not supported with Integrity VM Version 4.1 and later. 7.2.11 MAC Address Validation Can Be Enhanced When you add a virtual NIC to your guest, Integrity VM checks to make sure the MAC address is unique.
localnet 21 Up Shared N/A N/A vmlan0 22 Up Shared lan0 0x00306ea72c0d 15.13.114.205 vmlan4 23 Up Shared lan4 0x00127942fce3 192.1.2.205 vmlan900 24 Up Shared lan900 0x00306e39815a 192.1.4.205 Check the status of the transmit CKO using the following command: # lanadmin -x cko 4 Hardware TCP/UDP (IPv4) transmit checksum offload is currently enabled. Hardware TCP/UDP (IPv4) receive checksum offload is currently disabled. In this example, the VLANs are configured over the vswitch vmlan4.
7.2.18 Guest AVIO Interface Behavior The following list describes the guest AVIO interface behavior when guest boots while vswitch is down or resetting: • • • If you boot a guest while the vswitch is not up, AVIO interfaces associated with the vswitch might not be claimed in the guest. For example, this might occur if the guest is booted prior to booting the vswitch or if the corresponding network interface on the VM Host is not cabled.
7.2.21 Other Issues and Notes The following list provides additional issues with the Integrity VM V4.2 release of which you should be aware : • • • 74 If you modify the MAC address of an interface in the guest, the hpvmstatus command in the VM Host does not display the current MAC address correctly. There is no fix or workaround for this problem at this time.
8 Storage Information This chapter contains information about storage devices used as backing stores for guest virtual devices. 8.1 Changes and Issues in This Release The following section provides new information pertaining to this release. 8.1.1 Storage Interface Support for OpenVMS Guests The OpenVMS guest supports only the AVIO interface, however, Integrity VM commands allow you to configure both AVIO and VIO devices to a guest. These VIO devices might not give any apparent errors during the startup.
seen on HP-UX 11i v2 and HP-UX 11i v3 guests with GuestAVIOStor versions earlier than 11.23.0903 and 11.31.0903 respectively. In this case, the HostAVIOStor version is 11.31.0903 or 11.31.0909. • The following fixes are included in the GuestAVIOStor version HP–UX 11i v3 1003 driver: — Unload of HP-UX 11 v3 guest AVIO driver (gvsd) might cause guest to panic.
8.2.3 Agile Device Name Recommendations The Integrity VM commands supports mass storage agile device names. Use of agile device names (with the exception of attached devices using avio_stor, which uses the hardware path) for configuring storage devices is highly recommended as it provides VM Host multipathing benefits. 8.2.4 Configuration Limits A guest can have up to 158 LUNs — 128 AVIO and 30 VIO. A guest can have a maximum of 30 file backing stores, including both AVIO and VIO. 8.2.
disk disk adisk disk disk disk disk disk /dev/dsk/c0t0d0s3 sdisk CLAIMED /dev/dsk/c3t0d0 18 0/0/5/0.1.0 sdisk CLAIMED /dev/dsk/c3t1d0 20 0/0/5/0.2.0 sdisk CLAIMED /dev/dsk/c3t2d0 17 0/0/6/0.0.0 sdisk CLAIMED /dev/dsk/c4t0d0 19 0/0/6/0.1.0 sdisk CLAIMED /dev/dsk/c4t1d0 21 0/0/6/0.2.0 sdisk CLAIMED /dev/dsk/c4t2d0 23 0/0/6/0.3.0 sdisk CLAIMED /dev/dsk/c4t3d0 25 0/0/6/0.4.0 sdisk CLAIMED /dev/dsk/c4t4d0 16 0/0/5/0.0.
8.2.11 The hpvmmodify Command Fails to Change a DVD The hpvmmodify command might fail to change a Virtual FileDVD if the device has already been modified by the virtual console. The hpvmstatus command displays the current status of the Virtual FileDVD, which might not be in its original resource state. To see the original resource statement, which is required by the hpvmmodify command to change a Virtual FileDVD, use the hpvmstatus —D command. 8.2.
8.2.17 AVIO Limitations The following sections describe the current limitations using AVIO. 8.2.17.1 Modifying the Storage Adapter from scsi to avio_stor If you attempt to modify a storage adapter from scsi to avio_stor on a port for a running guest, the hpvmmodify command allows the change, but the change lasts only until the next guest startup. In addition, the hpvmnet command displays incorrect port information for the currently running guest until the guest is stopped and restarted. 8.2.17.
• • • PciFtn = 0 Addr (Target Id) = 22 (0x16) Lun = 0 Note that Addr (Target Id) is decimal in the hpvmstatus display, and PciFtn and Lun are always zero (0). The Integrity VM guest EFI device path encodes PciBus, PciDev, and Addr (Target Id) from the hpvmstatus display: PciDev | | PCIFtn PciBus | | Addr(Target Id) | | | | V V V V blk16 : Acpi(PNP0A03,0)/Pci(2|0)/Scsi(Pun16,Lun0) PciFtn (PCI function) and Lun# are always zero (0).
The following example shows the get_info option with the gvdsmgr utility: # gvsdmgr get_info -D /dev/gvsd0 -q lun=/dev/rdsk/c0t6d1 Tue Oct 2 13:35:32 2007 Lun DSF VSD LUN Id Lun Hardware path LUN State : : : : /dev/rdsk/c0t6d1 0x16 0/0/2/0.6.
9 Migrating Virtual Machines This chapter contains information about migrating virtual machines. 9.1 Changes and Issues in This Release The following section provides updated information about online migration in the V4.2 release. 9.1.1 Online Migration Support Limited to System with Compatible Processors Online migration support among Integrity servers is limited by the processor architecture.
9.2.3 NR Guest State A guest is placed in the Not Runnable (NR) state when it is the source of a successful migration. The guest is also marked Not Modify and Not Visible. The guest can also be placed in the NR state by the administrator using thehpvmmodify command, for example: # hpvmmodify -P guestname -x register_status=disabled The NR guest state appears on the hpvmstatus command output as Off (NR).
In most cases, migrating a guest saturates a 1 GB network. Migrating more than one guest at a time on a network usually takes longer than migrating them sequentially, and the guest frozen phase is longer as well. Do not attempt to migrate more than one guest at a time on a single VM Host or network. 9.2.8 Online Migration on the Target VM Host is the Same as Starting the Guest on the Target VM Host Online migration on the target VM Host system is equivalent to starting the guest on the target VM Host.
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.2 release. 10.2 Known Issues and Information The following sections describe known issues and information from previous releases that still apply to V4.2. 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: • 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 Beginning with Integrity VM Version 3.0, releases will be supported for a minimum of three years. Integrity VM Version Release Date Expected End of Support Date Current Status A.01.00 December 2005 December 2007 Not supported A.01.
11.3 VM Host OS and Server Support Integrity VM Host Integrity VM or Server Support Version A.03.50 Integrity VM Version B.04.00 Integrity VM Version B.04.10 Integrity VM Version B.04.20 Notes VM Host OS Support HP-UX 11i v3 September 2008 HP-UX 11i v3 March through September 2009 HP-UX 11i v3 March 2010 New Integrity VM versions support the latest HP-UX OE release at the time of the Integrity VM release.
11.5 Windows and Linux Guest Support Type of Guest OS Integrity VM Version A.03.50 Integrity VM Version B.04.00 Integrity VM Version B.04.10 Integrity VM Version B.04.
11.6 HP Serviceguard Support Packages or Nodes Integrity VM Version A.03.50 Integrity VM Version B.04.00 Integrity VM Version B.04.10 Integrity VM Version B.04.20 Notes Serviceguard – Virtual machines as packages (Serviceguard running on VM Host) Serviceguard release • A.11.16 • A.11.17 • A.11.17 w/ SMS A.01.00 • A.11.18 • A.11.18 w/ SMS A.01.01 • A.11.18 w/ SMS A.02.00 Serviceguard release • A.11.18 • A.11.18 w/ SMS A.02.00 Serviceguard release • A.11.
11.7 Storage Interface Support Integrity VM Version A.03.50 (Both VIO and AVIO) Integrity VM Version Integrity VM Version B.04.00 (both VIO and B.04.10 (both VIO and AVIO) AVIO) Integrity VM Version Notes B.04.20 (both VIO and AVIO) • Fibre Channel adapters supported by the FCLP (FibrChanl-02), TD or FCD driver • SCSI adapters supported by the C8xx, MPT, or CISS drivers • IDE adapters supported by the SIDE driver • USB support of the UsbScsiAdapter driver and USB 2.
NOTE: LVM mirroring in a VM is supported with 0909 or later versions of HostAVIOStor (on the VM Host) and GuestAVIOStor (on the guest). Backing Store Integrity VM Version A.03.50 Integrity VM Version B.04.
card can be configured with Auto Port Aggregation (APA), with the resulting port supported as indicated in the following table: Virtual Network Adapter Type Integrity VM Version Integrity VM Version A.03.50 B.04.
