| United States-English |
|
|
|
![]() |
HP Integrity Virtual Machines: Release Notes > Chapter 3 RestrictionsInstalling Integrity VM |
|
This section lists the release notes related to installing the HP Integrity Virtual Machines product and associated software on the VM Host system. The HP-UX Foundation Operating Environment (FOE) is included with Integrity VM. Install the FOE on the VM Host on which you install Integrity VM. The license for the FOE (used in the VM Host only) is included with the purchase of Integrity VM. (Licenses for OEs that run inside the individual virtual machines must be purchased separately.) For VM Hosts that will support guests as Serviceguard packages, the Mission Critical Operating Environment (MCOE) can also be used. Table 3-1 lists the patches that are required in the VM Host system: Table 3-1 VM Host Patches
Table 3-2 lists the patches that are required in the guests: Table 3-2 Guest Patches
For more information about updates to HP-UX software, contact your HP representative or support specialist. Regardless of whether guests are running or not, runing applications other than Integrity VM on the VM Host system is not supported. System management utilities and Serviceguard are supported as documented in the HP Integrity VM Installation, Configuration, and Administration manual. The installation of Integrity VM changes HP-UX kernel settings that make the environment unsuitable for running other applications. Other applications should be run inside virtual machines. The version of HP WBEM Services for HP-UX must be A.02.00.10 or later. Integrity VM fails to install if the version of WBEM Services on your VM Host is older than A.02.00.10. The HP WBEM Services for HP-UX software bundle (B8465BA) is available as part of HP-UX 11i V2 0606 (June 2006) and later. For VM Hosts running earlier versions of HP-UX, download the latest version of WBEM Services from www.hp.com. If existing guests have the start_attr attribute set to auto, they start when you install or update Integrity VM. The Windows installation process changes the GUIDs (guest user identifiers) associated with all visible boot partitions. If the VM Host is restarted as a Windows system, the information about visible guest boot devices is affected. Guest data is not lost, but EFI boot menu items for guests become invalid. HP does not support running Integrity VM in a vPar. If you override the Integrity VM installation warnings and force it, you receive errors during the start of Integrity VM. Install products that provide multipath failover (such as Secure Path) on the VM Host system, not on the guests. VM Host devices configured with multipath failover can be used as guest backing storage devices. For a list of supported devices, and for information about running multiple multipath solutions on the same VM Host, refer to the product documentation for your specific multipath solution. For optimal performance with storage intensive applications such as Oracle®, HP strongly recommends using whole disk backing stores. Virtual disks that use logical volumes or files as backing storage do not provide optimal performance for this type of application. For more information about the Integrity VM storage subsystem, see the HP Integrity Virtual Machines Installation, Configuration, and Administration manual. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||