I just had the same problem. I had enabled SMP FT, and then I had odd issues with VMXNET3 and UDP RSS (I believe) and this locked up a lot of stuff, caused all kinds of issues and somehow even after disabling SMP FT, it was not really disabled. It was a mess.
What I did was I unregistered the VM, edited the VMX file and commented out the following lines and re-registered the VM:
#ftcpt.enabled = "TRUE"
#ftcpt.newMetadataDir = "true"
#ft.metadataFile = "/vmfs/volumes/5e1a720e-88519630-dc80-4cd98f9ed01f/VPN-1/shared.vmft"
#ft.lockFile = "/vmfs/volumes/5e1a720e-88519630-dc80-4cd98f9ed01f/VPN-1/.ft-generation"
I believe the only thing needed to be disabled is the first line, as I missed that one in the first pass and still had that error. After commenting out that line it boot just fine. I would suggest disabling your FT, cleaning up manually (on the other datastore) and re-enabling it again. I have no plans to do that here until I work out the NIC issue first. My experience, it's a hardware firmware issue.