I have realized there are issues such as virtual machines being exposed to other VMs within the same system when they're connected to the VMCI socket interface. How do we prevent this ?
ESX/ESXi 4.0 to ESXi 5.0 provide .vmx options for VMCI isolation. As of ESXi 5.1, these options have no effect.
[vmci0.unrestricted = FALSE|TRUE]
When its vmci.unrestricted option was set TRUE, a virtual machine could communicate with all host endpoints and other virtual machines that had vmci0.unrestricted set TRUE.
[vmci0.domain = ]
(ESX/ESXi only) All virtual machines and host applications were members of the default domain ("") null string, by default. If the vmci0.domain option specified a non-default domain, then the virtual machine could communicate only with the hypervisor and other virtual machines in the same domain. This was to organize virtual machines into groups that could communicate with each other.
As of ESXi 5.1, or earlier when configured for restricted communication, the VMCI device has a security profile similar to any other device such as keyboard, video monitor, mouse, or motherboard. Guest communications depend on the VMCI applications running on the host. VMCI in itself does not expose any guest information.