HP Integrity Virtual Server Manager 6.3 User Guide

are insufficient, missing or unavailable check box is selected on the Create Virtual Machines
wizard Summary page, you can still have Integrity Virtual Server Manager create the VM.
You will have to correct the conditions prior to starting the VM.
• Failure starting a VM or a vPar
The most likely cause for a VM or a vPar failing to start is missing, insufficient, or unavailable
resources. Make sure the required resources are made available. For example:
◦ Not enough memory on the VSP is available for the VM or vPar
Make sure that enough memory is available on the VSP to provide the memory you
allocated for the new VM or vPar (in addition to providing for the existing VMs or vPars).
◦ You specified a device that is already in use by another VM or vPar
You might have specified a network or storage device that is already in use by another
VM or vPar. You need to return to the appropriate Create Wizard page to select a device
that is not in use. To determine what devices are already in use, examine the VSP Network
or VSP Storage tab.
◦ A file specified as a backing device does not exist
You might have incorrectly specified the name or path of a file to be used as a backing
storage device, or you specified a file that does not exist.
◦ The VM is currently migrating online or has migrated to another VSP (and is in a Not
Runnable state).
• Failure to modify the VM CPU entitlement
If you attempt to modify (by selecting Modify→CPU Entitlement for VM) the CPU entitlement
of a VM that is being managed by gWLM, the following error message is displayed, where
virtual-machine-name is the name of the VM:
The processor entitlement for VM virtual-machine-name cannot be
modified because it is being managed by gWLM. To adjust the processor
entitlement for this VM, use gWLM to change the policy associated
with this VM.
To create or modify the gWLM policy for this VM, use the Policy menu (available when using
Integrity Virtual Server Manager with the Matrix Operating Environment for HP-UX).
• Information is out of date, incomplete, or missing
In general, Integrity Virtual Server Manager tabbed view screens are refreshed automatically
every five minutes. An indicator on these visualization pages notifies you when the data was
last refreshed. Integrity Virtual Server Manager screens that display configuration data are
updated instantaneously when you use Integrity Virtual Server Manager to change the related
configuration parameters.
NOTE: When changes to VM or vPar I/O configuration are made using tools other than
Integrity Virtual Server Manager (such as adding or removing I/O devices by using the VSP
command line), the updated configuration data is not shown until the screen is refreshed. You
can manually refresh a tabbed view screen and certain dialog screens (such as those for
adding storage or network devices) by clicking on the Refresh Data link.
If information about certain VMs or vPars is missing from a Integrity Virtual Server Manager
screen (for example, specifics about a port interface), the screen might need refreshing, the
VMs or vPars might not yet be started or, if they are started, the VM Provider or certain WBEM
components might not be running on those VMs or vPars or on the VSP. WBEM components
are required on any VM or vPar for which you want data. If the VM Provider is not running
on the VSP, no data will be available on any Integrity Virtual Server Manager tabs; all tabs
will display a “No data available” message. To verify that the VM Provider is running, enter
the following command on the VM or vPar or VSP:
cimprovider -ls
Troubleshooting VM or vPar problems 143