VM Status (PI_VI)
- Organization of this page
Function
This record stores performance data on 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 the virtual machine, CPU insufficiency, and CPU allocation. The figure below shows an example of data that can be collected in this record.
|
|
![[Figure]](GRAPHICS/ZU050003.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.
-
Default values and values that can be changed
|
Item |
Default value |
Can it be changed? |
|---|---|---|
|
Collection Interval |
300 |
Yes |
|
Collection Offset |
0 |
Yes |
|
Log |
Yes |
Yes |
|
LOGIF |
Blank |
Yes |
|
Over 10 Sec Collection Time |
No |
No |
ODBC key field
PI_VI_VM_ID
Lifetime
None
Record size
-
Fixed portion: 937 bytes
-
Variable portion: 1,223 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 VI. |
COPY |
COPY |
char (8) |
No |
-- |
-- |
|
Record Time (RECORD_TIME) |
The time when the record was created. |
COPY |
COPY |
time_t |
No |
-- |
-- |
|
Interval (INTERVAL) |
Interval during which the information is collected. [Units: seconds] |
COPY |
FIXED |
ulong |
No |
-- |
-- |
|
VA DeviceID (VADEVICEID) |
The device ID of a monitored host. |
COPY |
COPY |
string (256) |
No |
-- |
-- |
|
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 |
-- |
|
Clocks (CLOCKS)#1 |
Clock frequency of the CPU resources. The value that is the total of the clock frequencies of the physical CPUs allocated to the virtual machine. [Units: MHz] |
COPY |
ADD |
double |
No |
VMware: 0 Hyper-V: 0 KVM: 0 logical partitioning feature: -1 |
Docker environment Podman environment |
|
Count (COUNT) |
Number of physical CPU cores in the CPU resources. The number of cores of the physical CPUs allocated to the virtual machine. |
COPY |
ADD |
long |
No |
VMware: 0 Hyper-V: 0 KVM: 0 logical partitioning feature: -1 Docker environment: 0 |
Podman environment |
|
VM Host Name (VM_HOST_NAME) |
Host name of the virtual machine. |
COPY |
FIXED |
string(257) |
No |
Blank |
Hyper-V KVM logical partitioning feature |
|
VM Name (VM_NAME) |
Name of the virtual machine. |
COPY |
FIXED |
string (257) |
No |
Blank |
-- |
|
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]#2 |
COPY |
FIXED |
string (32) |
No |
Blank |
-- |
|
Used (USED)#3 |
CPU usage amount. CPU resources that could run a virtual machine on a physical 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 CPU insufficiency. CPU resources that could not run a virtual machine on a physical CPU. [Units: MHz] |
HILO |
ADD |
double |
No |
VMware: 0 logical partitioning feature: -1 |
Hyper-V KVM Docker environment Podman environment |
|
Request (REQUEST) |
Amount of CPU requests. The amount of CPU resources required to run a virtual machine. (This is the total allocated resources added to the total unallocated resources.) [Units: MHz] |
HILO |
ADD |
double |
No |
VMware: 0 logical partitioning feature: -1 |
Hyper-V KVM Docker environment Podman environment |
|
Host Used % (HOST_USED_PERCENT) |
Usage rate of host CPUs. Percentage of total physical CPU resources that were executed on a physical CPU. [Units: %] |
HILO |
AVG |
double |
No |
VMware: 0 KVM: 0 logical partitioning feature: -1 Podman environment: 0 |
Hyper-V Docker environment |
|
Used % (USED_PERCENT)#1,#3,#4#5 |
CPU usage rate. Percentage of CPU resources that could run a virtual machine on a physical CPU. [Units: %] |
HILO |
AVG |
double |
No |
VMware: 0 Hyper-V: 0 KVM: 0 logical partitioning feature: -1 Docker environment: 0 Podman environment: 0 |
-- |
|
Insufficient % (INSUFFICIENT_PERCENT)#1 |
CPU insufficiency rate. Percentage of CPU resources that could not run a virtual machine on a physical CPU. [Units: %] |
HILO |
AVG |
double |
No |
VMware: 0 logical partitioning feature: -1 |
Hyper-V KVM Docker environment Podman environment |
|
Request % (REQUEST_PERCENT)#1 |
CPU request rate. Percentage of CPU resources required to run a virtual machine. (This is the total of the CPU allocation rate added to the CPU unallocation rate.) [Units: %] |
HILO |
AVG |
double |
No |
VMware: 0 logical partitioning feature: -1 |
Hyper-V KVM Docker environment Podman environment |
|
Used Per Request (USED_PER_REQUEST) |
% of allocatable CPU resources (= amount of CPU usage/amount of CPU requests). Percentage of the CPU resources required to run a virtual machine, 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) |
Rate of unallocated CPUs (= amount of CPU insufficiency/amount of CPU requests). Percentage of the CPU resources required to run a virtual machine, 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 |
|
Affinity (AFFINITY) |
Physical CPU that can be moved. The Affinity setting specifies that a physical CPU can be allocated to an individual virtual machine. (Ex: If a virtual machine can be allocated to physical CPU 1 and 2, the value of this field is 1,2.) |
COPY |
FIXED |
string (32) |
No |
Blank |
Hyper-V logical partitioning feature Podman environment |
|
Share (SHARE) |
CPU allocation ratio. A value used to request the CPU resources to be allocated to virtual machines. If two or more virtual machines require a large amount of CPU resources at the same time, the CPU resources are allocated according to this ratio. For Hyper-V, the root partition information cannot be obtained. For logical partitioning feature, when the CPU of the associated logical partition is running in dedicated mode, the value is always set to -1 and cannot be obtained. |
COPY |
AVG |
double |
No |
VMware: 0 Hyper-V: 0 logical partitioning feature: -1 Docker environment: 0 |
KVM Podman environment |
|
Max (MAX) |
Maximum value for CPU allocation. The maximum value for CPUs allocatable to a virtual machine. [Units: MHz] -1: No limit. For Hyper-V, the root partition information cannot be obtained. For logical partitioning feature, -1 indicates that the value cannot be obtained. |
COPY |
ADD |
double |
No |
VMware: 0 Hyper-V: 0 KVM: 0 logical partitioning feature: -1 |
Docker environment Podman environment |
|
Min (MIN) |
Minimum value for CPU allocation. The minimum value for CPUs allocatable to a virtual machine. [Units: MHz] For Hyper-V, the root partition information cannot be obtained. |
COPY |
ADD |
double |
No |
0 |
KVM logical partitioning feature Docker environment Podman environment |
|
Expectation (EXPECTATION) |
Balance value for CPU allocation. If two or more virtual machines require a large amount of resources at the same time, this value estimates what CPU resources can be expected to be available for the virtual machines. [Units: MHz] For logical partitioning feature, when the CPU of the associated logical partition is running in dedicated mode, the value is always set to -1 and cannot be obtained. |
HILO |
ADD |
double |
No |
VMware: 0 logical partitioning feature: -1 |
Hyper-V KVM Docker environment Podman environment |
|
Max % (MAX_PERCENT) |
Maximum % for CPU allocation. Percentage of CPU resources that is the maximum allocatable to a virtual machine. [Units: %] |
HILO |
AVG |
double |
No |
VMware: 0 Hyper-V: 0 logical partitioning feature: -1 |
KVM Docker environment Podman environment |
|
Min % (MIN_PERCENT) |
Minimum % for CPU allocation. The minimum percentage of CPU resources that are allocatable to a virtual machine. [Units: %] |
HILO |
AVG |
double |
No |
0 |
KVM logical partitioning feature Docker environment Podman environment |
|
Expectation % (EXPECTATION_PERCENT)#4 |
Balance point rate for CPU allocation. Percentage of CPU resources that can be expected to be used for virtual machines. [Units: %] For logical partitioning feature, when the CPU of the associated logical partition is running in dedicated mode, the value is always set to -1 and cannot be obtained. |
HILO |
AVG |
double |
No |
VMware: 0 logical partitioning feature: -1 Docker environment: 0 |
Hyper-V KVM Podman environment |
|
Snapshot (SNAPSHOT) |
Whether or not snapshots are taken.
|
-- |
FIXED |
ulong |
No |
0 |
Hyper-V KVM logical partitioning feature 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 changes in accordance with the UseVcpuMax value set as instance information as follows:
N: Clock frequency of the physical CPU x number of cores
Y: Clock frequency of the CPU allocated to the virtual machine
- #2
-
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.
- #3
-
For Hyper-V or KVM, this field requires performance data to be collected at least twice.
- #4
-
For Docker environment, this field requires performance data to be collected at least twice.
- #5
-
For Podman environment, this field requires performance data to be collected at least twice.