Can you try to do a host vmotion and see if it gets resolved? If not, can you shut down the VM's and start them again? I have seen this issue before and a shutdown and start resolved it.
Is this the same issue reported in your other discussion? http://communities.vmware.com/thread/437321
Can you try to do a host vmotion and see if it gets resolved? If not, can you shut down the VM's and start them again? I have seen this issue before and a shutdown and start resolved it.