In my environment am running ESX v4.0 U1, and migrating several VMs (vMotion) to new datastores, we ran into an error with a couple of systems: ” Solution was so straight-forward it was pitiful. Snapshot the problem system, then delete the just created snapshot, the vMotion proceeded as expected.
