kernel-packages team mailing list archive

[Rune Philosof <launchpad.net@xxxxxxxxxxx>]

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


** Description changed:

  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,
- the entire guest OS will be unusable. This does not happen when using
- the normal virtualbox shared folders.
+ every process that tried to access the nfs share will hang. This does
+ not happen when using the normal virtualbox shared folders.
  
- It's not only the nfs shared folder that is unusable, the entire OS is
- hanging. Even syslog does not seem to see much action. This is syslog on
- the guest, from waking up until vagrant halt is completed.
+ 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.
- 
- When I try to ssh to the guest system I the motd and last login: ..., but nothing more, it just hangs.
- If I was already logged in the guest system through ssh then that session is unresponsive (after pressing enter).
- 
- How can this be fixed?
- How should I debug it?

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1564807

Title:
  nfs causes guest system to get stuck

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1564807/+subscriptions