One possible reason why you are getting "VMmark2 PowerCLI Service Failed to Start :: Workers Ready : 0" is because some software package is missing on the prime client. We recommend looking back through the client configuration section of the benchmarking guide to make sure all software has been installed and each step has been exactly followed, including that the prime client has been completely updated via windows update.
Also, I note that there is some confusion regarding the role of the prime client vs. client0. The prime client is the physical client from which the VMmark harness is run. In your setup, it is separate from client0, which places load on tile0. The hostname of the prime client should be something like "primeclient" or whatever you wish, but not "client0".
The hostname of each client (in your case, virtualized clients) will be client0, client1 and so on, as opposed to 'virtualclient0'. The hostname of each client must match the names for "CLIENTS=" in VMMARK.CONFIG, and all client IPs and hostnames should be in the hosts file of the prime client.
For each workload VM, the IP and hostname of both the prime client and the VM's client must be in the VM's hosts file. At minimum, the prime client should be able to ping all clients and all workload VMs. Each client should be able to ping the prime client and its tile of workload VMs. Each workload VM should be able to ping the prime client and its client.
There's also a section "Networking Issues" at the end of the VMmark Benchmarking guide to address some network troubleshooting issues.