Apologies for the delay. It sounds like this problem is due to an unsupported virtualized environment. If we were somehow able to recreate the issue in a supported (native) environment, then we could likely find a solution. Unfortunately, there's not much that we can troubleshoot here.
Did you happen to reach out to VMware to see if they have any recommendations?
If this post answers your question or solves your issue, please click Accept as Solution so others in the community can find it easily.
Chris Preece
Technical Support Specialist