#878825 vagrant: Does not detect that `nfs-kernel-server` is sufficient

Package:
vagrant
Source:
vagrant
Description:
Tool for building and distributing virtualized development environments
Submitter:
"Paul \"LeoNerd\" Evans"
Date:
2017-10-17 13:27:06 UTC
Severity:
normal
#878825#5
Date:
2017-10-16 22:29:29 UTC
From:
To:
When trying to start a machine using NFS, when I have
`nfs-kernel-server` installed and available, it complains that

  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.

This is fixed by installing `nfs-server` (the userland version) which
replaces `nfs-kernel-server`.

#878825#10
Date:
2017-10-17 12:35:21 UTC
From:
To:
Hi,

I don't have nfs-server installed and still vagrant works just fine for
me:

un  nfs-client                            <none>
ii  nfs-common                            1:1.3.4-2.1+b1
ii  nfs-kernel-server                     1:1.3.4-2.1+b1
un  nfs-server                            <none>

Looking at the source code, vagrant does the following to check if nfs
is installed:

    cat /proc/filesystems | grep nfsd

Can you try to reproduce the issue by reinstalling nfs-kernel-server? Or
trying on a clean system?

#878825#17
Date:
2017-10-17 13:13:20 UTC
From:
To:
Hm; yes I did see it was doing that. Though when I had just
`nfs-kernel-server` running, `nfsd` didn't appear in
`/proc/filesystems` but having swapped to the userland `nfs-server` it
then appeared there.

I'll try swapping back and see what happens.

The history here is that vagrant had been working, and then I rebooted
the machine after various updates, and found it no longer working. I
suspected a version change of something, but maybe in fact it's related
to that reboot after all.