Vagrant up timeout

Question

Having some issues to get my vagrant up, Got the box, run vagrant init and after vagrant up command I get this message.

Bringing m         


        

Answer 1

For me, enabling virtualization option from BIOS fixed it.

Answer 2

A solution is gracefully described here. It was the only one that worked for me on a i686 with Ubuntu 16.04.2, Vagrant 1.9.3 and Virtualbox 5.1.18 trying to run a ubuntu/trusty32.

What you do is fix the networking on the server and add some extra time for the boot:

• start the VM, log in to the server via GUI (username: vagrant, password: vagrant) and run the following commands

  $ sudo ifdown eth0
  $ sudo ifup eth0
  

• then add the following to the file /etc/rc.local

  ifdown eth0
  ifup eth0
  

• on the host, add the following to the Vagrantfile

  config.vm.boot_timeout = 600
  

Now stop the VM. Next time you do a 'vagrant up' it will be OK.

Answer 3

config.vm.boot_timeout didn't help me even after setting up-to maximum!!!

The real problem in my case was, it was unable to create the network adapter. I have to explicitly edit the box.ovf file in order to enable it.

Locate the box.ovf file & open it in an text editor, then add cable="true" as shown in below, after that save and exit. Post that destroy your vagrant using vagrant destroy and then bring it up.

Locate(box.ovf): C:\Users\<use_name>\.vagrant.d\boxes\box-cutter-VAGRANTSLASH-centos68-desktop\2.0.21\virtualbox\box.ovf

Before: <Adapter slot="0" enabled="true" MACAddress="084017AA8CEB" type="virtio">

After: <Adapter slot="0" enabled="true" MACAddress="084017AA8CEB" cable="true" type="virtio">

There is a nice thread here

Answer 4

Upgrade VirtualBox to 5.1.12

I had the same problem using:

• VirtualBox 5.0.0
• Vagrant 1.9.1 (vagrant -v)
• Test Kitchen 1.14.2 (kitchen -v)
• centos-7.2

when I was trying to run the following commands:

kitchen create

and

kitchen test

Upgrading Oracle VirtualBox (download + install) to VirtualBox 5.1.12 fixed the problem.

---

If the upgrade is not a solution for you, you can use the following workaround mentioned by @paulalexandru, but it has the following main disadvantage: you need to make that manual step for every command that you are running.

---

But it seems that VirtualBox fixed the "Cable Connected" option problem. Now, if you go to Settings > Network > Adapter 1 > Advanced, you can see that the Cable Connected check box is checked by default:

Answer 5

This is the same problem that occurred to me. At last we found out that this problem is due to the Linux OS that we are using with Vagrant version is not compatible. So, we took the latest version (i.e. v1.6.3) of Vagrant and updated our OS to point to agent.vm.box_url = "http://developer.nrel.gov/downloads/vagrant-boxes/CentOS-6.4-i386-v20131103.box"

Vagrant version 4.3.8 was not working with the below OS. agent.vm.box_url = "http://developer.nrel.gov/downloads/vagrant-boxes/CentOS-6.4-x86_64-v20130731.box".

We exactly got the same issue that shown above.

Answer 6

I am using Windows 10.

I solved this problem by following the steps in the note

"If you are using Windows, you may need to enable hardware virtualization (VT-x). It can usually be enabled via your BIOS. If you are using Hyper-V on a UEFI system you may additionally need to disable Hyper-V in order to access VT-x."