kernel-packages team mailing list archive

[Rune Philosof <launchpad.net@xxxxxxxxxxx>]

Public bug reported:

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.

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.

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?

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: Incomplete

-- 
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, the entire guest OS will be unusable. 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.

  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?

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