From Wiki-UX.info

Wiki-UX / Integrity Virtual Machines / Integrity VM Installation Requirements
Jump to: navigation, search

Integrity VM Installation Requirements

Abstract

This article shows the hosts and guest requirements for running HP Integrity Virtual Machines.

Contents


Hosts

HPVM 3.5

Resource Description
Computer An Integrity server
Operating system HP-UX 11i v2 December 2007 (0712) or later, running on an Integrity server, as well as any appropriate software patches (see the HP Integrity Virtual Machines Release Notes). The license for Integrity VM includes the license for running the HP-UX Foundation Operating Environment on the VM Host system.
Local area network (LAN) card Required for network connection and configuration.
Source installation media An appropriate source for installing software (DVD or network connection).
Disk storage Sufficient physical memory (RAM), including the following:
  • 750 MB + 7.5% of memory beyond the first GB (that is, 7.5% of (total physical memory - 1 GB))
  • Total aggregate memory required for each guest (operating system and application requirements)</br>HP-UX 11i v2 May 2005 requires a minimum of 1 GB of memory, so a guest running HP-UX must be configured with at least that much memory.
  • Additional 7% of aggregate guest memory for overhead for guests less than or equal to 4 GB and between 7% and 7.3% for guests larger than 4 GB.

For example, for a VM Host with 16 GB of memory and two VMs configured with 3 GB of memory each, the memory requirements would be calculated as follows:

  • 1.86 GB for the VM Host (750 MB plus 7.5% of 15 GB)
  • 6.42 GB total guest requirement (107% of 6 GB)
  • Total requirements = 8.28 GB of memory</br>This leaves 7.72 GB of memory for additional guests.
Memory Sufficient physical memory (RAM), including the following:
  • 750 MB + 8.5% of memory beyond the first GB (that is, 8.5% of (total physical memory -1 GB))
  • Total aggregate memory required for each guest (operating system and application requirements) HP-UX 11i v2 May 2005 requires a minimum of 1 GB of memory, so a guest running HP-UX must be configured with at least that much memory.
  • Additional 8% of aggregate guest memory for overhead for guests less than or equal to 4 GB and between 8% and 8.3% for guests larger than 4 GB.

For example, for a VM Host with 16 GB of memory and two VMs configured with 3 GB of memory each, the memory requirements would be calculated as follows:

  • 2 GB for the VM Host (750 MB plus 8.5% of 15 GB)
  • 6.48 GB total guest requirement (108% of 6 GB)
  • Total requirements = 8.48 GB of memory This leaves 7.52 GB of memory for additional guests.
Network configuration A configured and operational network. To allow guests network access, the VM Host must have at least one functioning network interface card (NIC).

HPVM 4.0

Resource Description
Computer An Integrity server
Operating system HP-UX 11i v3 September 2008 or later running on an Integrity server, as well as any appropriate software patches (see the HP Integrity Virtual Machines Release Notes). The license for Integrity VM includes the license for running the HP-UX 11i v3 Base Operating Environment (BOE) on the VM Host system.
Local area network (LAN) card Required for network connection and configuration.
Source installation media An appropriate source for installing software (DVD or network connection).
Disk storage Sufficient disk space for the following:
  • The VM Host operating system
  • The VM Host software (50 MB)
  • Disk space for each guest operating system, including swap space
  • Disk space for the applications running on each guest
  • 4.7 MB for each running guest as the allowance for backing up configuration files
Memory Sufficient physical memory (RAM), including the following:
  • 750 MB + 8.5% of memory beyond the first GB (that is, 8.5% of (total physical memory -1 GB))
  • Total aggregate memory required for each guest (operating system and application requirements) HP-UX 11i v2 May 2005 requires a minimum of 1 GB of memory, so a guest running HP-UX must be configured with at least that much memory.
  • Additional 8% of aggregate guest memory for overhead for guests less than or equal to 4 GB and between 8% and 8.3% for guests larger than 4 GB.

For example, for a VM Host with 16 GB of memory and two VMs configured with 3 GB of memory each, the memory requirements would be calculated as follows:

  • 2 GB for the VM Host (750 MB plus 8.5% of 15 GB)
  • 6.48 GB total guest requirement (108% of 6 GB)
  • Total requirements = 8.48 GB of memory This leaves 7.52 GB of memory for additional guests.
