Generally, the xendConfig job configures each SUSE Xen VM host (that is, it modifies /etc/xen/xend-config.sxp). The configuration includes but is not limited to the following functions:
VNC console sessions to a VM ('vnc-listen', 'vnc-passwd')
VM migration between Xen VM hosts ('xend-relocation-server' 'xend-relocation-address', 'xend-relocation-port', 'xend-relocation-hosts-allow').
Currently, when the Orchestration Agent is running in a clustered environment (that is, it is active on only one host in the cluster at a time), it is not possible to use the xendConfig job to configure all of the VM hosts contained within the Xen cluster using the xendConfig job because the agent does not have access to all hosts.
If the xendConfig job detects that it is running on a clustered VM host, the following message (or similar) is displayed:
WARNING: cluster-xenha2_xen is a member of a XEN cluster. Xend should be manually configured on this host. Skipping..
To work around this issue, manually configure the /etc/xen/xend-config.sxp file on every cluster node as appropriate, then restart the xen service (rcxend restart).