Vagrant VirtualBox provider memory configuration for low‑traffic workloads without automatic idle shutdown

Goal: reduce host resource consumption for low‑traffic workloads by automatically lowering the VirtualBox VM’s memory or suspending the guest when it detects idle network or CPU activity.

Constraint: Vagrant’s VirtualBox provider lacks a built‑in mechanism to monitor guest inactivity and initiate a vagrant suspend or memory resize; operators must rely on external cron jobs, host power‑management hooks, or custom scripts.

Uncertainty: how can host‑level idle detection (e.g., screen saver, network traffic thresholds) be reliably mapped to Vagrant lifecycle actions without introducing race conditions or unintended service disruption?

What host‑level mechanisms can trigger a vagrant suspend based on sustained low network traffic?

Is there a safe way to adjust the memory allocation of a running VirtualBox VM via Vagrant without destroying the VM?

Are there existing Vagrant plugins or provider‑specific hooks that provide automatic idle shutdown for the VirtualBox provider?