Technical data

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.
For Windows guests, install the WMI Utilization Provider (UtilProvider) software provided
with the HP Integrity Support Pack for Windows. Follow the instructions for installing
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.15 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.3.16 Do Not Install Windows as Alternate Boot on a VM Host System
Guest boot disks might become unbootable if the VM Host is restarted as a Windows system.
2.3.17 Trunking Software
Trunking software such as HP Auto Port Aggregation (APA ) is supported on the VM Host and
not on the guest.
2.3.18 Warning During Startup if HP SIM is Installed
Integrity VM generates a warning during startup if HP SIM is installed, but Integrity VM continues
to start. The HP SIM product consumes memory and CPU resources that would otherwise be
available for running virtual machines. The amount of memory and CPU consumed varies
depending on the specific system configuration. On systems that are already tight on memory
or CPU resources, this might cause virtual machines to fail to start.
2.3.19 Patch PHSS_41543 Must be Installed Prior to Guest Activation
If you do not install patch PHSS_41543 prior to activating a guest when updating your image to
Integrity VM B.04.20.05, the guest might fail to start or exhibit other failure symptoms. The exact
symptoms differ depending on the amount of memory assigned to the guest and the guest
configuration. The symptoms include:
• Messages on guest console, like the following:
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 I/O devices,
with stack trace often containing memory allocation related functions, such as
sysmemreserve() and so on.
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 caused indirectly by Integrity VM V4.2.5 enabling the Integrity VM dynamic
memory feature by default. The default values of ram_dyn_target_start and ram_dyn_max
can default to 2G, which, in the case of a larger memory guest, is not enough memory for the
guest to properly run or even boot. If the guest boot was already attempted before the patch was
26 Installation Notes