Run fstrim in a VM via the guest agent #19

New Issue

2026-11-02T22:55:43+01:00

Duckboot commented

2026-11-02 22:55:43 +01:00

Why

On thin-provisioned storage (local-lvm, ZFS), blocks a VM has freed are only returned to the pool after a trim. Running fstrim from the TUI reclaims space without logging in to the VM.

Proposal

A key on the info screen runs fstrim in a running VM that has the guest agent enabled.
First ping the agent and show a clear message if it is not running.
Not for LXC: containers have no guest agent. Use pct fstrim on the node instead, which could reuse the SSH path from the LXC shell feature.

cv4pve-cli (2.4.0)

do vm agent ping <node> <vmid>
do vm agent fstrim <node> <vmid>

Done when

fstrim runs on VM 108 (with approval) and the result is shown.
Tests are written first.

Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com

## Why On thin-provisioned storage (`local-lvm`, ZFS), blocks a VM has freed are only returned to the pool after a trim. Running `fstrim` from the TUI reclaims space without logging in to the VM. ## Proposal - A key on the info screen runs `fstrim` in a running VM that has the guest agent enabled. - First ping the agent and show a clear message if it is not running. - Not for LXC: containers have no guest agent. Use `pct fstrim` on the node instead, which could reuse the SSH path from the LXC shell feature. ## cv4pve-cli (2.4.0) - `do vm agent ping <node> <vmid>` - `do vm agent fstrim <node> <vmid>` ## Done when - fstrim runs on VM 108 (with approval) and the result is shown. - Tests are written first. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Duckboot added the

priority

4-nice-to-have

label 2026-11-02 22:55:43 +01:00

Duckboot referenced this issue from a commit

2026-11-03 01:08:32 +01:00

Run fstrim in a VM via the guest agent

Duckboot referenced a pull request that will close this issue

2026-11-03 01:08:40 +01:00

Run fstrim in a VM via the guest agent #31

Duckboot closed this issue

2026-11-03 01:33:20 +01:00