title: NFS Vagrant on Fedora 22
body: <p>I'm trying to run Vagrant using libvirt as my provider. Using rsync is unbearable since I'm working with a huge shared directory, but vagrant does succeed when the nfs setting is commented out and the standard rsync config is set.</p>
  
  <pre><code>config.vm.synced_folder ".", "/vagrant", mount_options: ['dmode=777','fmode=777']
  </code></pre>
  
  <p>Vagrant hangs forever on this step here after running vagrant up</p>
  
  <pre><code>==&gt; default: Mounting NFS shared folders...
  </code></pre>
  
  <p>In my Vagrantfile I have this uncommented and the rsync config commented out, which turns NFS on.</p>
  
  <pre><code>config.vm.synced_folder ".", "/vagrant", type: "nfs"
  </code></pre>
  
  <p>When Vagrant is running it echos this out to the terminal.</p>
  
  <pre><code>Redirecting to /bin/systemctl status  nfs-server.service
  ● nfs-server.service - NFS server and services
     Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; disabled; vendor preset: disabled)
     Active: inactive (dead)
  Redirecting to /bin/systemctl start  nfs-server.service
  Job for nfs-server.service failed. See "systemctl status nfs-server.service" and "journalctl -xe" for details.
  </code></pre>
  
  <p>Results of systemctl status nfs-server.service</p>
  
  <pre><code>dillon@localhost ~ $ systemctl status nfs-server.service
  ● nfs-server.service - NFS server and services
     Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; disabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Fri 2015-05-29 22:24:47 PDT; 22s ago
    Process: 3044 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS (code=exited, status=1/FAILURE)
    Process: 3040 ExecStartPre=/usr/sbin/exportfs -r (code=exited, status=0/SUCCESS)
   Main PID: 3044 (code=exited, status=1/FAILURE)
  
  May 29 22:24:47 localhost.sulfur systemd[1]: Starting NFS server and services...
  May 29 22:24:47 localhost.sulfur rpc.nfsd[3044]: rpc.nfsd: writing fd to kernel failed: errno 111 (Connection refused)
  May 29 22:24:47 localhost.sulfur rpc.nfsd[3044]: rpc.nfsd: unable to set any sockets for nfsd
  May 29 22:24:47 localhost.sulfur systemd[1]: nfs-server.service: main process exited, code=exited, status=1/FAILURE
  May 29 22:24:47 localhost.sulfur systemd[1]: Failed to start NFS server and services.
  May 29 22:24:47 localhost.sulfur systemd[1]: Unit nfs-server.service entered failed state.
  May 29 22:24:47 localhost.sulfur systemd[1]: nfs-server.service failed.
  </code></pre>
  
  <p>The journelctl -xe log has a ton of stuff in it so I won't post all of it here, but there are some things in the bold red.</p>
  
  <pre><code>May 29 22:24:47 localhost.sulfur rpc.mountd[3024]: Could not bind socket: (98) Address already in use
  May 29 22:24:47 localhost.sulfur rpc.mountd[3024]: Could not bind socket: (98) Address already in use
  May 29 22:24:47 localhost.sulfur rpc.statd[3028]: failed to create RPC listeners, exiting
  May 29 22:24:47 localhost.sulfur systemd[1]: Failed to start NFS status monitor for NFSv2/3 locking..
  </code></pre>
  
  <p>Before I ran vagrant up I looked to see if there were any process binding to port 98 with netstat -tulpn and did not see anything and in fact while vagrant is hanging I ran netstat -tulpn again to see what was binding to port 98 and didn't see anything. (checked for both current user and root)</p>
  
  <p><strong>UPDATE</strong>: Haven't gotten any responses.</p>
  
  <p>I wasn't able to figure out the current issue I'm having. I tried using lxc instead, but gets stuck on booting. I'd also prefer not to use VirtualBox, but the issue seems to lie within nfs not the hypervisor. Going to try using the rsync-auto feature Vagrant provides, but I'd prefer to get nfs working.</p>