upgraded one node to 3.5.1 and get a warning when vmotioning now about guest cpu compatibility

[infinitiguy]

I'm a slight bit concerned.. my CPU's were compatible under 3.0.1, and now that I have a 3.0.1 and a 3.5.1 host they are no longer compatible? That's scary I attempt to move a machine and I get the following warning. Migration from amer-esx2 to amer-esx1: Migration will cause the virtual machine's configuration to be modified, to preserve the cpu feature requirements for its guest OS.

Amer-esx2 is my 3.0.1 node and Amer-esx1 is my newly upgraded 3.5.1 node.. Esx1 has a 3.2ghz xeon and Esx2 has a 2.8ghz Xeon, but they are from the same family, and like I said earlier... had worked fine over vMotion for months before this upgrade.

Now... I really don't care if the configuration has to change, or anything like that... just as long as it wont destroy the virtual machine/vmdk.. or bring down the machine. I have domain controllers, and websites running on esx2 that I really don't want to have to bring offline.

Any help is appreciated. I read a bunch of other posts about this subject but they don't exactly have to do with my circumstances.

[Troy_Clavell · Accepted solution]

that message is just that, a warning. It will write to the 3.0.x vm's .vmx file, but will not cause any harm. The VM will still be able to run

See KB article

http://kb.vmware.com/kb/1003770

[John_S1]

See thread

[infinitiguy]

yep, both are right I was actually on the phone with vmware when the first reply came back and I let him tell me the same thing.

Thanks all!

[TomHowarth]

Thread moved to the VI: ESX 3.5 forum

Tom Howarth

VMware Communities User Moderator