Hello, Once the VM has been created, can you open Virtualbox gui, stop the VM and start it fromt here?
Hopefully the console of Virtualbox should tell more information on whats going on. Alvaro. On Mon, May 9, 2016 at 5:57 PM, Rohit Kohli <[email protected]> wrote: > Thanks for helping out Alvaro > > So I tried with both precise32 and precise64 boxes, however for both, same > problem appears while running 'vagrant up'. > While trying to for precise64, following was thrown: > ====================== > C:\HashiCorp\Vagrant\bin\precise64>vagrant up > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Box 'hashicorp/precise64' could not be found. Attempting to > find an > d install... > default: Box Provider: virtualbox > default: Box Version: >= 0 > ==> default: Loading metadata for box 'hashicorp/precise64' > default: URL: https://atlas.hashicorp.com/hashicorp/precise64 > ==> default: Adding box 'hashicorp/precise64' (v1.1.0) for provider: > virtualbox > default: Downloading: > https://atlas.hashicorp.com/hashicorp/boxes/precise64/ > versions/1.1.0/providers/virtualbox.box > default: Progress: 100% (Rate: 6155k/s, Estimated time remaining: > --:--:--) > ==> default: Successfully added box 'hashicorp/precise64' (v1.1.0) for > 'virtualb > ox'! > ==> default: Importing base box 'hashicorp/precise64'... > ==> default: Matching MAC address for NAT networking... > ==> default: Checking if box 'hashicorp/precise64' is up to date... > ==> default: Setting the name of the VM: > precise64_default_1462772511405_18359 > ==> default: Fixed port collision for 22 => 2222. Now on port 2201. > ==> default: Clearing any previously set network interfaces... > ==> default: Preparing network interfaces based on configuration... > default: Adapter 1: nat > ==> default: Forwarding ports... > default: 22 (guest) => 2201 (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:2201 > 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. > > C:\HashiCorp\Vagrant\bin\precise64>vagrant box list > hashicorp/precise32 (virtualbox, 1.0.0) > hashicorp/precise64 (virtualbox, 1.1.0) > ====================== > > On Monday, May 9, 2016 at 10:46:21 AM UTC+5:30, Alvaro Miranda Aguilera > wrote: >> >> 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/d9999062-e109-4b13-88e1-a627dbf52649%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/d9999062-e109-4b13-88e1-a627dbf52649%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/CAHqq0eyTbH1pMKNVRPzBBycSNC4xbdQfwETxCOSonO40v-UkPw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
