nfs causes guest system to get stuck

[Rune Philosof]

Host OS Ubuntu 15.10
Guest OS Ubuntu 14.10

Using Vagrant with nfs and Virtualbox and static ip on the private network.

It is working perfectly except that after having suspended the host OS, every process that tried to access the nfs share will hang. This does not happen when using the normal virtualbox shared folders.

This is syslog on the guest, from waking up until vagrant halt --force is completed.

Feb 26 07:15:33 vagrant kernel: [ 8375.252989] e1000: eth1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
Feb 26 07:16:11 vagrant kernel: [ 8413.109832] nfs: server 192.168.33.1 not responding, still trying
Feb 26 07:16:38 vagrant kernel: [ 8440.687476] nfs: server 192.168.33.1 not responding, still trying
Feb 26 07:17:01 vagrant CRON[3776]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Feb 26 07:20:33 vagrant rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="753" x-info="http://www.rsyslog.com"] exiting on signal 15.
---
AlsaDevices:
 total 0
 crw-rw---- 1 root audio 116, 1 Apr 15 09:07 seq
 crw-rw---- 1 root audio 116, 33 Apr 15 09:07 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
IwConfig: Error: [Errno 2] No such file or directory
Lsusb: Error: command ['lsusb'] failed with exit code 1: unable to initialize libusb: -99
MachineType: innotek GmbH VirtualBox
Package: linux (not installed)
PciMultimedia:

ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-85-generic root=UUID=6872cb1e-3766-4ff3-9de5-11ffd99c3fc9 ro console=tty1 console=ttyS0
ProcVersionSignature: Ubuntu 3.13.0-85.129-generic 3.13.11-ckt36
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-85-generic N/A
 linux-backports-modules-3.13.0-85-generic N/A
 linux-firmware N/A
RfKill: Error: [Errno 2] No such file or directory
Tags: trusty uec-images
Uname: Linux 3.13.0-85-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

WifiSyslog:

_MarkForUpload: True
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1564807

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Joseph Salisbury (jsalisbury)]

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.6 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.6-rc1-wily/

[Rune Philosof (olberd)]

I have tested these versions:
linux-image-3.19.0-56-generic
linux-image-3.16.0-67-generic
linux-image-3.13.0-85-generic

The initial report is wrong.
It does not make the entire guest OS hang, only processes that touch the nfs mount hangs (like ls /vagrant).
It can easily be recreated with this Vagrantfile:
Vagrant.configure(2) do |config|
  config.vm.box = "ubuntu/trusty64"
  config.vm.network "private_network", ip: "192.168.33.10"
  config.vm.synced_folder ".", "/vagrant", type: "nfs"
end

1. vagrant up
2. vagrant ssh # ls /vagrant works
3. suspend the host machine
4. resume the host machine
5. in the vagrant ssh terminal ls /vagrant hangs

At least one other (the commenter) has the problem: http://stackoverflow.com/questions/35645041/after-suspend-guest-os-hangs-when-using-vagrant-with-nfs

[Rune Philosof (olberd)]

suspending and resuming the guest os does not trigger this problem.
Only when doing it for the host os.

[Rune Philosof (olberd)]

apport information

[Rune Philosof (olberd)]

apport information

[Rune Philosof (olberd)]

apport information

[Rune Philosof (olberd)]

apport information

[Rune Philosof (olberd)]

apport information

[Rune Philosof (olberd)]

apport information

[Rune Philosof (olberd)]

apport information

[Rune Philosof (olberd)]

apport information