After much digging into CPUID and vSphere EVC mode, I was able to properly configure the cluster in EVC mode with two of my three hosts.
I am now able to successfully vMotion a Win2k3 VM from westwood to northvale (ESXi host names) and back again, leaving the network and storage as shared.
With the Win2k3 VM not doing any real work, the vMotion takes less than 1 minute. I am going to run some spin type scripts on the VM to see if I can detect any hiccups.
During the vMotion migration wizard, if I select cresskill (my ESXi utility host) I get a CPU incompatibility message. This host has a Pentium D, while the other two have Core 2 CPU's of different flavors.
No comments:
Post a Comment