ESXi

Hi Guys,

I have two servers HP DL 380 G5 and HP DL 380 G6 configured shared storage and etc also enabled vmotion but when I try to vmotion a VM from one host to another host i get the below error how can I resolve this.

Thanks in Advance.

The two server have CPU that have different features - you will either need to manually set the CPU masking for the VM or if the two host are part of a DRS cluster enable EVC so that vCenter will automatically do the masking for you - 

Hi Wienstein,

Thanks for your reponse yes they are part of DRS Cluster I have already tried enable EVC but when i try to enable it in my cluster it says my hosts have incompatable hardware. any other ideas ?

Check this kb.. http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003212

are you selecting correct base line

Hi,

Did you check BIOS settings??

VT and no execute bit is enabled

Could you pl. post the output if your problem is fixed.

Thanks

SA

I have checked one of the host Dl  380 G5 VT and no execute bit is enabled but the other host is running live vms on it so ill check it out this weekend and let you guys know how I go.

We had a similiar issue on our infrastructure a while back. Rather than taking the steps to mask the bits on the CPU's it was easier for us to power down the virtual infrastructure out of hours, enable EVC at the correct level then power the machines back on to bring them all within the same feature set. This resolved it for us.

But my vcenter is virtual so i can turn off everything except vcenter :smileysad:  any other ideas ??

Move all the VMs to one host.  Create a new cluster and move the host with no VMs to it.  Shutdown your vCenter host, then connect directly to the hosts with the vSphere client.  Unregister the VM on the host where it was running, and then register it on the host that was put in the new cluster.  Once you bring it online you can use it to migrate the remaining VMs to the other host and the finally the 2nd host to the new cluster.

Hi Dave,

what do you mean by "Shutdown your vCenter host, then connect directly to the hosts with the vSphere client" if shutdown the host i wont able to login to my host via Vsphere client ??

Hi,

Pl. check the below link to ensure and determine Intel VT is enabled in the BIOS without rebooting..

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003944

http://kb.vmware.com/selfservice/documentLinkInt.do?micrositeID=&popup=true&languageId=&externalID=1011712

Thanks

SA

Hi Sa,

Thanks for your post I run the # esxcfg-info|grep "HV Support" command on both hosts and got the below output.

And according to link u provided 3 Means  VT/AMD-V indicates that VT or AMD-V is enabled in the BIOS and can be used.

any other suggestions ?

Cheers

Ed

Hi,

Output seems to fine. sorry but did you try this document..

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1013111

Could pl. update your post if this document helps.

Thanks

SA

Another way to check VT status is to locate a VM, with Windows 2008 for example and look into the vmware.log file in the VM folder.

Check for lines including the line MONITOR and paste the result.

2012-05-11T05:41:13.719Z| vmx| hostCpuFeatures = 0x4c6001fd
2012-05-11T05:41:13.719Z| vmx| hostNumPerfCounters = 4
2012-05-11T05:41:13.719Z| vmx| MONITOR MODE: allowed modes          : BT32 HV HWMMU
2012-05-11T05:41:13.719Z| vmx| MONITOR MODE: user requested modes   : BT32 HV HWMMU
2012-05-11T05:41:13.719Z| vmx| MONITOR MODE: guestOS preferred modes: HWMMU HV BT32
2012-05-11T05:41:13.719Z| vmx| MONITOR MODE: filtered list          : HWMMU HV BT32

Also guys i checked both of my hosts VT is enbaled see the screen shots below.

Edi47 wrote:

Also guys i checked both of my hosts VT is enbaled see the screen shots below.

Did you also check the option called Intel Virtualization Technology? There was no screenshot on that.

Hi Richard,

isnt intel VT -D "Intel Virtualization Technology" ?

Edi47 wrote:

Hi Richard,

isnt intel VT -D "Intel Virtualization Technology" ?

Kind of, but it is more a special technology to give hardware devices to VMs. The Intel-VT is the original CPU virtualization that enables the hypervisor to offload some software operations to the hardware.

Hi Guys,

Vmotion is working now thanks to Dave's post that did the trick.

Regards

Ed

Great !. Finally it worked. Thanks to Dave and good point to notedown while troubleshooting these type of problems.

Thanks for the update

SA