Print | Rate this content

CUSTOMER ADVISORY: HP Integrity Virtual Machines (HPVM) B.04.20.05: dynamic memory issues encountered during installation/upgrade

SUPPORT COMMUNICATION - CUSTOMER ADVISORY

Document ID: c02692588

Version: 1

CUSTOMER ADVISORY: HP Integrity Virtual Machines (HPVM) B.04.20.05: dynamic memory issues encountered during installation/upgrade
NOTICE: The information in this document, including products and software versions, is current as of the Release Date. This document is subject to change without notice.

Release Date: 2011-01-21

Last Updated: 2011-01-21


DESCRIPTION

Customers may see issues revolving around the dynamic memory feature enabled in HP Integrity VM B.04.20.05 when upgrading their installation to this version. There has been a pattern of customers not fully reading the Release notes and Installation guides and following the instructions to load co-requisite patches listed in the supporting documentation.

These issues can be avoided by following the instructions in the HPVM release documentation to install the required patches with this release.

Failure to install the required patches on the host HPVM machines prior to booting a guest image may result in the following problems:
  • Guest failing to boot with the following message (or similar) on the guest console:

    hpvmdynmem: unable to reach target memory size of 2105 MB after 60 seconds, resulting memory size is xxxx MB.

  • guest panics at boot time due to memory shortage typically when initializing IO devices, with stack trace often containing memory allocation related functions like sysmemreserve().

    Another example is panic under gvsd_attach_cleanup() with the following panic string: "Not all objects de-allocated"

  • guest hangs at boot time typically at the start of rc scripts.

The problem is indirectly caused by HP Integrity VM B.04.20.05 enabling the dynamic memory feature by default. The default values of ram_dyn_target_start and ram_dyn_max can default to 2GB which, in the case of a guest with large memory requirements, will not be enough memory for the guest to properly run or even boot.

SCOPE

This issue may affect users upgrading current installations of HPVM to HPVM B.04.20.05. It is seen with guest configurations that have large memory configurations.

RESOLUTION

Administrators should install all required patches listed in the HPVM Release Notes and the Administration guide documents before attempting to start up the system guests after installing HPVM B.04.20.05.

The Release notes can be found:
  1. Connect to the Hewlett-Packard Manual page for HP Integrity Virtual Machines and Online VM Migration at:

    http://www.hp.com/go/hpux-hpvm-docs

  2. Select your Manual Language and under “Getting started” look for “HP Integrity Virtual Machines 4.2.5: Release Notes”.

Customers are instructed to review section “1 Introduction” and the patches listed in this section. The patches include:
  • PHSS_41543 1.0 HPVM B.04.20.05 CORE (HPVM host) (or superceding)

  • PHSS_41550 1.0 HPVM B.04.20.05 HPVM –VMSGTK (HPVM host) (or superceding)

  • Logical Volume Manager (LVM) software (LVM B.11.31.1010 on HPVM host) (or superceding)

NOTE: If the guest boot was already attempted before the patch was installed, installing the patch by itself will not prevent the problem and reconfiguration of the dynamic memory settings is necessary for the guest to be able to boot again.

As a workaround HPVM dynamic memory can be disabled for the guest by

# hpvmmodify -P ${guest_name} -x ram_dyn_type=none

The manageability features for HP-UX guests brought by enabling HPVM dynamic memory can safely be re-enabled for the guest once the correct patch is installed by

# hpvmmodify -P ${guest_name} -x ram_dyn_type=any

If ram_dyn_target_start and ram_dyn_max have already been set, then you need to change their values to the desired range dependent on the configured memory size.

It's recommended that ram_dyn_target_start (and ram_dyn_min) should not fall below 25% (or 1GB whichever is higher) of memory configured for the guest. ram_dyn_max should be set to the memory configured.


Hardware Platforms Affected: HP Integrity Virtual Machines Manager (vmmgr) Software(Standard HP Product)
Components Affected: Not Applicable
Operating Systems Affected: HP-UX 11i v3
Software Affected: Not Applicable
Third Party Products Affected: Not Applicable
Support Communication Cross Reference ID: IA02692588
©Copyright 2011 Hewlett-Packard Development Company, L.P.
Hewlett-Packard Company shall not be liable for technical or editorial errors or omissions contained herein. The information provided is provided "as is" without warranty of any kind. To the extent permitted by law, neither HP or its affiliates, subcontractors or suppliers will be liable for incidental,special or consequential damages including downtime cost; lost profits;damages relating to the procurement of substitute products or services; or damages for loss of data, or software restoration. The information in this document is subject to change without notice. Hewlett-Packard Company and the names of Hewlett-Packard products referenced herein are trademarks of Hewlett-Packard Company in the United States and other countries. Other product and company names mentioned herein may be trademarks of their respective owners.

Provide feedback

Please rate the information on this page to help us improve our content. Thank you!