HP Integrity Virtual Machines 4.2.5: Release Notes HP Part Number: 5900-1482 Published: January 2011, Edition 13.
© Copyright 2011 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.....................................................................
2.9 Patches Required for SUSE Enterprise Linux Guests......................................................................36 3 Creating Virtual Machines..........................................................................................37 3.1 Changes and Issues in this Release.................................................................................................37 3.2 Known Issues and Information...............................................................................................
4.3.1 Changes and Issues in This Release........................................................................................46 4.3.2 Known Issues and Information...............................................................................................46 4.3.2.1 Using Linux Guests.........................................................................................................46 4.3.2.2 SUSE Linux Cloned Guests Boot-Disk Boot Problems...................................................47 4.3.
5.2.13 Do Not Attempt to Remove Busy Virtual Devices................................................................58 5.2.14 Missing uuid or .vmid Files................................................................................................58 5.2.15 Maintain Minimum Entitlement...........................................................................................58 5.2.16 Actual Running Entitlement Might Differ from Configured Entitlement............................58 5.2.
.2.2 AVIO LAN Devices Left Unclaimed by OpenVMS Guest if vswitch is Down at Boot..........70 7.2.3 Known Limitation on OpenVMS Guests and HP-UX Guests Sharing the same vswitch......71 7.2.4 OpenVMS Guests Support vswitch-based VLAN Configuration and Not Guest-based VLANs.............................................................................................................................................71 7.2.5 Networking Interface Support for OpenVMS Guest............................................
.2.20.2 iSCSI-Based Backing Stores with AVIO Require Host AVIOstor B.11.31.1009.01.........84 8.2.20.3 Modifying the Storage Adapter from scsi to avio_stor.........................................84 8.2.20.4 GuestAVIOStor Bundle not Installed but AVIO Storage Device is Configured...........84 8.2.20.5 Longer Failure Reporting Time for AVIO Devices on 11i v2 Guests............................84 8.2.20.6 Online Modification of AVIO Devices Might Fail.........................................................
11.8.3 EVA Series Firmware Requirement.....................................................................................101 11.9 Network Interface Support..........................................................................................................102 11.10 AVIO Support............................................................................................................................102 A hpvmhostgdev Manpage............................................................................
List of Tables 1-1 1-2 2-1 2-2 2-3 2-4 2-5 2-6 2-7 2-8 2-9 10 Guest and VM Host Support.........................................................................................................16 Guest Management Software Kit Locations..................................................................................17 VM Host Patches...........................................................................................................................27 Do Not Install Product or Patch...................
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.
HP Insight Remote Support HP strongly recommends that you install HP Insight Remote Support software to complete the installation or upgrade of your product and to enable enhanced delivery of your HP Warranty, HP Care Pack Service or HP contractual support agreement.
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.5 release introduces several new features including support for the HP-UX 11i v3 1009 as a VM Host. The following patches and software products are required: • On the 11i v3 VM Host: — PHSS_41543 1.0 HPVM B.04.20.
1.1 New Features and Enhancements in This Version of Integrity VM This section describes how the current version of Integrity VM has been enhanced over previous versions. The following feature has been included in this release of Integrity VM: • Support for the HP Integrity rx2800 i2 • Dynamic memory support enabled by default- Dynamic memory is now enabled by default for support of the statistics—gathering feature in guests. For guests that are not currently using dynamic memory, there should be no effect.
Table 1-1 Guest and VM Host Support (continued) Guests VM Host on HP Integrity server blades1 VM Host on HP Integrity Superdome 21 VM Host on HP Integrity Servers VM Host on HP Integrity rx2800 i2 HP-UX 11i v3 0903 Yes No Yes No HP-UX 11i v3 0909 Yes No Yes No HP-UX 11i v3 1003 Yes No Yes No HP-UX 11i v3 1009 Yes Yes Yes Yes HP OpenVMS V8.
the guest management software on each guest can cause problems that are difficult to diagnose and solve.
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.05 is supported on HP Integrity servers or nPartitions running HP-UX 11i v3 September 2010 1009).
2.3.1 After Installation, Integrity VM Might Hang Upon Reboot Due to a timing issue, Integrity VM V4.2.5 might hang upon reboot after it is installed. This is an intermittent issue. To fix the problem, install patch PHKL_41227, which will be available from the HP IT Resource Center website: http://itrc.hp.com by the middle of August 2010. 2.3.2 Unable to Communicate with the FSS Agents Messages in /var/opt/hpvm/ common/command.log When Integrity VM is stopped either with the /sbin/init.
• 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 command to modify all guests to use the new USB DVD device.
2.3.10 Failures in Key Applications Some applications fail when run on HP-UX with large pages configured (larger than 8K).
Dynamics Virtual Software Environment software versions earlier than V4.0 must upgrade to HP Insight Dynamics — VSE V4.1 (which contains VMMgr V4.0). VMMgr V4.0 is designed to run on HP-UX 11i v3 with Integrity VM V4.2.5 or earlier. It cannot use or display any new features in Integrity VM V4.2,5, but does support new features in HP-UX 11i v3, including the new agile addressing hardware paths and device files for storage devices. This means the following: • The VMMgr product V4.
utilities and Serviceguard, as documented in the HP Integrity Virtual Machines Installation, Configuration, and Administration manual. • Using backup solutions for VM Host and guest backups Backup solutions such as HP Data Protector or Veritas NetBackup can be used on both the VM Host system and the guest systems. Consult the support matrix of such products for supported versions. Install the backup (client) agents on the VM Host and the guests.
If you have installed the HP Integrity Virtual Machines Manager software, you must upgrade it to a version that supports this version of Integrity VM. To use Integrity Virtual Machines Manager, you must install the VMProvider bundle that is provided with Integrity VM. If you upgrade Integrity VM, be sure to keep the VMProvider up-to-date also. If the VMProvider version does not match the Integrity VM version, the Integrity Virtual Machines Manager will not work properly.
installed, installing the patch by itself does not prevent the problem. Reconfiguration of dynamic memory settings is necessary for the guest to be able to boot again.
Table 2-1 VM Host Patches (continued) Affected HP-UX (VM Host) Version 28 Fix Description/Impact Comment 11i v2 0505 thru 0606 A.02.00 or later PHKL_33604 (11.23.0609) PHKL_33605 (11.23.0609) FSS Must install PHKL_33605 before PHKL_33604. 11i v2 0512 thru 0606 A.01.00 or later PHKL_33827 (11.23.0609) Bug fix Resolves panic on guest. Specific to EVA8000 environment. (corrected to be Host patch, not guest) 11i v2 0505 or later A.01.
Table 2-1 VM Host Patches (continued) Affected HP-UX (VM Host) Version Affected Integrity VM Version Fix Description/Impact Comment 11i v2 0712 A.03.50 PHSS_38297 Bug fix Mandatory patch: HPVM A.03.50 HPVM-CORE (cell-based memory tuning, support for USB 2.0 driver, other fixes). 11i v2 0712 A.03.50 PHSS_38298 Bug fix Mandatory patch: HPVM A.03.50 VMAGENT vmProvider (cell-based memory tuning). 11i v2 0609 to 0712 A.03.00 or later PHSS_38610 Bug fix Mandatory patch: HPVM B.04.
Table 2-1 VM Host Patches (continued) 30 Affected HP-UX (VM Host) Version Affected Integrity VM Version Fix Description/Impact Comment 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.10 HPVM-VMSGTK 11i v3 0903 and later B.04.10 PHKL_39407 Bug fix 11i v3 USB 2.0, DVD Write, Cumulative USB Patch (Avoid lengthy hpvmcreate and hpvmmodify operations when adding USB DVD. 11i v3 0903 and later 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 B.11.31.0910.01 (HostAVIOStor) Enhancements HostAVIOStor: Support for Shared LVM and bug fixes 11i v3 1003 B.04.20 PHKL_40383 Bug fix HostAVIOStor: AVIO Host driver 11i v3 1003 B.04.20 PHSS_40875 Enhancements HPVM core: Itanium 9300 series host and OpenVMS guest support 11i v3 1003 B.04.
Table 2-2 Do Not Install Product or Patch Affected HP-UX Host Version Affected Integrity VM Version Fix Description/Impact Comment 11i v2 0505 or later A.02.00 or later PHNE_35793 igelan patch An Integrity VM guest that uses a virtual interface that belongs to an IGELAN interface configured on the Integrity VM Host can experience hangs with network services like ping, NFS, rcp, ftp for data transfers that use full-sized frames. 2.
11i v2 0505 or later A.01.00 or later 11i v2 Intel Itanium 9000 (Montecito) A.01.20 or later 11i v2 0505 or later PHNE_35182 Bug fix Cumulative ARPA transport patch, resolves panic. Requires prerequisite PHNE_32277. 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. A.01.20 or later PHSS_35863 (Serviceguard A.11.16) PHSS_35427 (Serviceguard A.11.17) Bug fix Specific to Serviceguard.
Table 2-3 HP-UX Guest Patches (continued) 34 11i v2 0505 through 0706 A.03.50 PHKL_37091 (11.23.0712) Bug fix 11i v3 A.03.50 PHSS_37843 Bug fix 11i v3 B.04.10 PHSS_39376 Bug fix HPVM-Guest 11i v2 A.04.10 PHSS_39377 Bug fix HPVM-Guest 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.
Table 2-3 HP-UX Guest Patches (continued) 11i v2 0712 A.04.20.05 PHSS_41415 Enhancements 11i v2 guest vmGuestLib VirtProvider enhancements 11i v2 0712 A.04.20.05 PHSS_41416 Enhancements 11i v2 vmTools Virtprovider enhancements 11i v3 0803 or later B.04.20.05 PHSS_41413 Enhancements 11i v3 VMGuestLib VirtProvider enhancements 11i v3 0803 or later B.04.20.
Table 2-6 Windows Patches Affected Guest OS and Affected Integrity VM Version Version Fix Description/Impact Comment Windows Server 2003 A.02.00 or later SSM 4.6 Bug fix Microsoft patches correct a compiler issue that can affect Windows guests in various ways. Table 2-7 lists patches and products that you should not install on Windows 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.5 release. 3.2 Known Issues and Information The following sections describe known issues and information from previous releases that still apply to V4.2.5. 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 There are no new Windows guest issues in the V4.2.5 release. 4.1.2 Known Issues and Information The following sections describe known issues and information from previous releases that still apply to V4.2.5. 4.1.2.
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. The VM Host can then use the physical processor for other useful purposes (for example, running other guests or running host service processes and threads) whenever the Windows guest does not need it.
• • • • • 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. Before the system is allowed to continue, from the virtual console, execute the necessary insert (IN) command to reload the media. After the media is reloaded into the virtual DVD, select the Windows Media install (the first boot option) and allow the system to boot.
copy the file /opt/hpvm/guest-images/common/nvram to /var/opt/hpvm/guests/vm_name/nvram on the VM Host system. This procedure restores the copy of the NVRAM that was used when the guest was created. Then you can used the EFI Boot Manager to recreate the guest's boot path and other data. (The installed guest's operating system should be intact and unaffected by the corruption.) To build the EFI Boot Menu Entry for Windows Server 2003 guest: 1.
[my_guest] vMP> in Insertable Guest Devices Num Hw-path (Bus,Slot,Tgt) Gdev -------------------------------------------[1] 0/0/1/0.1.0 (0,1,1) dvd Enter menu item number or [Q] to Quit: 1 Insertable File Backing Stores Num File --------------------[1] 1131_0909_DVD1.iso [2] 1131_0909_DVD2.iso Enter menu item number or [Q] to Quit: 1 Confirm insertion action G - Go F - Force Enter menu item or [Q] to Quit: g 5.
------------------------------------------------------------------------[1] 0/0/0/0.1.0 (0,0,1) dvd file /tmp/iso/1131_0909_DVD1.iso Enter menu item number or [Q] to Quit: 1 Confirm eject action G - Go F - Force Enter menu item or [Q] to Quit: g c. Insert the second DVD: [my_guest] vMP:VM> in Insertable Guest Devices Num Hw-path (Bus,Slot,Tgt) Gdev -------------------------------------------[1] 0/0/0/0.1.
• • 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.4 HP-UX 11i v3 Guests Might Fail to Configure Interface Cards Due to Lack of Memory HP-UX 11i v3 guests with small memory resources (less than or equal to 2 GB RAM) might fail to configure one or more virtual interface cards.
4.2.2.7 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.8 iCAP Commands Fail on HP-UX Guests iCAP is installed as part of the HP-UX OS installation. Install-time configuration of iCAP reports failure with messages similar to the following: NOTE: ERROR: ERROR: ERROR: Checking for partitionable system. Software configuration has failed.
The guest parameter settings for Linux guests are listed in the HP Integrity Virtual Machines 4.2: Installation, Configuration, and Administration manual. For information about installing Linux guests, see the HP Integrity Virtual Machines 4.2: Installation, Configuration, and Administration manual. 4.3.2.2 SUSE Linux Cloned Guests Boot-Disk Boot Problems SUSE Linux (SLES) cloned guests have issues with the cloned guest boot disk.
NOTE: The cloned guest's boot disk SCSI WWID can be copied from the /dev/disk/ by-id/ device names. For example, the cloned guest boot disk device names are as follows: Rescue:~ # ls -l /dev/disk/by-id total 0 lrwxrwxrwx 1 root root 9 Dec 5 17:08 scsi-0HP_Virtual_FileDVD_isoLinuxSLES10-SP2SLES-10-SP2- 9 Dec 5 17:08 scsi-3600508b4001049440001200002f20000 -> ../../sda DVD-i -> ../../sr0 lrwxrwxrwx 1 root root 4. lrwxrwxrwx 1 root root 10 Dec 5 17:08 scsi-3600508b4001049440001200002f20000-part1 -> ../.
The SUSE Linux RPM guest kit is actually two parts, a guest kit and a provider kit. The Hpvm.*.rpm kit contains: • Tuning scripts • hpvminfo • hpvmcollect • Guest library The Hpvmprovider.*.rpm kit contains the VMprovider and related files. This RPM requires that both the hpvm and tog-pegasus kits must be installed. http://h20293.www2.hp.com/portal/swdepot/displayProductInfo.
processor file system, which might lead to confusion as to the actual number of CPUs configured in the guest. 4.3.2.8 HP SIM CMS Cannot Connect to SLES10 over SSH SSH password authentication is turned off by default in SLES10. In this default setting, HP SIM CMS cannot connect to the SUSE guest. To enable password authentication for SSH, do the following: 1. Login to SUSE. 2. Edit the /etc/ssh/sshd_config file. 3. Set passwordauthentication value to yes. 4. Restart sshd.
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... Found volume group "VolGroup00" using metadata type lvm2 2 logical volume(s) in volume group "VolGroup00" now active INIT: version 2.85 booting Welcome to Red Hat Enterprise Linux AS 4.3.2.11 Disable IPv6 on Linux Guests Integrity VM does not support IPv6 on Linux guests.
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. HP recommends that you tune this value, so that the file systems on the guests are successfully unmounted before the guest is powered off. 4.
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.
$ $ $ $ $ $ $ part2 part3 part4 part5 = = = = f$fao("!AS",f$ext(20,4,uuid)) f$fao("!AS",f$ext(16,4,uuid)) f$fao("!AS!AS",f$ext(14,2,uuid),f$ext(12,2,uuid)) f$fao("!AS!AS!AS!AS!AS!AS", f$ext(10,2,uuid),f$ext(8,2,uuid), f$ext(6,2,uuid),f$ext(4,2,uuid), f$ext(2,2,uuid),f$ext(0,2,uuid)) pr_uuid = f$edit("''part1'-''part2'-''part3'-''part4'-''part5'", "lowercase") write sys$output "SYSTEM_UUID=''pr_uuid'" 4.4.
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.
the kernel version, Linux guests might support enabling or disabling virtual CPUs by writing into /sys/devices/system/cpu/cpuN/ online, as on a physical system. Disabled virtual CPUs no longer show up in the guest in commands such as top or GlancePlus, and no longer consume resources on the host. However, disabled virtual CPUs still appear on the host, for example in the hpvmsar command. 5.2.
devices if they have legitimate WWIDs in the /var/opt/hpvm/common/hpvm_mgmtb_pre1131 device database file. 5.2.6.2 Error Comments from hpvmdevtranslate Command The hpvmdevtranslate command creates ERROR messages for all devices used by guests that have WWID set to WWID_NULL. This message indicates that no translation could be done. 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.
virtual device to sharable using the hpvmdevmgmt command. Incorrectly marking a virtual device as sharable can lead to device conflicts and data corruption if multiple guests access it concurrently. In particular, attached devices using scsi (as opposed to the avio_stor) adapter type (tape, burner, or changer) should not be made sharable. 5.2.
hpvmmodify: WARNING (test_duperr): File size of: 0 (bytes) for disk backing file: /tmp/zero.size.2 must be equal to or greater than: 512 (bytes), or the device may not show up in the guest when booted. Remove the failing device from the guest configuration using the hpvmmodify command. 5.2.
6 Guest Administration This chapter contains information about managing Integrity VM guests. 6.1 Changes and Issues in this Release The following sections discuss new guest administration information in the V4.2.5 release. 6.1.1 Integrity VM Fully Supported with ID-VSE Logical Server Management 6.2 Integrity VM now fully supports ID-VSE Logical Server Management (LSM).
NOTE: If you add new devices in the future, run the hpvmhostgdev -a script again. If you want to select the guest devices instead of adding all of them to the gdev database, create a list of unused disks and logical volumes with the -l option and pipe them to a file. Use the specified device-list file to add devices for guest use with the -f option. # hpvmhostgdev -l > devicelist # hpvmhostgdev -f devicelist For information about the hpvmhostgdev script, see Appendix A (page 103). 5.
6.2.1 Creating Virtual Machine Administrator and Operator Accounts In versions of Integrity VM prior to A.03.00, Admin console access is available, and 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.2.4 (page 63). 6.2.2 Administrator Account Names Integrity VM Version 4.
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 access to the virtual console, and
devices in the guest configuration and evaluate the Host storage configuration with respect to these devices and the adapters used to access them. 6.2.8 Do Not Add User Accounts to the hpvmsys Group The hpvmsys group implements the security model for the VM Host and guests. The hpvmsys group is automatically added to /etc/group when Integrity VM is installed. Do not add user accounts to this group. 6.2.
used by guests but requires users to verify or provide activation modes and package dependencies for the backing stores. The hpvmsg_package script creates the package configuration in the package directory: /etc/cmcluster/hpvm-name/hpvm-name.conf. Inside the configuration file are instructions, examples, and default and assigned named-values pairs describing the resources used by the virtual machines and controlled and monitored by Serviceguard.
6.2.13.10 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.2.13.11 Do not Use Integrity VM Commands to Manage Distributed Guests Guests configured as Serviceguard packages should be stopped and started using Serviceguard package control commands.
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 networking information for the patch kit applied to the V4.2.5 release. 7.1.1 AVIO LAN Driver on OpenVMS Guest Does Not Support Checksum Offloading (CKO) OpenVMS does not support checksum offloading.
lan0 lan1 lan2 lan3 lan900 lan901 lan902 lan903 lan904 UP UP UP UP UP DOWN DOWN DOWN DOWN 0x0017A4AB5461 0x0017A4AB5460 0x001A4B06E90A 0x001A4B06E90B 0x001A4B06E90B 0x000000000000 0x000000000000 0x000000000000 0x000000000000 igelan igelan iether iether hp_apa hp_apa hp_apa hp_apa hp_apa 1000Base-T 1000Base-T 1000Base-T 1000Base-T hp_apa hp_apa hp_apa hp_apa hp_apa lan900 To configure a PPA of the VLAN interface (VPPA) with a VLAN ID = 20 on the lan900 aggregate, enter the following: # nwmgr -a -S vlan
booted prior to booting the vswitch, or if the corresponding network interface on the VM Host is not cabled during the guest boot time. If you encounter this problem, perform the following steps: 1. Fix the vswitch state; that is, ensure that the hpvmnet command displays the vswitch state as UP. 2. Once the vswitch is started, reboot the OpenVMS guest to get the AVIO LAN devices recognized, which ensures that all the AVIO LAN interfaces that are configured through this vswitch are recognized by the guest.
alias eth0 lgssn 2. Issue the depmod -a command to inform the kernel of the device type change. After you issue the command, you should see the following (or similar) line in modules.dep file: /lib/modules/2.6.9-55.EL/kernel/drivers/net/lgssn/lgssn.ko: For example: # grep lgssn /lib/modules/2.6.9-42.EL/modules.dep /lib/modules/2.6.9-42.EL/kernel/drivers/net/lgssn/lgssn.ko: These two steps enable automatic loading of the AVIO Linux LAN guest driver (lgssn) at boot time. 7.2.
be allowed to deliver time (allow guests to be a time consumers). Because a VM guest never delivers time, you do not need to configure the local clock (server 127.127.1.0) or an ntp.drift file. So, the ntp.conf file on a VM guest should be as simple as the single line: server minpoll 4 maxpoll 6 After configuring the guest's /etc/ntp.conf file, assuming NTP is already enabled (that is, the XNTPD variable in /etc/rc.config.
• • NC360m — C-class Mezz card NC364m — C-class Mezz card 7.2.11 Calculating the Actual Utilization of the Virtual Network Card The emulation of the virtual network I/O card is based on the Intel I8254X family. Thus, the virtual network card (vNIC) is presented to the guest operating system as PCI-X 1000Base-T with the speed of 1 Gb regardless of the physical network interface card backing the vswitch.
You can set the HPVMMACADDRFRAMES tunable to zero (0), which completely eliminates the MAC address verification. However, HP recommends that you do so after you configure all of your guests and confirm that there are no conflicts with MAC addresses in your network environment. To boost virtual network performance, create additional vswitches and allocate them across guests. 7.2.18 Auto Port Aggregation (APA) is Supported on the VM Host, Not on the Guest Integrity VM does not support running APA on a guest.
In this example, the VLANs are configured over the vswitch vmlan4. This vswitch is created on PPA 4 on the VM Host. The following table shows the nwmgr command that performs the task as the lanadmin command: Task Legacy Command nwmgr Command Turn off CKO on PPA 4 by entering this command on the VM Host. # lanadmin -X send_cko_off 4 Hardware TCP/UDP (IPv4) transmit checksum offload is currently disabled. # nwmgr -s -A tx_cko=off -c 4 lan2 current values: Transmit Checksum Offload=Off 7.2.
• • You change the network interface characteristics on the VM Host; for example, by using the nwmgr command to change checksum offloading (CKO). You notice that there is no communication from an avio_lan interface to a lan interface after booting the guest(s) while the vswitch is down. For information about how to restart vswitches, see the HP Integrity Virtual Machines 4.2: Installation, Configuration, and Administration manual.
NOTE: These change are not carried over to subsequent reboots of the system. To maintain the configuration over reboots of the guest, the administrator must edit the guest file, /etc/ rc.config.d/hpigssnconf. For each igssn device that must have drv_pr disabled, you must construct a block of information in the hpigssnconf file.
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 There are no new storage issues in the V4.2.5 release. 8.2 Known Issues and Information The following sections describe known issues and information from previous releases that still apply to V4.2.5. 8.2.
— — • If the LV or file backing store file name is 55 characters long and the guest is a HP-UX 11i v3 guest, guest panic or disk dsf name change is seen on subsequent guest reboots. When guest storage applications (for example, dd, diskinfo, and so on) attempt to access a device special file, an “Invalid argument” error might be returned. This problem is 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.
8.2.6 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.7 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.14 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.20 AVIO Limitations The following sections describe the current limitations using AVIO. 8.2.20.1 iSCSI-Based Backing Stores Not Supported with Physical Volumes Under Certain Circumstances iSCSI-based backing stores are not supported with a physical volume under a logical volume that is then exposed to guests as a virtual disk using AVIO. 8.2.20.2 iSCSI-Based Backing Stores with AVIO Require Host AVIOstor B.11.31.1009.
# hpvmstatus -P aviotest [Storage Interface Details] Guest Physical Device Adaptor Bus Dev Ftn Tgt Lun Storage Device ======= ========== === === === === === ========= ========================= disk avio_stor 0 2 0 22 0 disk /dev/rdsk/c82t15d3 The following statistics are displayed in this example: • PciBus = 0 • PciDev = 2 • 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).
In this example, exp1 / exp2 represents the quotient from exp1 divided by exp2 (integer division), and exp1 % exp2 finds modulo of exp1 divided by exp2 (that is, finds the remainder of an integer division). 2. get_info option of the gvsdmgr utility If you are using the HP-UX DSF, the following gvsdmgr option can be used to get the VSD LUN ID, which is the same as the Addr (Target Id) in the hpvmstatus display. The gvsdmgr utility displays VSD LUN Id as a hexidecimal number.
1. 2. In the guest, rmsf the target path (tgtpath Class in ioscan display) corresponding to the lun path. In the guest, perform an ioscan. 8.2.22 Storage for Deactivated Volume Groups not Protected by Integrity VM Storage Management When an LVM volume group is deactivated, the storage (physical volumes) used by that storage is designated as unused by HP-UX system administration tools such as System Management Homepage (SMH). This is also true for Integrity VM storage management.
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.5 release. 9.1.1 Online Migration Support The following list provides the supported online migration paths for HP-UX guests: • A V4.2 guest can be online migrated to V4.2.5. • A V4.2 guest plus general release patches can be online migrated to V4.2.5. • A V4.2.
Opening minor device and creating guest machine container Creation of VM, minor device 1 hpvmmigrate: ERROR (vmname): Remote message: Target guest exited. Status 2. hpvmmigrate: ERROR (vmname): Remote message: Unable to start guest on target. In this case, use the following workaround: 1. Enter the following: # swremove vmOVMMSW.OnlineMigr-SW 2. Force a reinstall of the 4.
9.2.7 Unpresenting SAN Devices to Integrity VM Hosts Unpresenting SAN devices that were configured to be used by guests causes the guest to fail to start. If SAN devices must be unpresented, guests configured to use those devices should be reconfigured to no longer require them.
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.5 release. 10.2 Known Issues and Information The following sections describe known issues and information from previous releases that still apply to V4.2.5. 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.
# hpvmstatus -P guestname -d | grep -w scsi # hpvmstatus -P guestname -d | grep -w lan • Integrity VM V4.2.5 will be the last release to support Microsoft Windows and Linux guests. Integrity VM V4.2.5 is the last release that will support Microsoft Windows and Linux guests. Beginning with the next Integrity VM release, HP-UX and OpenVMS guests will be supported. • Use of legacy device special files (DSFs) to define virtual storage will not be supported in a future release.
11.4 HP-UX Guest Support Integrity VM Type of Guest Version OS Support A.03.50 Integrity VM Integrity VM Version Version B.04.00 B.04.10 Integrity VM B.04.20 Integrity VM B.04.20.
NOTE: For information about required patches, see Chapter 2 (page 19). HP-UX patches might be required for proper operation. Install these patches on HP-UX guest operating systems as necessary. For specific patch information, see the patch tables in Chapter 2 (page 19) . 11.5 Windows and Linux Guest Support Type of Guest OS Windows Linux Integrity VM Version A.03.50 Integrity VM Version B.04.
1 2 Intel® Itanium® 2 9000 Series and Intel Itanium 2 9100 Series Requires V4.2 with the following VM Host patches: PHSS_40875 1.0 HPVM B.04.20 CORE PATCH PHSS_40876 1.0 HPVM B.04.20 VMAGENT PHSS_40901 1.0 HPVM B.04.20 VMMIGRATE PATCH 3 Support for the latest Intel® Itanium® Processor 9300 Series 11.7 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 Integrity VM Version B.04.20.
11.8 Storage Interface Support Integrity VM Version A.03.50 (Both VIO and AVIO unless explicity excluded) Integrity VM Version B.04.00 (both VIO and AVIO unless explicitly excluded) Integrity VM Version B.04.10 (both VIO and AVIO unless explicitly excluded) Integrity VM Version B.04.20 (both VIO and AVIO unless explicitly excluded) Integrity VM Version V.04.20.
11.8.2 Multipathing Software Support Multipathing software is supported on the Integrity VM Host system. Unless specified otherwise, multipathing is supported for use with either legacy virtual I/O (virtual adapter type specified as scsi) or AVIO (virtual adapter type specified as avio_stor). The required version for these products is determined by the software vendor and the release of HP-UX installed on the VM Host system.
• • On EVA 4000/6000/8000, all released firmware revisions support Active-Active configuration. Therefore, no action is necessary on these arrays. EVA 3000/5000 arrays need minimum firmware revisions of VCS v4.004 (Active-Active firmware). For more information about EVA firmware upgrades, see the HP Services EVA upgrade website: http://hpswest.corp.hp.com/VCSUpgradeProgram.asp. 11.9 Network Interface Support VM Host I/O is HP-UX based.
A hpvmhostgdev Manpage 103
hpvmhostgdev(1M) NAME hpvmhostgdev -- Manages Integrity VM Host devices available for virtual machine access. SYNOPSIS hpvmhostgdev [-H | [-u] | { -a | -c {disklist|lvlist} | -l [>devlistfile] } | -d | -f devlistfile| -r | -v { all|assigned|unassigned }] DESCRIPTION The hpvmhostgdev command analyzes disklist and lvlist output searching for unused disks and logical volumes (LVs). It uses its results to add unused devices to the Integrity VM device database as guest devices (gdevs).
-r -u Recovers the Integrity VM device management database. Uses disklist device cache (Do not force hardware scan.). NOTE: This option is used to speed up the disklist command to obtain unused disks. Use the -u option before using the following options: • -a • -c disklist • -l -v Verifies add and delete operations by this script (with the AUTOGDEV=YES attribute). • all — lists all guest devices. • assigned — lists all guest devices configured by any guests.
hpvmcollect(1M), hpvmmgmt(1M), hpvmpubapi(3) 106 hpvmhostgdev Manpage
