Comment 2 for bug 1615579

I can't reproduce this on either of my Ubuntu machines, both of which are running the same version of Vagrant and the Linux kernel.

What happens if you run 'vagrant box update' in the same directory as the Vagrantfile? It could be that you are running an older box which doesn't have this issue fixed (the official Vagrant boxes are updated every few days).

For reference, the commands I ran were:

cd /tmp
vagrant init ubuntu/xenial64
vagrant up

I didn't have the ubuntu/xenial64 box installed, so it fetched the latest version automatically the first time I ran vagrant up.