I know this is an older post, but, I agree. We just experienced the same issue within ESXi 5.0 and took a little while to get solved. Is there any good explanation out that that can explain why vCenter decides to do this AND are there any logs we could have looked at to determine this more quickly rather than playing the "isolation" game?
↧