NFS vs VirtualBox Shared Folders: Performance vs Compatibility

Goal

Ensure a stable synced folder for a Vagrant VM running on a Windows host, using NFS for performance while avoiding silent mount failures.

Constraints

• NFS provisioner on Windows may silently fail when the Windows NFS client or firewall is misconfigured.
• Vagrant documentation does not specify a fallback to VirtualBox shared folders when NFS fails.
• Mount attempts can precede full readiness of the host NFS service, causing intermittent failures during provisioning.

Unresolved Questions

1. Does Vagrant automatically switch to VirtualBox shared folders if an NFS mount fails on a Windows host, or does it simply raise an error?
2. What provisioning order or pre‑check steps can guarantee that the Windows NFS service is fully ready before Vagrant attempts to mount?
3. Which diagnostic commands or log entries can reliably detect silent NFS mount failures during vagrant up or vagrant reload?