virtualization-memory-pressure
/virtualization-memory-pressure
Use when a Proxmox host reports high memory use or swap, to measure configured-versus-real memory per guest, swap pressure, balloon, and KSM before proposing any change.
- Author
- otixe ↗
- Repository
- agent-skills ↗
- Licence
- MIT
- Last repository change
- 26.10.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 26.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when a Proxmox host reports high memory use or swap, to measure configured-versus-real memory per guest, swap pressure, balloon, and KSM before proposing any change.
Original author description
Use when a Proxmox host reports high memory use or swap, to measure configured-versus-real memory per guest, swap pressure, balloon, and KSM before proposing any change.
How it works
- Authorization and test boundary
- Rule: free does not answer the question
- Distinguish cold swap from thrashing
- Counters are not rates
- Balloon
- Kernel Samepage Merging (KSM)
- Done when
SKILL.md preview
--- name: virtualization-memory-pressure description: "Use when a Proxmox host reports high memory use or swap, to measure configured-versus-real memory per guest, swap pressure, balloon, and KSM before proposing any change." --- # Virtualization Memory Pressure Triage ## Authorization and test boundary These instructions grant no permission. Confirm the exact resources, allowed effects and data handling before acting. Use synthetic canaries and disposable fixtures for deliberate failures; never use real credentials as test inputs. Keep secrets and fragments out of model context, arguments, logs and plaintext artifacts. Imports, constructors, help and dry-run commands may have effects. Establish external-effect isolation before executing untrusted code; application stubs are not a sandbox. Record untested scope and obtain separate authorization for production changes or destructive actions. Use this when someone says a Proxmox node uses too much RAM, is running out of memory, or feels slow. It also applies before adding a new VM, to check real headroom. Read-only diagnosis comes first; no configuration changes without explicit approval. ## Rule: `free` does not answer the question A summary of used and free memory can look healthy while swap is heavily used. Measure instead: - `SwapFree` against `SwapTotal` in `/proc/meminfo`, to see whether overcommitment is being paid in swap. - `Committed_AS` against `CommitLimit`, to see promised memory against what can be honored. - Configured memory against resident memory for each guest: `qm config ID` against the VmRSS of its `kvm` process. The host total is the last thing to check, not the first. ## Distinguish cold swap from thrashing Swap that is full but idle is not an emergency. Read the pressure stall file for memory and sample the `si` and `so` columns of `vmstat` over several seconds. Three signs of inert swap: high occupancy, memory pressure averages at zero, and no blocked processes. If the guest still stalls, compare the CPU and I/O pressure files; the bottleneck may be CPU, which belongs to the CPU contention skill. ## Counters are not rates `pswpin`, `pswpout`, balloon swap-in counts, and major fault counts are cumulative since boot. Take two readings separated by 30 seconds and report the delta. A large cumulative value is not evidence of current activity. ## Balloon A balloon configuration key does not prove ballooning works. Ask the running guest through the hypervisor monitor (`info balloon`) and compare the actual value to the maximum. A guest without the balloon driver or guest agent keeps its full allocation. Mark that cause as inference until verified inside the guest. ## Kernel Samepage Merging (KSM) Check that the daemon is running, the run flag, shared and sharing page counts, and whether each guest's memory regions are marked mergeable. Guests may be excluded by an explicit configuration option; never reverse such an option without the owner's approval. Changes to the daemon's configuration file should be preceded by a backup and by calculating the threshold from current host numbers. ## Done when The report includes per-guest configured against real memory, the swap and pressure evidence with deltas, balloon and KSM status, and a single health verdict stated plainly. Any proposed change lists its risk, reversibility, and rollback command, and is not applied without approval.
Versions
The database has no other skills named virtualization-memory-pressure.
Database snapshot: 13.11.2026 · package version e91357aa4a8f (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100virtualization-storage-hygiene
Use when a Proxmox host storage pool is filling up, to audit ZFS snapshots, clone dependencies, backup retention, and orphaned volumes before any destructive cleanup. - 100home-lab-virtualization-proxmox-esxi-setup
Use this skill when build a dedicated cybersecurity virtualization home lab using Proxmox VE or VMware ESXi. - 100proxmox-maintenance
Use when the user wants to perform maintenance, diagnostics, or configuration on their Proxmox VE host via SSH or the Proxmox API. Reads connection details from `$CLAUDE_USER_DATA/proxmox-mgmt/config.json` (populated by the `onboard` skill in this plugin). Triggers on phrases… - 100vm-cpu-contention-triage
Use when a virtual machine on a Proxmox host freezes, lags, or disconnects, to measure host CPU per KVM process with correct deltas before blaming the guest. - 100onboard
First-run onboarding for the proxmox-mgmt plugin. Interview the user about their Proxmox host — IP, SSH user, web UI URL, and (optionally) Proxmox API token references — and persist the result to `$CLAUDE_USER_DATA/proxmox-mgmt/config.json`. Run this before any other skill in… - 93proxmox-skill
Operate a Proxmox VE environment from this skill folder by reading connection details from the local `.env` file and using the bundled helper script to inspect nodes, QEMU VMs, and LXC containers, start existing guests, allocate a new VM or container ID, create a new VM shell,…