[vagrant-up] vagrant up fails with ssh-key timeout issue

Denislav Denov

2018-10-02 06:49:51 UTC

Hello,

It is probable that the specific box that you choose has a problem since it
seems to fail on booting and not on the SSH settings.

In order to test if vagrant works correctly please test with our box:

- mkdir p64
- cd p64
- vagrant init -m hashicorp/precise64
- vagrant up

If there is no issue booting up and vagrant ssh into our testing box, then
we can assume that issue is in the centos box that you are using.

You can either build your own box using Packer, or try any of the Bento
boxes that would be suitable for your case - https://app.vagrantup.com/bento

Best regards,

Denislav.

Post by Bubunia Patra
Hi all,
I am trying to set up vagrant in centos-7 following the instruction given
as "https://www.tecmint.com/how-to-install-vagrant-on-centos-7/".
https://stackoverflow.com/questions/23293071/timed-out-while-waiting-for-the-machine-to-boot-when-vagrant-up.
I could not get a solution from the thread? Can anyone help me in this
regard?
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'centos/7' is up to date...
==> 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.
Regards
Pradeep

--
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 vagrant-up+***@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/82263ee3-84e4-46d0-8351-f6f15705d08a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.