2.3.14 Virtualized system functionality and collected performance data
In virtualized systems, the setup of provided resources differs depending on how the system is implemented. Also, resource changes might or might not require temporary stoppage of a logical partition. If a logical partition needs to be stopped, this should not affect much because PFM - Agent for Platform is also stopped. However, if a logical partition does not need to be stopped, and the system resources change dynamically, the performance data obtained by PFM - Agent for Platform might be significantly affected. In this case, we recommend that you collect performance data not significantly affected by dynamic resource changes.
The following table shows the resources that can be collected for each virtualized system.
|
Virtualized system |
Resource |
|||
|---|---|---|---|---|
|
Processor count |
Memory |
Disk |
Network |
|
|
Zone |
-- |
-- |
TS |
-- |
|
PowerVM |
DS |
DS |
TS |
TS |
|
HP Integrity Virtual Machines (I-VM) |
TS |
TS |
TS |
TS |
|
VMware/KVM |
TS |
TS |
TS |
TS |
|
Hitachi Compute Blade logical partitioning feature |
TS |
TS |
-- |
TS |
|
WPAR |
DS |
DS |
DS |
-- |
|
Linux container# |
-- |
-- |
TS |
TS |
- Legend:
-
DS: Dynamic change is possible.
TS: Logical partitions or the Linux container must be suspended for changes to take effect in them or the Linux container itself.
--: Not supported
- #:
-
PFM - Agent for Platform supports Docker and Podman as a Linux container engine.