| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Powered_on |
Indicates whether this desktop is powered-on or not currently. |
|
The table below displays the States that can be reported by this measure, and their numeric equivalents:
Note:
By default, this measure reports one of the States listed in the table above. The graph of this measure however will represent the VM status using the numeric equivalents - 0 or 1. |
| Tot_ram_size |
Indicates the amount of memory allocated to this desktop. |
MB |
|
| Ram_util |
Indicates the percentage of allocated RAM been utilized by this desktop. |
Percent |
Ideally, the value of this measure should be low. A high value is indicative of excessive memory consumption by a desktop. In the event of a slowdown, you can compare the value of this measure across desktops to identify the desktop that is memory-intensive, and could hence be causing the slowdown. |
| Ram_used |
Indicates the amount of allocated RAM been utilized by this desktop. |
MB |
| Video_ram_size |
Indicates the total amount of video memory allocated to this desktop. |
MB |
This sets the size of the memory provided by the virtual graphics card available to the guest, in MB. As with the main memory, the specified amount will be allocated from the host's resident memory. Based on the amount of video memory, higher resolutions and color depths may be available. |
| Baloon_mem |
Indicates the configured balloon memory for this desktop. |
MB |
Normally, to change the amount of memory allocated to a virtual machine, one has to shut down the virtual machine entirely and modify its settings. With memory ballooning, memory that was allocated for a virtual machine can be given to another virtual machine without having to shut the machine down.
When memory ballooning is requested, the VirtualBox allocates physical memory from the guest operating system on the kernel level and locks this memory down in the guest. This ensures that the guest will not use that memory any longer; no guest applications can allocate it, and the guest kernel will not use it either. VirtualBox can then re-use this memory and give it to another virtual machine.
The memory made available through the ballooning mechanism is only available for re-use by VirtualBox. It is not returned as free memory to the host. Requesting balloon memory from a running guest will therefore not increase the amount of free, unallocated memory on the host.
Effectively, memory ballooning is therefore a memory overcommitment mechanism for multiple virtual machines while they are running. This can be useful to temporarily start another machine, or in more complicated environments, for sophisticated memory management of many virtual machines that may be running in parallel depending on how memory is used by the guests. |
| Num_cpu |
Indicates the number of virtual CPUs allocated to this desktop. |
Number |
|
| User_cpu |
Indicates the percentage of CPU time spent by this desktop on user processes. |
Percent |
If the CPU utilization of a desktop appears to be increasing consistently, then, you can use the value of this measure to figure out where the CPU time is being spent - on system processes? or user processes? |
| Kernal_cpu |
Indicates the percentage of CPU time spent by this desktop on kernel processes. |
Percent |
If the CPU utilization of a desktop appears to be increasing consistently, then, you can use the value of this measure to figure out where the CPU time is being spent - on kernel processes? or user processes? |
| cpu_util |
Indicates the percentage of the allocated CPU resources used by this desktop. |
Percent |
Compare the value of this measure to identify the desktop that is running CPU-intensive applications. Once the desktop is identified, then, you can use the User_cpu and the Kernal_cpu measures to know where the desktop is spending maximum CPU time - on kernel processes? or user processes? |