Hello, Please test with these boxes first:
hashicorp/precise32 hashicorp/precise64 you can do something like this: mkdir precise32 cd precise32 vagrant init -m hashicorp/precise32 vagrant up That will help to identify where the error is comming from. Alvaro. On Mon, May 9, 2016 at 4:53 PM, Rohit Kohli <[email protected]> wrote: > Hi, > > 'vagrant up' on my windows 7 machine is failing with following message: > ================= > C:\HashiCorp\Vagrant\bin>vagrant up > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Clearing any previously set forwarded ports... > ==> default: Clearing any previously set network interfaces... > ==> default: Preparing network interfaces based on configuration... > default: Adapter 1: nat > ==> default: Forwarding ports... > default: 22 (guest) => 2222 (host) (adapter 1) > ==> default: Booting VM... > ==> default: Waiting for machine to boot. This may take a few minutes... > default: SSH address: 127.0.0.1:2222 > default: SSH username: vagrant > default: SSH auth method: private key > Timed out while waiting for the machine to boot. This means that > Vagrant was unable to communicate with the guest machine within > the configured ("config.vm.boot_timeout" value) time period. > > If you look above, you should be able to see the error(s) that > Vagrant had when attempting to connect to the machine. These errors > are usually good hints as to what may be wrong. > > If you're using a custom box, make sure that networking is properly > working and you're able to connect to the machine. It is a common > problem that networking isn't setup properly in these boxes. > Verify that authentication configurations are also setup properly, > as well. > > If the box appears to be booting properly, you may want to increase > the timeout ("config.vm.boot_timeout") value. > ================= > > I have tried- > 1) Checking and making sure support for virtualization is enabled at BIOS > level. > 2) Uninstalling and Installing Virtualbox and Vagrant again. > > but the issue still remains. > > Any pointers toward the possible reason or suggestions would be > appreciated. > > -- > 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/254807de-097c-4518-9bf1-aec56ab8a8d7%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/254807de-097c-4518-9bf1-aec56ab8a8d7%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CAHqq0ewq7R0OZPRUnGOvzLUbMW_0sNVWrr0dcBt9--OuYPe8ig%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
