HP Integrity Virtual Server Manager 6.0 User Guide

• Failure starting a virtual partition
The most likely cause for a virtual partition 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 virtual partition
Make sure that enough memory is available on the VSP to provide the memory you
allocated for the new virtual partition (in addition to providing for the existing virtual
partitions).
◦ You specified a device that is already in use by another virtual partition
You might have specified a network or storage device that is already in use by another
virtual partition. 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 virtual partition is currently migrating online or has migrated to another VSP (and is
in a Not Runnable state).
• Failure to modify the virtual partition CPU entitlement
If you attempt to modify (by selecting Modify→Virtual Partition CPU Entitlement) the CPU
entitlement of a virtual partition that is being managed by gWLM, the following error message
is displayed, where virtual-partition-name is the name of the virtual partition:
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 virtual partition, use the Policy menu (available
when using Virtual Server Manager with the Matrix Operating Environment for HP-UX).
• Information is out of date, incomplete, or missing
In general, 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. Virtual Server Manager screens that display configuration data are updated
instantaneously when you use Virtual Server Manager to change the related configuration
parameters.
NOTE: When changes to virtual partition I/O configuration are made using tools other than
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 virtual partitions is missing from a Virtual Server Manager screen
(for example, specifics about a port interface), the screen might need refreshing, the virtual
partitions might not yet be started or, if they are started, the VM Provider or certain WBEM
components might not be running on those virtual partitions or on the VSP. WBEM components
are required on any virtual partition for which you want data. If the VM Provider is not running
on the VSP, no data will be available on any 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 virtual partition or VSP
cimprovider -ls
The response “HPVMProviderModule OK” indicates the VM Provider is running. Any other
response indicates it is not running. For system and software requirements regarding the VM
Provider, see “System and software requirements” (page 11). For installation instructions and
Troubleshooting virtual partition problems 129