v2.11.0 — CRS integration + IOWait exemption
Highlights
Proxmox VE 9.2 Cluster Resource Scheduler (CRS) integration
- Detects the native CRS config from
/cluster/optionsand surfaces it on the dashboard — a quiet chip at the default, an info banner for load-aware modes, and a warning when CRS dynamic auto-rebalance is dueling with ProxBalance automigrate (both engines moving HA guests). - Edit CRS settings from the dashboard (mode, auto-rebalance, threshold/margin/hold, method) via
POST /api/pve-crs. Requires the API token to holdSys.Modifyon/; a missing permission is surfaced as an actionable 403. - HA-managed guests are flagged as managed-by-CRS in recommendations when the dynamic balancer is active.
IOWait exemption for passthrough / NAS nodes
- A node whose host IOWait is dominated by a guest on dedicated/passthrough storage (e.g. a NAS VM doing a RAID resync) is no longer falsely scored "unhealthy" or flagged for evacuation — migrating other guests can't relieve that IOWait.
- Auto-detected from raw-device passthrough disks, or set explicitly with an
io_exemptguest tag. One-click toggle in Guest Details; global on/off in Penalty Scoring → Expert Mode. - Indicators across the UI: ⊘ on the Map node + amber dot on exempt guests, and an
exemptchip on the node charts.
Evacuation
- The evacuation plan now offers "Include stopped guests" — stopped guests default to ignore (no point streaming cold disks on a routine rebalance); tick the box for maintenance/upgrade evacuations.
Fixes
- Asset cache-busting: deploys now stamp
app.js/tailwind.csswith a per-deploy build id, so browsers pick up new bundles automatically (no more manual hard-refresh after an update).
Full changelog: v2.10.1...v2.11.0