ESX 3.5 Build 130756

[niljersweden]

Hi!

I have just done an update on one of our hosts in our test cluster in ESX and i can not migrate vm's to this host (130756) after upgrade?

Upgraded host build 130756

The other host build 123630

Exactly the same hardware.

Here is some information

Someone else with this problem?

Thanks

Jerry

Dec 4 14:47:01 vmhost6 vmkernel: 27:03:32:37.706 cpu2:1197)WARNING: MigrateNet: 398: 1228398388092832: Connect to <xxx.xxx.xxx.xxx>:8000 failed: I/O error

Dec 4 14:47:01 vmhost6 vmkernel: 27:03:32:37.706 cpu2:1197)WARNING: Migrate: 1243: 1228398388092832: Failed: I/O error (0xbad000a) @0x9e3d5f

Dec 4 14:47:01 vmhost6 vmkernel: 27:03:32:37.707 cpu3:1184)WARNING: Migrate: 7054: No migration found for vmm leader 1184.

[bradley4681]

I'm having this exact same problem and i'm recieving the same error messages in the logs. I can ping both nodes in the cluster and i can also vmkping both nodes but nothing will migrate. I tried turning off the firewall for testing and still nothing.

Cheers,

Bradley Sessions

If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".

[chill]

Have you tried disabling the vSwitch for VMotion? Sometimes during an upgrade/maintenance, the vSwitch or Vmkernel connection for VMotion goes into a "state of shock" and is not sure what to do. Disable, then enable. I've even gone as far as removing it and creating a new one. This has always resolved the issue for me.

If you find this information helpful or correct, please consider awarding points.

[bradley4681]

Yeah I ened up having to remove the vmkernel port group twice from one host and 3 times from another before they all worked properly.

Cheers,

Bradley Sessions

If you found this or other information useful, please consider awarding points for "Correct" or "Helpful".

[kinchit]

Yes it work once you disable the vmotion and then enable it