(Apologies if this is a repost, but my original post to Google Groups two days ago seems to not have appeared here.)
I've got a misbehaving Vagrant box that takes forever to boot, and I'd like to be able to diagnose the reason. vb.gui = True doesn't help. After the kernel part of booting is finished, the screen is not updated before the login prompt finally appears. vagrant up with debug mode is extremely verbose, yet seems to indicate nothing more than the fact that SSH isn't ready just yet. Is there some way I could actually see what messages are printed during service startup? Failing that, any way to see after the fact any messages printed or timeouts hit during that period? Googling for slow vagrant boots provides plenty of results, but there are seemingly endless different workarounds with inconsistent success rates. I'd like to narrow the possibilities before blindly trying dozens of different combinations. Vagrant is 1.4.3. Virtualbox is at 4.3.7r91560. (The issue has been present with older versions of each, too.) The box is running 64-bit Ubuntu 13.10, the default cloud image off vagrantbox.es. The guest additions are up-to-date (I use vagrant-vbguest for that). - JK Laiho -- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
