If you look in the agent.log file for the HQ agent that you are using to connect to your Xen hosts, you may notice a line that contains the following:
"com.xensource.xenapi.Types$BadServerResponse [HOST_IS_SLAVE..."
In order to collect information on hosts in a configured pool, you have to modify the platform's Configuratoin Properties, connecting to the Xen master node's API URL, and specifying the platform.uuid that corresponds to the Xen slave host. This should allow the collection of host metrics to begin for your slave.
A problem has just been identified where the VMs on the slave may not be auto-discovered correctly for the Xen pool slave. If you could attempt this configuration, and report back on your experience, it would be very helpful.
Thanks.