| Measurement |
Description |
Measurement Unit |
Interpretation |
| Run_state |
Indicates the current operational state of this VM. |
|
The values that this measure can report and their corresponding numeric values are discussed in the table below:
| Measure Value |
Numeric Value |
| Stopped |
0 |
| Running |
1 |
| Starting |
2 |
| Stopping |
3 |
| Suspended |
4 |
| Template |
5 |
Note:
By default, this measure reports one of the values listed under Measure Values to indicate the current status of VM. In the graph of this measure however, the same is represented using the numeric equivalents only. |
| Cpu_count |
Indicates the number of virtual CPUs allocated to this VM. |
Number |
|
| Cpu_count_limit |
Indicates the number of processors that this VM is allowed to make use of. |
Number |
|
| Cpu_utilization |
Indicates the percentage of the vCPUs allowed for use that is currently in use. |
Percent |
A high value for this measure indicates that the VM is consuming too many vCPUs. Compare this value across VMs to know which VM is consuming the maximum vCPUs. |
| Physical_cpu_util |
Indicates the percentage of the physical CPUs currently used by this VM. |
Percent |
A high value for this measure indicates that the VM is consuming too many vCPUs physical CPUs. A probable cause for high CPU utilization is the presence of one or more CPU-intensive processes on the VM.
Use the detailed diagnosis of this measure to identify the CPU-intensive processes running on a VM. |
| Cpu_periority |
Indicates CPU priority value set for for this VM when scheduling. |
Number |
|
| Cpu_util_cap |
Indicates the maximum number of CPUs used by this VM, as per the credit scheduler. |
Number |
Oracle VM's default CPU scheduler is the credit scheduler. The credit scheduler uses a credit/debit system to fairly share CPU resources between virtual machines. Credits are assigned to each running virtual machine, along with the allocated fraction of CPU resources. The credit scheduler continually increments/decrements credits from running virtual machines, which is how the credit scheduler balances CPU resources. |
| Current_memory |
Indicates the amount of memory currently used by this VM. |
MB |
|
| Memory |
Indicates the amount of memory allocated to this VM. |
MB |
|
| Memory_limit |
Indicates the maximum amount of memory that can be allocated to this VM. |
MB |
|
| Memory_used_per |
Indicates the percentage of physical memory used by this VM. |
Percent |
Compare the value of this measure across VMs to know which VM is consuming the maximum memory.
A high value for this measure indicates that the VM is consuming memory resources excessively. One of the common causes for this is the execution of one/more memory-intensive operations on the VM.
Use the detailed diagnosis of this measure to identify the memory-intensive processes running on a VM. |
| Disk_capacity |
Indicates the total disk capacity of this VM. |
MB |
|
| Huge_pages |
Indicates whether/not Huge Pages are enabled for this VM. |
|
Paging is a process whereby the CPU, for a system, allocates contiguous blocks of memory for use by a running process. These pages are tracked by the operating system, so that processes access the correct blocks of assigned memory. Typically, these blocks are sized at 4 KB. This means that when a process uses 1 GB of memory, 262144 page (1 GB/4 KB) entries are created and are referenced continually by the process.
Most current CPU architectures support bigger pages to reduce the number of page lookups required by the CPU or Operating System. On Linux systems, these are called Huge Pages, while on Windows systems they are called Large Pages. These terminologies are equivalent.
Oracle VM Manager provides an option to enable huge page support for a paravirtualized virtual machine when you create or edit a virtual machine. Huge pages are not supported on virtual machines running on SPARC architecture. Attempting to enable Huge Page support for a virtual machine running on a SPARC server, causes an exception to be returned.
The values that this measure can report and their corresponding numeric values are discussed in the table below:
| Measure Value |
Numeric Value |
| Enabled |
1 |
| Disabled |
0 |
Note:
By default, this measure reports one of the values listed under Measure Values to indicate whether/not Huge Pages are enabled for a VM. In the graph of this measure however, the same is represented using the numeric equivalents only. |
| High_availability |
Indicates whether/not high availability is enabled for this VM. |
|
You can set up High Availability to help ensure the uninterrupted availability of a virtual machine. If HA is configured and a Oracle VM Server is restarted or shut down, the virtual machines running on it are either restarted on, or migrated to, another Oracle VM Server.
The values that this measure can report and their corresponding numeric values are discussed in the table below:
| Measure Value |
Numeric Value |
| Enabled |
1 |
| Disabled |
0 |
Note:
By default, this measure reports one of the values listed under Measure Values to indicate whether/not HA is enabled for a VM. In the graph of this measure however, the same is represented using the numeric equivalents only. |