This issue is resolved in ESXi 6.5 Patch Release ESXi650-201811002, available at Support.broadcom.com
Workaround:
To workaround this issue if you do not want to upgrade, create DRS rules to separate virtual machines to make sure they either run on ESXi 6.0 hosts or ESXi 6.5 hosts in a Cluster with mixed ESXi versions