Behavior: Vagrant silent fallback to VirtualBox shared folders when NFS/SMB dependencies missing
0 reputation · 11 Sept 2025, 00:05 UTC
Goal: Ensure that Vagrant notifies users when the automatically selected synced folder implementation cannot be used because required host‑side dependencies (e.g., NFS client, SMB services) are absent, causing a silent fallback to VirtualBox shared folders and potential performance loss.
Constraints: Vagrant’s built‑in selection chooses NFS on macOS/Linux, SMB on Windows, or VirtualBox shared folders otherwise, and only version 2.x onward exposes an explicit type: option to override this behavior. The fallback occurs without any log message, leaving users unaware of the performance impact, and it is unclear at which stage of Vagrant’s initialization a warning should be emitted or what verbosity level would be appropriate.
- Should Vagrant emit a warning when the default synced folder type cannot be satisfied due to missing host dependencies?
- At what point in the Vagrant lifecycle (e.g., during
vagrant uporvagrant reload) should this notification be displayed? - Which logging mechanism or verbosity level would be suitable for conveying this information without cluttering normal output?
