This fixed it for me.. that host was upgraded with a new motherboard and had just moved the VMs back in this week the day after I had that message. just saying what happened before i got the message.
