HP Integrity Virtual Machines 4.2: Installation, Configuration, and Administration

The asynchronous event generation occurs in addition to any notifications issued using the SCSI
programming model, such as CHECK CONDITION on a subsequent I/O.
When the AVIO storage driver on the guest detects the events, it takes the appropriate actions,
such as discovering the new targets. For example, if new targets are added using the hpvmmodify
-a command, then the guest driver automatically detects the new device without the manual
scan. The guest automatically detects any modification of the underlying backing storage.
Changing the underlying backing storage of a guest is best done when the guest is not running
to avoid damage to the guest. If the change is to a running guest, the administrator is responsible
for knowing that the change will not adversely affect the health of the running guest. Although
Integrity VM does check to determine if the device is in use by the guest, those checks are not
100% reliable, because the guest might or might not be using the device at the time it is checked.
Guest backing storage can be adversely affected if the actual storage or access path is modified
directly by an HP-UX server command, for example, by removing a file backing store or
unmounting the file system. If the devices being changed are a result of some SAN reconfiguration,
the ioscan command should be run on the Integrity VM server before attempting the change
with the hpvmmodify command. If the backing storage is changed by remapping a different
wwid to an existing dsf using: scsimgr replace_wwid -D dsf, the hpvmdevmgmt -I
command needs to be run. If the backing storage is SAN presented as a different device and the
change is done using: io_redirect_dsf -d old_dsf -n new_dsf, the guest must be
modified using the hpvmmodify command to reference the new disk in place of the old disk.
1.5 Running Applications in the Integrity VM Environment
The VM Host system runs the Integrity VM software, which is responsible for allocating processor
and memory resources to the running guests. The VM Host system can run physical resource,
performance, and software management and monitoring tools. To allow the VM Host to allocate
resources to the virtual machines, do not run end-user applications, such as database software,
on the VM Host system. Instead, run them on virtual machines.
Typical software you can run on the VM Host system includes the following:
• HP-UX 11i v3 Virtual Server Operating Environment (VSE-OE)
NOTE: Integrity VM Version 4.2 is included in the HP-UX VSE-OE, as well as the in the
HP-UX DC-OE. You can install Integrity VM from the OE and run it on the VM Host system.
For HP-UX guests, you must purchase separate HP-UX 11i v3 licenses.
For information about the software that is required on the VM Host system, see Chapter 2
(page 27).
• Software installation tools (Ignite-UX and Software Distributor-UX)
• Hardware diagnostic and support tools to monitor guests (WBEM, online diagnostics, Instant
Support Enterprise Edition [ISEE])
• System performance monitoring tools (GlancePlus, Measureware, OpenView Operations
Agent)
• Utility pricing tools (Instant Capacity, Pay per use)
• Hardware management tools (nPartition Manager, storage and network management tools)
• Multipath storage solutions
• HP Serviceguard can be run on the VM Host system or on HP-UX guests.
Do not run applications on the VM Host system, such as Oracle, Workload Manager (WLM), HP
SIM, and so forth. Integrity VM installation modifies kernel parameters, making the system
unsuitable for running applications. Regardless of whether guests are running or not, do not run
applications on the VM Host system.
1.5 Running Applications in the Integrity VM Environment 21