VMOTION

[epj]

Ok To make a long story longer I have read the knowledge base article at least 3 or 4 times about the CPUID Mask etc. I'm still confused (but that's normal for this old fart)

Any way I have a Dell 6650 in my VI3 farm of Dell 6850's and I just want to be able to migrate between it and the 6850's (hot migrate not cold(which works))

The issue is shown in this line:" Unable to migrate from 10.1.1.1 to 10.1.1.2:The CPU of the host is incompatible with the CPU feature requirements of virtual machine; Problem detected at CPUID level 0x80000001 register 'edx'"

So I was attempting to go to the advance settings on the VM and try to set the mask to over ride this issue, but I just don't have any idea how to correctly do this.

In my old ESX 2.5x farm under VCC1.x these 2 hosts played fine after setting the global config to ignore the CPU differences and I had no issues at all in migration.

I just want to duplicate this same thing in my VI3 farm, otherwise my 6650 is useless in my VI3 farm.

So question is can this be accomplished with the advance tab? under the VM, and if so how exactly?

Can some kind soul give me a mask string that would go in the advanced tab fields that will make this go away for that error?

Thanks as always for any input.

[peetz]

Hello epj,

to help you we really need the exact vendor/type of the CPUs you are using in source and target hosts.

In the meantime carefully look at the VMware KB-articles

KB1991[/url]

KB1992[/url]

KB1993[/url]

\- Andreas

[epj]

ok here is the Dell 6650 CPU info per ESXVI3 Screen

Intel(R) Xeon(TM) MP CPU 3.00GHz quad processor

the Dell 6850's are all

Intel(R) Xeon(TM) MP CPU 3.16GHZ quad Processors

This is a reported directly from VI3 VCC

Thanks

[peetz]

Referencing KB1991 and looking at the Dell Specs for the 6650 and 6850 you will find that the 6650 is in VMotion Group A, and the 6850 is in VMotion Group C.

There it looks like VMotion (A<->C) is not supported, and the Dell VMotion Compatibility matrix (at. http://www.dell.com/downloads/global/solutions/vmotion_compatiblity_matix.pdf) also shows them as being incompatible.

However, I would give a try with combining the SSE3 and the NX mask. Look at KB1993 and follow the instructions there for "modifying default NX/DX mask" and modifying the default mask for SSE3.

You probably need to power-cycle a VM after you changed the masks on it to have the changes take effect.

After that, try VMotion again. If it doesn't work you are probably doomed...

\- Andreas

[epj]

Ok,

This vmotion thing is driving me crazy. So far as I can tell you guys are bascially telling me that I can't get there from here!

But what I don't understand I guess is that under 2.5x and VC 1.x I could migrate all day long with no issues once I edited the cfg file and told VC1.x to ignor.

Can I not get simular functionality under VI3? by applying the masks to the VM?

I have read the articles and such but still not sure about the masks and how I would set those correctly. So far I have tried some of the examples in the articles but to no avail. the migration error never changes.

So having said this, has any one used masking to make vmotion work correctly and if so have some examples of what you used it and where in the advance area did you apply it.

Sorry for being so blind here but sometimes I have to beat the information in till I see it clearly

thanks