vagrant up fails with ssh-key timeout issue

261 views
Skip to first unread message

Bubunia Patra

unread,
Sep 30, 2018, 4:38:19 PM9/30/18
to Vagrant
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/".


Error: 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?

vagrant up fails with below error:

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

Denislav Denov

unread,
Oct 2, 2018, 2:49:52 AM10/2/18
to Vagrant
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.
Reply all
Reply to author
Forward
0 new messages