Host os: Elementary OS (Luna)
Version of nfsd running on the host:
The content of /etc/exports:
While installing vagrant, running the "vagrant up" command with nfs turned on, gave errors as given here: http://pastebin.com/7fHsE8Hq
However, the setup could be installed by stopping nfs shares.
Version: unspecified
Severity: normal
OS: Linux
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T139859 Vagrant and NFS are not always the best of friends [tracking] | |||
| Declined | None | T74144 'vagrant up' gives issues with nfs enabled on Elementary OS Luna host |
physik wrote:
I started over deleted the vagrant and the ~/.vagrant directories and downloaded the most recent versions of virtualbox and vagrant from the websites (not using the package manager).
Now I'm getting a timeout while mounting the folders
mount.nfs: Connection timed out
Try this work around: vagrant config nfs_shares no
That command will turn off the use of nfs in our Vagrantfile. The nfs problems would likely be on the vagrant side. They have custom code per distribution to manage the nfs share exports and it is possible the Luna does something they don't know how to manage properly.
(In reply to Bryan Davis from comment #3)
Try this work around: vagrant config nfs_shares no
That command will turn off the use of nfs in our Vagrantfile. The nfs
problems would likely be on the vagrant side. They have custom code per
distribution to manage the nfs share exports and it is possible the Luna
does something they don't know how to manage properly.
It would be helpful for someone using Luna regularly to file an upstream bug with Vagrant (https://github.com/mitchellh/vagrant/issues) and see if a reasonably small reproduction case can be created to work out why Vagrant and Luna are not agreeing on the proper configuration to share NFS mounts with the guest VM. Luna is an Ubuntu 12.04 variant but may be doing something with it's default configuration that is unexpected.
Unfortunately closing this Phabricator task as no further information has been provided.
@Ankitashukla: After you have provided the information asked for and if this still happens, please set the status of this task back to "Open" via the Add Action... → Change Status dropdown. Thanks!