Sunday, March 27, 2011

"VMkernel not configured" in iSCSI adapter

Login to Vmware Host >configuration>add networking>add VMKernel>give it an IP Subnet, mask and gateway..Make sure the ip is different than service console. It should work now.

Wednesday, March 23, 2011

VMotion migration warning: The VMotion interface of the destination host uses network, which differs from the network used by the VMotion interface of

Symptoms


  • Unable to migrate from to : Currently connected network interface '' uses network '', which is configured for different offload or security policies on the destination host than on the source host .
When performing a VMotion migration the following compatibility warning is displayed:

Resolution

This issue occurs when the Network Label of the VMkernel portgroup used for VMotion differs between ESX hosts.
This warning can be safely ignored as long as the VMkernel portgroups used for VMotion are connected to the correct physical network.
Note: The compatibility check only verifies that the network names of the portgroups to ensure that the network is the same, it does not check connectivity.
To eliminate the warning completely:
  1. Edit the settings of the virtual switches on ESX hosts that have the VMkernel portgroup configured.
  2. Change the Network Label to be same (including case sensitivity) across ESX hosts involved in the VMotion.

When deploying a template using Guest Customization, Windows operating systems fail


Symptoms

  • When deploying a template using Guest Customization, the Windows 7, Windows Server 2008, or Windows Vista based operating systems fail
  • When the virtual machine boots into Windows, you see the error:

    The computer restarted unexpectedly or encountered an unexpected error. Windows installation cannot proceed. To install Windows, click OK to restart the computer, and then restart the installation.
  • In the setupact.log file located at %SystemRoot% xxxx, you see this error multiple times:
Resolution
This issue may occur if an invalid Product Key is entered during the Guest Customization of the template when deploying the virtual machine.

Monday, March 21, 2011

VMware vmotion fails with CPU of host incompatible

Unable to migrate from to : The CPU of the host is incompatible with the CPU feature requirements of the virtual machine; problem detected at CPUID level.

or

Host CPU is incompatible with the virtual machine's requirements at cupid level 0x1 register'ecx'
Host bits: 0000:0100:0000:1000:0010:0010:0000:0001
Required: 1000:0100:0000:100x:xxx0:0x1x:xxx0:x001
Mismatch detected for these features:
*General incompatibilities; refer to KB article 1993 for possible solutions.


Try this:
  1. Power down the virtual machine.
  2. Click the link to Edit Settings of the virtual machine.
  3. Click the Options tab.
  4. Select CPUID Mask under Advanced.
  5. Click Advanced.
  6. Click Reset All to Default.
  7. Click OK.
  8. Click OK again.
  9. Power on the virtual machine and migrate.