HP Matrix Operating Environment Software - Manual (Page 107)

8 Troubleshooting
This chapter covers some of the issues that can occur when you are using logical servers, and
provides the troubleshooting steps you need to correct the problem, and provides some tips that
will help you better use the Virtualization Manager.
Importing a Microsoft Hyper-V virtual machine with configuration file in
default location is not supported
A Hyper-V virtual machine whose configuration file is in the default location on the hard disk in
\ProgramData\Microsoft\Windows\Hyper-V
is not supported by logical server management.
You cannot import a virtual machine guest as a logical server if the virtual machine's configuration
file is in this location. There is a limitation in Microsoft Hyper-V that allows HP Insight Control virtual
machine management to re-register the virtual machine if the configuration file is created in this
directory. To prevent issues with reactivation, logical server management checks the path and
rejects any virtual machines with a configuration file in the default location.
Recovery after logical server operation failures
After performing a logical server operation such as a deactivation, you may see the following error
message on the Report Logical Server Job Status screen:
Internal error occurred. This logical server might be in an
inconsistent state. HP strongly recommends that you unmanage
logical server {logical server name} and verify the status
of {resource name: profile or VM}.
Possible causes are:
•
Environment configuration problems.
•
The resource became unavailable during the runtime of the logical server operation.
•
The resource has been changed outside of logical server management. For example, the virtual
machine was deleted or the server blade profile was changed.
Suggested actions
1. Ensure that the following configurations are set correctly in your environment. Failure to do
so can cause various errors.
•
DNS is configured for all managed servers
•
Time synchronization has been performed among the CMS, managed systems (including
ESX hosts), and VMware vCenter
•
VMware vCenter credentials and URL settings in Systems Insight Manager are correct
•
VMware vCenter is discovered in Systems Insight Manager
•
Onboard Administrator credentials and URL settings in Systems Insight Manager are
correct
Importing a Microsoft Hyper-V virtual machine with configuration file in default location is not supported 107