 |
» |
|
|
|
Changes to I/O Configuration Are Not Displayed in VM Manager | |
When you change your I/O configuration outside VM Manager (such as
adding or removing devices through the command line or other tools), the
updated configuration is not shown until the display is refreshed. The display is automatically refreshed at regular intervals. To refresh the display
manually, click the Refresh Data link. to refresh the I/O
device information, use the Refresh link in the Set
Network and Set Storage screens of the
Create Virtual Machine wizard. Incomplete Network or Storage Information from Virtual Machines | |
Incomplete network or storage information is available from virtual
machines if the VM Provider is not running on all of the started virtual
machines and on the VM Host. Enter the following command on each VM and look for the response
“HPVMProviderModule OK”:
If the information on the VM Manager screens is incomplete, it could be
a result of VM Manager's asynchronous discovery, which does not
wait for every result before drawing a page. If the expected information
is not displayed, click the Refresh Data link.
Slow Response Time on Systems with Many Heavily Active Virtual
Machines | |
The amount of CPU reserved for non-virtual machine processes running on the VM
Host is controlled by two tunable parameters in the
/etc/rc.config.d/hpvmconf file. These parameters
are SVRCPURESPCT and SVRCPUALLOWPCT.
Both parameters are interpreted as percentages of a single CPU and are
initially set to 20. In practice, on a multiprocessor VM Host, the server percentage is
split equally across all processors on the host, with the percentage per
processor rounded up to the nearest whole number. Thus, a 20% value
for a 1-way host reserves 20% of that processor for host processes. On a
2-way host, 10% of each processor is reserved. On a 4-way host, 5% of each
processor is reserved. On an 8-way host, 3% of each processor is reserved
(due to rounding). On a 16-way host, 2% of each processor is reserved
(again, because of rounding). To give more processor resource to management applications running
on the VM Host, increase both of these parameters to the same new value.
After these parameters are changed, stop and restart Integrity VM for
the changes to take effect. Virtual Machines Not Identified Correctly | |
Virtual machines might
not be correctly identified as such if the VM Provider is not running on the virtual
machine or if the VM Host is not included in HP SIM discovery. In either of
these cases, the virtual machines are color-coded the same as standalone servers, and
they have no View: VM link in the System View. However, the
model string still identifies them as HP Integrity Virtual Machines.
To determine if the VM Provider is running on a virtual machine, enter the
following command on the virtual machine and look for the response
“HPVMProviderModule OK”:
If you do not see the expected response, install the VM Provider on the
virtual machine. For installation instructions, see the
VSE Management Software Installation and Update Guide Version A.03.00.00 (“Installing VSE
Agent Software on Managed Systems”).
Include both the VM Host and the individual virtual machines in the HP SIM
discovery list. This enables HP SIM and the VSE Management Software to
properly associate the virtual machine and the VM Host to one another and
enables management using HP Integrity Virtual Machines Manager.
Versions of Integrity Virtual Machines, VMProvider, and VMGuestLib Must Be
Compatible | |
If VMProvider, VMGuestLib, and HP Integrity Virtual Machines are
already installed, upgrades of any of these three products require
upgrades of the others so that all versions are compatible and all
products function correctly. It is generally a good idea to upgrade all three products at the
same time. However: If HP Integrity Virtual Machines is upgraded on the VM Host,
VMProvider and VMGuestLib running on a virtual machine need not be
upgraded; however, if they are not, some features might not be available
in VM Manager. If VMProvider is upgraded on a VM guest, the VMGuestLib
must also be upgraded and vice versa, and neither can be upgraded
to a version higher than that of HP Integrity Virtual Machines
running on the VM Host.
|
Printable version
