This really a good discussion.
I just figured out few things with this KB and with CPU scheduler with vmware document..
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1010184
As per CPU proccessing with VMware.
1vCPU is mapped to 1 physical core ( not to physical cpu (socket)).
lets come to our discussion what happen when you increase the cores for virtual machine for example you have 1vCPU socket and increased the cores to 2. ESXi still see it as 2 individual vCPU and its mapped to 2 physical CPU cores.Virtual machine see it a 1CPU with 2 cores(i.e is dual core). refer below screen shot with 1 virtual CPU socket and changing the core to 2 and finally it shows as 2vCPU's in summary tab.
So from ESX side the vCPU scheduling doesnt make difference if there is 2 individual vCPU socket or 1 vCPU socket with 2 vCore.. esxi see's it as 2vCPU and does the scheduling.. vmkernel does the scheduling in a much better way to give the good performance to the virtual machine.
Hope this clarifies..
Award points by clicking the below tab if the answer is helpful or correct :smileyhappy: