NFS not detected, though present (Linux)

[simbaho...@gmail.com]

Hi,

I'm a complete noob to Vagrant - someone sent me some instructions to get Vagrant running so that I could reproduce an error he was having on his development site.

My environment: Fedora 16 / VirtualBox-4.2-4.2.12_84980_fedora16-1.x86_64 / Vagrant 1.2.27

I run "vagrant up" and get:

Bringing machine 'default' up with 'virtualbox' provider...

[default] Box 'raring-1304' was not found. Fetching box from specified URL for

the provider 'virtualbox'. Note that if the URL does not have

a box for this provider, you should interrupt Vagrant now and add

the box yourself. Otherwise Vagrant will attempt to download the

full box prior to discovering this error.

Downloading or copying the box...

Extracting box...te: 1545k/s, Estimated time remaining: 0:00:01)

Successfully added box 'raring-1304' with provider 'virtualbox'!

There are errors in the configuration of this machine. Please fix

the following errors and try again:

vm:

* It appears your machine doesn't support NFS, or there is not an

adapter to enable NFS on this machine for Vagrant. Please verify

that `nfsd` is installed on your machine, and try again. If you're

on Windows, NFS isn't supported. If the problem persists, please

contact Vagrant support.

I do have the operating system's nfsd - it's at /usr/sbin/rpc.nfsd. As a stab in the dark, I symlinked it (/usr/sbin/nfsd), but that made no difference.

Any ideas? I did some Googling, but hardly knew what to look for, and got nowhere.

Thank you!

David

[Adrian Simmons]

nfs requires an nfs server on the host – it looks like you have that installed, but is it turned on? I've no idea what fedora uses to enable services...try "service nfs start" as root, or using sudo, whatever fedora uses. Then run vagrant again.

[Todd Lyons]

Having just worked through a similar issue on CentOS, which is very similar to Fedora, I have a couple of points for you to look into:
1) vagrant on the host machine needs sudo access so that it can edit /etc/exports and restart the nfs system with those changes. [1]
2) RH derivatives typically have a firewall installed by default. Make sure the firewall isn't blocking traffic on the vboxnet interfaces. [2]
3) make sure that the client has all of the necessary services started up for an nfs mount to work. Most boxes that you can download will have everything pre-configured.

...Todd

[1] Appearance when vagrant does the nfs changes:
[farm@mail ~/vagrant/FreeBSD_9.1_64_zfs]$ vagrant up

Bringing machine 'default' up with 'virtualbox' provider...

[default] Importing base box 'FreeBSD_9.1_64_zfs'...
[default] Matching MAC address for NAT networking...
[default] Setting the name of the VM...
[default] Clearing any previously set forwarded ports...
[default] Creating shared folders metadata...
[default] Clearing any previously set network interfaces...
[default] Preparing network interfaces based on configuration...
[default] Forwarding ports...
[default] -- 22 => 2222 (adapter 1)
[default] Running 'pre-boot' VM customizations...
[default] Booting VM...
[default] Waiting for VM to boot. This can take a few minutes.
[default] VM booted and ready for use!
[default] Configuring and enabling network interfaces...
[default] Mounting shared folders...
[default] Exporting NFS shared folders...
Preparing to edit /etc/exports. Administrator privileges will be required...
Shutting down NFS daemon:                                  [  OK  ]
Shutting down NFS mountd:                                  [  OK  ]
Shutting down NFS services:                                [  OK  ]
Starting NFS services:                                     [  OK  ]
Starting NFS mountd:                                       [  OK  ]
Stopping RPC idmapd:                                       [  OK  ]
Starting RPC idmapd:                                       [  OK  ]
Starting NFS daemon:                                       [  OK  ]
[default] Mounting NFS shared folders...

[farm@mail ~/vagrant/FreeBSD_9.1_64_zfs]$ grep -E '33.33.33|virtio' Vagrantfile
  config.vm.network :private_network, ip: "33.33.33.10"
    vb.customize ["modifyvm", :id, "--nictype1", "virtio"]
    vb.customize ["modifyvm", :id, "--nictype2", "virtio"]

[farm@mail ~/vagrant/FreeBSD_9.1_64_zfs]$ more /etc/exports
# VAGRANT-BEGIN: 7c22411f-fff1-4946-9852-ab81694304eb
/home/farm/vagrant/FreeBSD_9.1_64_zfs 33.33.33.10(rw,no_subtree_check,all_squash,anonuid=5
02,anongid=48,fsid=3398699527)
# VAGRANT-END: 7c22411f-fff1-4946-9852-ab81694304eb

[farm@mail ~/vagrant/FreeBSD_9.1_64_zfs]$  ip addr show dev vboxnet0
6: vboxnet0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether 0a:00:27:00:00:00 brd ff:ff:ff:ff:ff:ff
    inet 33.33.33.1/24 brd 33.33.33.255 scope global vboxnet0
<snip>


[2] I added a rule to the default RedHat firewall chain named RH-Firewall-1-INPUT, located in /etc/sysconfig/iptables, which allows all connections on the vboxnet devices:
CentOS63[root@mail ~]$ grep vboxnet /etc/sysconfig/iptables
-A RH-Firewall-1-INPUT -i vboxnet+ -j ACCEPT

...Todd