It is a bug, but it's fixed in the latest 6.5 release (VMware-VMvisor-Installer-201704001-5310538.x86_64)
