My first guess is that you are running into a "nested VM" problem, but whatever the problem is, your next step towards debugging it is to look at virtualbox and determine what it thinks the status of the VM is. If you're in a situation where you can display the console of the guest VM while it boots, that might show you something useful.
What vagrant can tell us is necessarily limited. You need to determine whether the guest VM is successfully created and booting and whether, once it boots, it reaches a level where it can communicate over the network, then, finally, whether there may be some firewall or misconfiguration that is preventing the ssh attempt from succeeding. -- jmcg -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/2eae1054-8c60-4f40-93f8-4d5625ea403f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
