VDI-in-a-Box Processes Test

The vdimanager will not be available for use, if any/all of the following processes stop executing:

  • The KVM_tomcat process
  • Lmadmin, which is the Citrix license server manager process
  • Lmgrd, which is the FLEXlm license manager daemon that handles the initial point of contact with the VDI-in-a-Box appliance, and processes all licensing requests

The VDI-in-a-Box Processes test has been pre-configured to monitor and report on the status (whether running or not) of the above-mentioned processes and their resource usage. If users are not able to connect to the vdimanager or complain of a slowdown when working with the vdimanager, you can use this test to figure out if one/all of these critical processes are at fault.

  Target of the test : A VDI-in-a-Box Manager

Agent deploying the test : A remote agent

Outputs of the test : One set of results for each Process that is configured.

Configurable parameters for the test
Parameters Description

Test period

This indicates how often should the test be executed.


The host for which this test is to be configured.


The port at which the specified host listens to.

VDI in a Box Host

The IP address of the vdimanager that is being monitored.

VDI in a Box Username, VDI in a Box Password, and Confirm Password

The test needs to log on to the VDI-in-a-Box appliance to pull out the metrics of interest. For this purpose, you need to configure the test with the credentials of a user with login rights to the appliance. By default, the appliance supports a root user named root (with the default password root) and a Read-only user named kvm (with the default password kaviza123). If you prefer not to expose the credentials of the root user, then you can configure the VDI in a Box Username and VDI in a Box Password parameters with the credentials of the user kvm. Confirm the password of this user by retyping it in the Confirm Password text box.


The default password of user kvm is kaviza123. If this is changed, then make sure you configure the VDI in a box password parameter with the new password.

SSH Port

Specify the SSH port number of the vdimanager. By default, this is 22.


By default, this parameter is configured to monitor the KVM_tomcat, lmadmin, and lmgrd processes. If required, you can add more processes for monitoring by specifying these processes as a comma separated list of processNames:processPattern pairs. processName is a string that will be used for display purposes only. processPattern is an expression of the form - *expr* or expr or *expr or expr* or *expr1*expr2*... or expr1*expr2, etc. A leading '*' signifies any number of leading characters, while a trailing '*' signifies any number of trailing characters. The pattern(s) used vary from one application to another and must be configured per application. For example, to monitor the lmgrd process, your specification can be, Lmgrd:*CITRIX*vdimgr*lmgrd*,   where * denotes zero or more characters. Other special characters such as slashes (\) can also be used while defining the process pattern.


The Process parameter supports process patterns containing the ~ character.


By default, this parameter has a value "none"; this means that the test monitors all processes that match the configured patterns, regardless of the user executing them. If you want the test to monitor the processes for specific users alone, then, specify a comma-separated list of users to be monitored in the user text box. For instance: john,elvis,sydney

If multiple processes are configured for monitoring and multiple users are also configured, then the test will check whether the first process is run by the first user, the second process by the second user, and so on. For instance, if the processes configured are java:java.exe,apache:*httpd* and the users configured are john,elvis, then the test will check whether user john is running the process java, and user elvis is running the process apache. Similarly, if multiple processes are configured, but a single user alone is configured, then the test will check whether the specified user runs each of the configured processes. However, if you want to check whether a single process, say java.exe, is run by multiple users - say, james and jane - then, you have to do the following:

  • Your User specification should be: james,jane (if the target host is a Unix host
  • Your Process configuration should be: Process1:java.exe,Process2:java.exe. The number of processes in this case should match the number of users.

Such a configuration will ensure that the test checks for the java.exe process for both the users, james and jane.   

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Processes running

Indicates the number of instances of a process(es) currently executing on a host.


This value indicates if too many or too few processes corresponding to an application are executing on the host.

CPU utilization

Indicates the percentage of CPU used by executing process(es) corresponding to the pattern specified.


A very high value could indicate that processes corresponding to the specified pattern are consuming excessive CPU resources.

Memory utilization

For one or more processes corresponding to a specified set of patterns, this value represents the ratio of the resident set size of the processes to the physical memory of the host system, expressed as a percentage.


A sudden increase in memory utilization for a process(es) may be indicative of memory leaks in the application.