PMDAKVM(1)
π PMDAKVM π
okay bestie so this is a page from the General Commands Manual section and it's literally all about pmdakvm, the Linux virtualization performance metrics domain agent (PMDA). sit down, grab a strawberry π, we're doing this.
β¨ NAME β¨
pmdakvm β Linux virtualization performance metrics domain agent (PMDA) π
πΈ SYNOPSIS πΈ
$PCP_PMDAS_DIR/kvm/pmdakvm [-D debug]
that's it. that's the whole vibe check. π
π¦ DESCRIPTION π¦
so pmdakvm is a Performance Metrics Domain Agent (PMDA) β and what a PMDA does is export metric values from the Linux KVM (Kernel Virtual Machine) virtualization subsystem. no cap, that's the whole job. π§
and here's the tea: per-processor KVM trace metrics come from the kernel events enumerated below /sys/kernel/debug/tracing/events/kvm, and you can configure them statically using the pmdakvm configuration file, which lives at /etc/pcp/kvm/kvm.conf. π
π INSTALLATION π
first things first: optionally configure your trace points in the configuration file. then install the KVM PMDA using the Install script, as root:
# cd $PCP_PMDAS_DIR/kvm
# ./Install
and to uninstall, bestie, you do this as root:
# cd $PCP_PMDAS_DIR/kvm
# ./Remove
now listen: pmdakvm is launched by pmcd(1) and should never be executed directly. like, don't. the Install and Remove scripts notify pmcd(1) when the agent is installed or removed, so the machinery handles itself. main character energy only. π
π CAVEATS π
okay this part is important, no skipping:
while pmdakvm is running, it holds references to kernel resources within the KVM device driver. which means β and I need you to hear me β it is not possible to unload or reload the device driver module while the PMDA is running. π
so the ideal procedure to reload the kernel module is the reverse of what we just did in the ``INSTALLATION'' section. i.e.:
- first run
./Remove - then reload the kernel module
- then run
./Install
in that order. periodt. π₯
π FILES π
$PCP_SYSCONF_DIR/kvm/kvm.confβ configuration file for thepmdakvmagent$PCP_PMDAS_DIR/kvm/Installβ installation script for thepmdakvmagent$PCP_PMDAS_DIR/kvm/Removeβ undo installation script for thepmdakvmagent$PCP_LOG_DIR/pmcd/kvm.logβ default log file for error messages frompmdakvm
π PCP ENVIRONMENT π
environment variables with the prefix PCP_ are used to parameterize the file and directory names used by PCP. every time you install, the file /etc/pcp.conf contains the local values for these variables. and the $PCP_CONF variable may be used to specify an alternative configuration file, as described in pcp.conf(5). slay. β¨
π DEBUGGING OPTIONS π
-D,--debugβ turns on the output of additional diagnostics onstderrto help triage problems. lowkey though, the information is sometimes cryptic and is primarily intended to provide guidance for developers rather than for end-users.debugis a comma separated list of debugging options; usepmdbg(1)with the-loption to get a list of the available debugging options and what they actually mean. π
β SEE ALSO β
PCPIntro(1), pmcd(1) and kvm(1).
and that's the whole page, bestie!! π«Ά this came to you from Performance Co-Pilot, PCP β the PMDAKVM(1) energy, dated however old this thing is. go forth and monitor some virtual machines, you absolute icon. πππ¦
π¦ where this page comes from
- arch rolling: pcp 7.2.2-2 Β· GPL-2.0-or-later AND LGPL-2.1-or-later AND CC-BY-3.0
- fedora 43: pcp-doc 7.2.1-1.fc43
- fedora 43: pcp-doc 7.2.2-1.fc43
- fedora 43: pcp-doc 7.2.2-2.fc43 Β· GPL-2.0-or-later AND CC-BY-3.0
- fedora 44: pcp-doc 7.2.1-1.fc44
- fedora 44: pcp-doc 7.2.2-1.fc44
- fedora 44: pcp-doc 7.2.2-2.fc44 Β· GPL-2.0-or-later AND CC-BY-3.0
- ubuntu stonking: pcp 7.2.1-2build1
- Copyright (c) 2020-2021 Red Hat
- Copyright (c) 2008 Aconex. All Rights Reserved
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms