VirtualBox Shared Folders vs NFS for Cross-Platform Vagrant Teams

Direct answers

1. Yes. A single Vagrantfile can select NFS on macOS and Linux and fall back to VirtualBox shared folders on Windows using Ruby host-OS detection. No custom plugin is required; the logic is committed in the shared Vagrantfile rather than maintained per developer.
2. No. Default NFS options do not match Windows VirtualBox shared-folder ownership. Vagrant NFS defaults map_uid and map_gid to the host user's UID/GID, while Windows shared folders typically present files as UID 1000/GID 1000 (the guest vagrant user). Explicit mapping is required for consistency, assuming the guest primary user is UID 1000.

Likely explanation versus confirmed facts

Likely explanation

Vagrant does not silently fall back from NFS to VirtualBox shared folders when an NFS server is missing. Windows does not include an NFS server by default, so an unconditional type: :nfs fails on Windows hosts. Host-OS detection in the Vagrantfile is the standard zero-plugin workaround.

Confirmed facts

• Vagrant NFS on macOS and Linux defaults map_uid and map_gid to the host user's UID/GID unless overridden.
• VirtualBox shared folders on Windows typically map files to the guest vagrant user, UID 1000/GID 1000.
• Ownership mapping does not translate file mode bits or ACLs; chmod behavior can still differ between NFS and VirtualBox shared folders.
• WSL2 and msys2 may report unexpected host_os values, so verify the detection pattern on each exact developer setup.

Single Vagrantfile configuration

Vagrant.configure("2") do |config|
  config.vm.box = "generic/ubuntu2204"

  is_windows = RbConfig::CONFIG["host_os"] =~ /mswin|mingw|cygwin|windows/

  config.vm.synced_folder ".", "/vagrant",
    type: is_windows ? :virtualbox : :nfs,
    nfs_udp: false,
    map_uid: 1000,
    map_gid: 1000
end

• map_uid and map_gid are ignored by VirtualBox shared folders, so they are safe to include unconditionally.
• nfs_udp: false improves reliability on modern networks and is ignored when VirtualBox shared folders are active.
• This assumes the guest box's primary user is UID 1000/GID 1000. Adjust those values if your box uses a different user.

Verification steps

1. Run vagrant up on macOS, Linux, and Windows hosts. Windows should not report a missing NFS server.
2. SSH into the guest and run touch /vagrant/ownership-check && stat -c '%u %g' /vagrant/ownership-check. Expect 1000 1000 on all three platforms.
3. Run a small-file workload such as find /vagrant -type f | xargs cat > /dev/null and compare runtime; NFS should be materially faster on macOS and Linux than VirtualBox shared folders.
4. Confirm vagrant plugin list contains no NFS server plugin such as vagrant-winnfsd.

Missing diagnostic detail

If your guest box does not use UID 1000/GID 1000 for the primary user, provide that UID/GID pair; the map_uid and map_gid values must match the guest user to avoid permission mismatches.