VMware Cloud Community
thro
Enthusiast
Enthusiast
Jump to solution

esx 4.0 vmotion broken (on some VMs, not all) - not sure when/why

Hi all,

For a while now I've been getting the following error when trying to vmotion several of my VMs:

"Host CPU is incompatible with the virtual machine's requirements at CPUID level 0x1 register 'ecx'.

Host bits: 0000:0000:0000:1000:0010:0000:0001

Required: 1000:0000:0000:100x:xxx0:0x1x:xxx0:x001

Mismatch detected for these features:

*general incompatibilities; refer to KB article 1993 for possible solutions."

Now, the thing is... all of my hosts are identical in terms of CPU. They've been happily running vmotion for the past year and a half under ESX 3.5, and these same hosts can vmotion other VMs. These same VMs have been vmotioned in the past. I'm certain they have also vmotioned in the past on ESX4 as well (to do updates via update manager after the 4.0 upgrade).

Vmware tools are up-to-date.

Any idea what gives?






I use/administer: vSphere 4 (ESX) | Workstation 6.5 | Vmware Server 2.0 | Windows 2003 | FreeBSD | Redhat EL

I use/administer: vSphere 6.0 (ESXi) | Workstation 12.5 | Vmware Server 2.0 | Vmware Fusion 12.5 | Windows | FreeBSD | Redhat EL
Tags (2)
0 Kudos
1 Solution

Accepted Solutions
krowczynski
Virtuoso
Virtuoso
Jump to solution

0 Kudos
2 Replies
krowczynski
Virtuoso
Virtuoso
Jump to solution

Hi,

check this out if it can help you.

http://kb.vmware.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=1011294&sl... 0 50459451






MCP, VCP

MCP, VCP3 , VCP4
0 Kudos
thro
Enthusiast
Enthusiast
Jump to solution

Legend... got it in one.

Cheers Smiley Happy






I use/administer: vSphere 4 (ESX) | Workstation 6.5 | Vmware Server 2.0 | Windows 2003 | FreeBSD | Redhat EL

I use/administer: vSphere 6.0 (ESXi) | Workstation 12.5 | Vmware Server 2.0 | Vmware Fusion 12.5 | Windows | FreeBSD | Redhat EL
0 Kudos