Network configuration A configured and operational network. To allow guests network access, the VM Host must have at least one functioning network interface card (NIC).

Available Memory on the HPVM Host

Determinate the available Virtual Memory available on the HPVM Host. The vmstat, swapinfo, kctune, top, glance command can assist you. This is an example of a system with 98GB of physical memory before tunning.

vmstat

The vmstat output shows that only around 470 MB of virtual memory is available for the HPVM host.

Example:

# vmstat 2 5
         procs           memory                   page                              faults       cpu
    r     b     w      avm    free   re   at    pi   po    fr   de    sr     in     sy    cs  us sy id
    1     4     0  12132397  120591   25   12     0    0     0    0     0   9473  26628  7357   1  5 94
 
    1     4     0  12124042  120519    4    0     1    0     0    0     0  15333   7532 11809   0  3 97
    1     4     0  12124042  120684   37    4     0    0     0    0     0  15518  26073 11936   0  2 97
    1     4     0  12124042  120646   23    2     0    0     0    0     0  15483  33094 12152   2  4 94
    1     4     0  12124042  120670   16    0     0    0     0    0     0  15558  22655 12110   0  7 93

To calculate the ammount of free memory use the following formula: (free * 4) / 1024.

For example, in the example, the ammount of available virtual memory is: (120670 * 4 ) / 1024 = 471.36 MB

  • Note: On a HP-UX 11i v3 HPVM Host, the page memory size changes from 4k to 64k to take advantage of the large memory page feature of this release. use the following formula: (free * 64 ) / 1024.

swapinfo

Confirm that the HPVM host has at least the same ammount of swap space as physical memory assigned. Having less will cap the available virtual memory space available to the HPVM host for it's guest(s).

# swapinfo -tam
             Mb      Mb      Mb   PCT  START/      Mb
TYPE      AVAIL    USED    FREE  USED   LIMIT RESERVE  PRI  NAME
dev        8192       0    8192    0%       0       -    1  /dev/vg00/lvol2
dev       40960       0   40960    0%       0       -    0  /dev/vg00/lvol_swap1
reserve       -   46296  -46296
total     49152   46296    2856   94%       -       0    -

The vmstat commands shows that only 49152 MB (8192 + 40960) virtual address space is assigned to the system. This should be increase to at least 98 GB (100352 MB). For example, adding another logical volume with additional 49152 MB will provided the required swap space.

Create the required LVM logical volume and volume group. Update the entries on the /etc/fstab file to attach the new swap during boot. Check that </tt>swchunk</tt> kernel parameter allows for at least 100 GB (6400 chunks or greater) of swap space.

kctune

There are key kernel parameters that affect the amount of memory available to the HPVM host to the guest(s).

HPVM 3.0 and 3.5 (11i v2)

Parameter Default Value Modified Value
dbc_max_pct 50 1
dbc_min_pct 5 1
maxdsiz_64bit 4294967296 34359738368
swapmem_on 1 0
# kctune -q dbc_max_pct -q dbc_min_pct -q maxdsiz_64bit -q swapmem_on

HPVM 4.0 (11i v3)

Parameter Default Value Modified Value
base_pagesize 4 64
filecache_max 50% 1%
filecache_min 5% 1%
lcpu_attr 0 0
lockable_mem_pct 90% 99%
maxdsiz_64bit 4294967296 34359738368
# kctune -q base_pagesize \
-q filecache_max -q filecache_min \
-q lcpu_attr -q lockable_mem_pct -q maxdsiz_64bit

Example

# kctune -q dbc_max_pct -q dbc_min_pct -q maxdsiz_64bit -q swapmem_on
Tunable              Value  Expression   Changes
dbc_max_pct             50  50           Immed
dbc_min_pct              5  Default      Immed
maxdsiz_64bit  34359738368  34359738368  Immed
swapmem_on               0  0

In the previous example (HPVM 3.5 host), the values of dbc_max_pct and dbc_min_pct need to be adjusted.

Guests

Sumary Table

Reference

Authors

This page was last modified on 20 July 2010, at 04:40. This page has been accessed 2,525 times.