vSphere 6.0 and 6.5 have an interesting bug in the vSphere Web Client: a DirectPath I/O option is enabled by default for a new virtual machine with VMXNET3 network adapter provisioned.
A New Virtual Machine dialogue looks good.
However, when I open the VM settings, surprise surprise, it is quite different.
I have done my research and found the DirectPath I/O option was enabled regardless the VM hardware version (checked all versions starting from 8 to 13). VMware explains this behaviour in a KB # 2145889 with the recommendation to disable this parameter.
Feel free to use this code.
28/11/2016 – Update 1: vSphere Client (C#) and vSphere HTML5 Web Client (Fling) also create VMs with the DirectPath I/O option enabled.
28/11/2016 – Update 2:
The workaround is to use PowerCLI to provision a new VM.
26/04/2017 – Update 3: The solution to this problem has been provided by LucD. I am working on an updated script which automate the process of disabling DirectPath I/O for the VMs.