The XenMemCpu test reports the real-time CPU utilization statistics pertaining to the control domain and every processor supported by the XenServer. The control domain is a privileged VM that provides low-level services to other VMs, such as providing access to physical devices. It also runs the management tool stack. Using this test, administrators can determine whether there is a resource-contention at the XenServer host, and if so, where - at the control domain? or with the processors supported by the host?

This page depicts the default parameters that need to be configured for the XenMemCpuTest.

• The TEST PERIOD list box helps the user to decide how often this test needs to be executed. 

• To enable the eG agent to connect to the XenServer API for collecting statistics of interest, this test should login to the XenServer as a valid user. Provide the name of such a user in the XEN POOL USER text box. By default, the root user is authorized to execute the test. If for some reason you prefer not to use the root user's credentials, you can create a new user on the XenServer host for this purpose.

  The steps for creating a new user on the XenServer host are detailed below:

  1. Login to the host on which the XenServer is installed, as the root user.
  2. From the /usr/sbin directory, execute the following commands to create a new user and assign a password to him/her:

  useradd {UserName}

  passwd {Password}

  3. The following messages then appear:

     Changing password for user

     New UNIX password:

     BAD PASSWORD: it is based on a dictionary word

  4. You will then be prompted to retype the password:

     Retype new UNIX password::{password}

  5. Confirm the password by retyping it in the space provided.

• The password of the specified XEN POOL USER needs to be mentioned in the XEN POOL PASSWORD text box.

• Confirm the XEN POOL PASSWORD by retyping it in the CONFIRM PASSWORD text box.

• By default, the Xen Server is not SSL-enabled. This indicates that by default, the eG agent communicates with the XenServer using HTTP. Accordingly, the SSL flag is set to No by default. If you configure the XenServer to use SSL, then make sure that the SSL flag is set to Yes, so that the eG agent communicates with the XenServer using HTTPS. Note that a default SSL certificate comes bundled with every XenServer installation. If you want the eG agent to use this default certificate for communicating with an SSL-enabled XenServer, then no additional configuration is required. However, if you do not want to use the default certificate, then you can generate a self-signed certificate for use by the XenServer. In such a case, you need to explicitly follow the broad steps given below to enable the eG agent to communicate with the XenServer via HTTPS:

1. Obtain the server-certificate for the XenServer
2. Import the server-certificate into the local certificate store of the eG agent

For an elaborate discussion on each of the above-mentioned steps, refer to the Troubleshooting section in the Monitoring XenServers document.

• Once the above value is provided, click on the Update button to register the changes made.