Flapane, Thanks for the log. It shows the information I'm looking for, though I'm confused by exactly what it shows.
Nov 2 16:06:31 virtualbox kernel: [ 25.934277] init: network-interface (eth0) pre-start process (350) exited normally Nov 2 16:06:31 virtualbox kernel: [ 25.934627] init: network-interface (eth0) state changed from pre-start to spawned Nov 2 16:06:31 virtualbox kernel: [ 25.934884] init: network-interface (eth0) state changed from spawned to post-start Nov 2 16:06:31 virtualbox kernel: [ 25.935013] init: network-interface (eth0) state changed from post-start to running This, combined with your /etc/network/interfaces file, should be enough to cause the system to continue booting without the failsafe job. However, it's at least clear to me that you have a different issue than the one being addressed in this bug: your error is not a spurious message, but an actual timeout waiting for the network. Please open a new bug report against the ifupdown package, attaching the same files that you've included in this bug to date, and add a comment here with the bug number. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/881079 Title: "Waiting up to 60 more seconds for network configuration" at startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-common/+bug/881079/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
