In my particular case, I had not re-added the connection to the SAN in which our VMs are stored. vMotion was configured and the single host was not available in any list. I stumbled across this question searching for answers. I thought I'd add my situation if it helps anyone else having the same problem. I skipped a step in reconfiguring the new host. Once I added the access to the SAN again, the host showed up and all was fine for vMotion events. Hope this helps someone out there. Thanks for all the input.