First of all, for Iometer tests and trace replayer tests, worker VMs MUST be I/O Analyzer appliance VMs as well since I/O Analyzer appliance comes with our customized workload generator. If all of your controller VMs and worker VMs are I/O Analyzer appliance VMs, please see answers above (quoted below for your reference).
If guest-level stats are missing, that means Iometer didn't start at all. Please make sure your controller VM can ssh to all worker VMs (including the controller itself). Please login to NGC or vSphere client console during Iometer tests and make sure an Iometer window is popped up and showing progress.
If you're running trace replayer and you cannot see host-level VM stats, mostly likely it's also due to network problem. Please make sure your controller VM can ssh to all worker VMs (including the controller itself). For troubleshooting network issues, running Iometer might be more appropriate as you can see Iometer progress from NGC/vSphere client console.
If you're running in listening mode, please make sure your VM is doing some work to the desired target disk.
Note that for trace replay and listening mode, there will be NO guest-level stats. Only host-level stats will be collected, which will contain VM stats.
If the problem persists, please send your /var/www/ioa.log and /var/log/daemon.log to io-analyzer-info@vmware.com.
Thanks,
Chien-Chia