VM CPU Status (PI_VCI)
- Organization of this page
Function
This record stores performance data on a virtual CPU being used by a virtual machine over a unit of time. This record is a multi-instance record.
In this record, you can collect performance data such as CPU usage by a virtual machine. The CPU usage can be divided into CPU usage and CPU insufficiency. The figure below shows an example of data that can be collected in this record.
|
|
![[Figure]](GRAPHICS/ZU050004.GIF)
- Note:
-
-
Information cannot be collected if an attempt to connect to the monitored physical server fails.
-
Information cannot be collected for a virtual machine that is not running.
-
For Hyper-V, if there are multiple virtual machines with the same virtual machine name, PFM - RM for Virtual Machine might not be able to collect the correct information.
-
For Hyper-V, any special character contained in the virtual machine name is converted to a different character and then stored in the VM Name field. The conversion rules are as follows:
Before conversion
After conversion
/ and \
-
# and *
_
(
[
)
]
-
Default values and values that can be changed
|
Item |
Default value |
Can it be changed? |
|---|---|---|
|
Collection Interval |
300 |
Yes |
|
Collection Offset |
0 |
Yes |
|
Log |
No |
Yes |
|
LOGIF |
Blank |
Yes |
|
Over 10 Sec Collection Time |
No |
No |
ODBC key field
PI_VCI_VM_ID
PI_VCI_CPU_ID
Lifetime
None
Record size
-
Fixed portion: 937 bytes
-
Variable portion: 1,003 bytes
Fields
|
PFM - View name (PFM - Manager name) |
Explanation |
Summary |
Grouping |
Format |
Delta |
When not collected |
Unsup-ported |
|---|---|---|---|---|---|---|---|
|
Record Type (INPUT_RECORD_TYPE) |
The record name. This is always VCI. |
COPY |
COPY |
char (8) |
No |
-- |
Docker environment (Windows) |
|
Record Time (RECORD_TIME) |
The time when the record was created. |
COPY |
COPY |
time_t |
No |
-- |
Docker environment (Windows) |
|
Interval (INTERVAL) |
Interval during which the information is collected. [Units: seconds] |
COPY |
FIXED |
ulong |
No |
-- |
Docker environment (Windows) |
|
VA DeviceID (VADEVICEID) |
The device ID of a monitored host. |
COPY |
COPY |
string(256) |
No |
-- |
Docker environment (Windows) |
|
VM ID (VM_ID) |
ID of the virtual machine. For Hyper-V, the root partition is set to Root. |
COPY |
FIXED |
string (65) |
No |
No |
Docker environment (Windows) |
|
CPU ID (CPU_ID) |
ID of the virtual CPU. |
COPY |
FIXED |
string (32) |
No |
No |
Docker environment (Windows) |
|
VM Host Name (VM_HOST_NAME) |
Host name of the virtual machine. |
COPY |
FIXED |
string(257) |
No |
Blank |
Hyper-V KVM logical partitioning feature Docker environment (Windows) |
|
VM Name (VM_NAME) |
Name of the virtual machine. |
COPY |
FIXED |
string (257) |
No |
Blank |
Docker environment (Windows) |
|
Sampling Time (SAMPLING_TIME) |
Sampling time. The time when the performance information is collected on the host machine. Displayed in the following format: yyyy-mm-ddThh:mm[±hh:mm]#1 |
COPY |
FIXED |
string (32) |
No |
Blank |
Docker environment (Windows) |
|
Used (USED)#2 |
Amount of used virtual CPU resources. CPU resources that could run a virtual machine on a virtual CPU. [Units: MHz] |
HILO |
ADD |
double |
No |
VMware: 0 Hyper-V: 0 KVM: 0 logical partitioning feature: -1 Podman environment: 0 |
Docker environment |
|
Insufficient (INSUFFICIENT) |
Amount of virtual CPU insufficiency. CPU resources that could not run a virtual machine on a virtual CPU. [Units: MHz] |
HILO |
ADD |
double |
No |
VMware: 0 logical partitioning feature: -1 |
Hyper-V KVM Docker environment Podman environment |
|
Request (REQUEST) |
Amount of virtual CPU requests. Resources required to run virtual machines. (This is the total of the amount of allocated CPUs added to the amount of unallocated CPUs.) [Units: MHz] |
HILO |
ADD |
double |
No |
VMware: 0 logical partitioning feature: -1 |
Hyper-V KVM Docker environment Podman environment |
|
Used % (USED_PERCENT)#2 |
Usage rate of virtual CPUs. Percentage of CPU resources that are allocated to a virtual CPU. [Units: %] |
HILO |
AVG |
double |
No |
VMware: 0 Hyper-V: 0 KVM: 0 logical partitioning feature: -1 Docker environment (Linux): 0 Podman environment: 0 |
Docker environment (Windows) |
|
Insufficient % (INSUFFICIENT_PERCENT) |
Insufficiency rate of virtual CPUs. Percentage of CPU resources that are unallocated to a virtual CPU. [Units: %] |
HILO |
AVG |
double |
No |
VMware: 0 logical partitioning feature: -1 |
Hyper-V KVM Docker environment Podman environment |
|
Request % (REQUEST_PERCENT) |
Request rate of virtual CPUs. Percentage of CPU resources for which virtual CPUs are requested. [Units: %] |
HILO |
AVG |
double |
No |
VMware: 0 logical partitioning feature: -1 |
Hyper-V KVM Docker environment Podman environment |
|
Used Per Request (USED_PER_REQUEST) |
Usage ratio of virtual CPUs. Percentage of the CPU resources, required to run a virtual machine, that are CPU resources that could run a virtual machine. [Units: %] |
HILO |
AVG |
double |
No |
VMware: 0 logical partitioning feature: -1 |
Hyper-V KVM Docker environment Podman environment |
|
Insufficient Per Request (INSUFFICIENT_PER_REQUEST) |
Insufficiency rate for virtual CPUs. Percentage of the CPU resources, required to run a virtual machine, that are CPU resources that could not run a virtual machine. [Units: %] |
HILO |
AVG |
double |
No |
VMware: 0 logical partitioning feature: -1 |
Hyper-V KVM Docker environment Podman environment |
|
Co-Stop (CO_STOP) |
CPU conflict. CPU resources that the virtual machine could not run due to CPU conflict. [Units: MHz] |
HILO |
ADD |
double |
No |
VMware: 0 |
Hyper-V KVM logical partitioning feature Docker environment Podman environment |
|
Co-Stop % (CO_STOP_PERCENT) |
CPU conflict rate. Percentage of CPU resources that the virtual machine could not run due to CPU conflict. [Units: %] |
HILO |
AVG |
double |
No |
VMware: 0 |
Hyper-V KVM logical partitioning feature Docker environment Podman environment |
- #1
-
The value used in [±hh:mm] varies depending on the time zone of the monitored host. For example, if the monitored virtual environment is operating according to JST, +09:00 is displayed. If the monitored virtual environment is operating according to UTC, Z is displayed.
- #2
-
For Hyper-V, KVM, Docker environment, or Podman environment, this field requires performance data to be collected at least twice.