LDoms Guest Details Test

This test monitors the amount of the physical server's resources that each guest on a Solaris LDoms server is taking up. Using the metrics reported by this test, administrators can determine which virtual guest is taking up most CPU, which guest is taking up the maximum memory, etc. Note that the amount of resources taken up by a guest will be limited by the resource allocations that have been made by administrators. For example, an administrator could cap the amount of memory that a specific guest may take.

Target of the test : A Solaris LDoms server

Agent deploying the test : An internal agent

Outputs of the test : One set of results for each guest configured on the Solaris LDoms server.

Configurable parameters for the test
Parameter Description

Test period

How often should the test be executed

Host

The host for which the test is to be configured.

Port

The port number at which the specified host listens. By default, the port is NULL.

Domain

Specify the domain within which the virtual guests reside. Since the Solaris LDoms server supports only Solaris and Linux guests, this parameter should always be set to none.

Admin User

This test connects to each virtual guest and collects status and resource usage statistics from the guest. In order to do so, the test must be configured with user privileges that allow a remote connection to the virtual guest from the Solaris host. If a single user has access to all the guest domains on the Solaris server, specify the name of that user against Admin User, and specify his password against Admin Password. On the other hand, if the user credentials vary from one guest to another, then multiple Admin Users and Admin Passwords might have to be specified for every Solaris LDoms server being monitored.

To help administrators provide these user details quickly and easily, the eG administrative interface embeds a special configuration page. To access this page, simply click on the Click here hyperlink that appears just above the parameters of this test in the test configuration page. To know how to use the special page, refer to Configuring Users for VM Monitoring.

Admin Password

The password of the Admin User needs to be provided here. Here again, if multiple passwords need to be specified, then follow the procedure detailed in Configuring Users for VM Monitoring.

Confirm Password

Confirm the password by retyping it here. Here again, if multiple passwords need to be confirmed, then follow the procedure detailed in Configuring Users for VM Monitoring.

KeonCommand

Keon is a security mechanism that can be used with a multitude of operating systems to provide a centralized base for user account and password management, user access and inactivity control, system integrity checking, and auditing. If the Keon security model is in use on the Solaris LDoms host being monitored, then this test may require special user privileges for executing the operating system commands. In such a case, specify the exact command that the test is permitted to execute, in the KeonCommand text box. For example, if the keon command to be executed by the test is sudo, specify sudo in the KeonCommand text box. Alternatively, you can even specify the full path to the sudo command in the KeonCommand text box. On the other hand, if a Keon security model is not in place, then set the KeonCommand parameter to none.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Is VM powered on?

Whether the logical domain is currently running on the Solaris LDoms server or no.

Boolean

The value 1 indicates that the guest is up and running. The value 0 could indicate that the guest has been powered-off; it could also indicate that the guest has been moved to a different server.

While the test reports a wide variety of other metrics too for virtual machines that are alive, only the powered on status is indicated for virtual machines that are currently not available.

Physical CPU utilization of VM

Indicates the percentage of the physical CPU processing power of the physical server that is used by the guest.

Percent

A high value for this measure indicates a virtual machine that one/more processes executing on the guest domain are using up too much physical CPU. Beside draining the server of its physical CPU resources, this can also affect the CPU allocations to other guests, thereby adversely impacting the performance of the applications on those guest domains.

Virtual CPU utilization of VM

Indicates the percentage of virtual CPU utilized by this guest domain.

Percent

A high value for this measure indicates that resource-intensive processes are executing on the guest domain.

Percent of virtual CPUs allocated

Indicates the ratio of the virtual CPUs allocated to this guest domain to the total number of CPUs on the server, expressed as a percentage.

 

Percent

These measures help determine whether CPU allocations to the guest domain are commensurate to the current and expected processing load on the domain; over-allocations/under-allocations are thus brought to light. 

Virtual CPUs allocated to VM

Indicates the number of CPUs allocated to the guest domain.

Number

Physical memory allocated to VM

Indicates the amount of physical memory currently allocated to the guest.

MB

These measures help determine whether memory allocations to the guest domain are commensurate to the memory requirements of the domain; over-allocations/under-allocations are thus brought to light. 

Percent of physical memory allocated to VM

Indicates the percentage of total physical memory that is allocated to VM.

Percent