I have nothing to offer other than I believe I saw some other post expressing the same issue with the 5.1.2 agent. If I remember correctly they ened up just going back to the older 5.1.1 agent to solve their issue.
Have you submitted a ticket to VMware? That is the best course of action so the problem can be documented and hopefully they have an eta on a potential fix.