Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time

Vagrant WinNFSd

Manage and adds support for NFS on Windows.

Supported Platforms

As of version 1.0.6 or later Vagrant 1.5 is required. For Vagrant 1.4 please use the plugin version 1.0.5 or lower.

Supported guests:

  • Linux


vagrant plugin install vagrant-winnfsd

Activate NFS for Vagrant

To activate NFS for Vagrant see:

The plugin extends Vagrant in the way that you can use NFS also with Windows. So the following hint on the Vagrant documentation page is no longer true:

Windows users: NFS folders do not work on Windows hosts. Vagrant will ignore your request for NFS synced folders on Windows.

You will also need to declare some sort of network in order for NFS to work (the VirtualBox implied network will not work). Luckily this is easily done by adding the following line to your Vagrantfile:

# A private dhcp network is required for NFS to work (on Windows hosts, at least) "private_network", type: "dhcp"



You can activate the logging of the NFS daemon which will show the daemon window in the foreground. To activate the logging set the config.winnfsd.logging to on.

Set uid and gid

You can set the uid via the config.winnfsd.uid param and the gid via the config.winnfsd.gid param. Example:

Vagrant.configure('2') do |config|
    config.winnfsd.uid = 1
    config.winnfsd.gid = 1

Note that will be set global, that means the uid and gid is taken from the first box which starts the NFS daemon. If a box with an other uid or gid is started after that the option will be ignored.