Timed out while waiting for the machine to boot when vagrant up [closed]

Question 1

I increase the time using config.vm.boot_timeout. But for me it was not the reason although the error tells about a timeout.

I opened the Vagrantfile using vim and add the following lines which turns on GUI for the VM.

config.vm.provider :virtualbox do |vb|
  vb.gui = true
end

After re-running the vagrant up i saw the real reason in the GUI. There was an error dialog and it keeps waiting. That was the reason for the connection timeout.

To fix this i had to do some configurations in the system BIOS. I had to turn on the intel VT-x setting. And please check for AMD-V setting as well. These settings help hardware virtualization.

Question 2

Select your Ubuntu server, click on Settings, go to Network tab and make sure that your Cable Connected option is selected.

Question 3

I used "vagrant destroy" and solved the problem.

This command stops the running machine Vagrant is managing and destroys all resources that were created during the machine creation process. After running this command, your computer should be left at a clean state, as if you never created the guest machine in the first place.

Question 4

I had the same problem on windows 10 and the solution for me was to enable Intel Virtualization.

I'm afraid I can't give you specific instructions, as far as the BIOS menu options vary from computer to computer depending on the manufacturer. However, generally you should follow these steps:

1-Power on the machine and open the BIOS.

2- Open the Processor submenu. The processor settings menu may be hidden in the Chipset, Advanced CPU Configuration or Northbridge.

3-Enable Intel Virtualization Technology (also known as Intel VT) or AMD-V depending on the brand of the processor.

4- Save the changes and restart.

Question 5

You need to able the GUI. Remove the comment of this lines in your Vagrant file:

config.vm.provider :virtualbox do |vb|
  vb.gui = true
end

After you need shutdown your machine and start again:

vagrant halt
vagrant up

Question 6

I was also getting error message Timed out while waiting for the machine to boot. After enabling the GUI through vagrant file, I could see that vagrant tp was asking for login & password. providing vagrant/vagrant worked but the machine was still not up.

Finally, Vagrant destroy worked. After this vagrant up provisioned machine & now I could do ssh.

Question 7

I know this is an old thread, but I recently ran into this same issue with an Ubuntu vagrant box (19.04) and wanted to post the solution that worked for me.

The key part was the number of cpus. The box had been trying to boot with 2 enabled and that was absolutely killing the performance during boot, so much so that vagrant would time out waiting.

By setting it to 1 my box came up immediately on vagrant up!

In your Vagrantfile under the config.vm.provider "virtualbox" do |v| section try adding v.cpus = 1 and see if that helps.

Hope this helps someone else having a similar issue.

Question 8

You probably enabled firewall which is causing the problem. Just add

config.vm.provider :virtualbox do |vb|
  vb.gui = true
end

to your VagrantFile then vagrant up. Login wth vagrant credentials on the gui window and disable the firewall with sudo ufw disable.

Restart vagrant and everything should be fine.

vagrant halt
vagrant up

Question 9

I had tried everything but didn't work for me any solution. Then i had found this solution on github. Check the solution.

Option 1:

Restart and keep pressing F10 to open BIOS settings.
Open Advanced CPU Configuration. (Try to find Virtualization technology settings.)
Enable Intel Virtualization Technology (also known as Intel VT) depending on the brand.
Save the changes and restart.

Option 2:

Open up the command prompt of your windows. You should open terminal or command prompt as an administrator and then then type:
```
bcdedit /set hypervisorlaunchtype off
```
Restart your computer.

find more details from this blog

Question 10

I had the same issue on a Windows 10

 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.

And this solution worked for me :

Open up the command prompt of your windows as an administrator and run :

 bcdedit /set hypervisorlaunchtype off

Restart your computer.

Question 11

just enable virtualization technology of cpu setting in BIOS

Question 12

Just paste this code in your variant file and it will work fine.

config.vm.boot_timeout = "1440"

After saving changes, enter the vagrant provision command to update changes Then run vagrant ssh to start a homestead

Question 13

Edit config.vm and increase the value of config.vm.boot_timeout to your needs.

Question 14

Prerequisite: Please Make sure your virtualization is enabled.

I had the same problem in my windows 10 system and I researched a lot about the issue in both StackOverflow and GitHub issues but nothing worked. So I simply updated my virtual box to the latest version and rebooted the system. Afterwards, it worked absolutely fine for me :)

Question 15

Potential Issue: Virtualization might be disabled in your bios

Restart your computer and keep hitting F10 key. This will take you into the system BIOS. There you can check if your Intel-Virtualization is disabled. If so, change it to Enabled, save and continue to restart your pc.

Question 16

Few things you can try:

Check the Vagrant version (vagrant -v) you are running and it should be latest. Also run vagrant box update.
Increase config.vm.boot_timeout value in Vagrantfile.
Add vb.gui = true after config.vm.provider :virtualbox do |vb| line in Vagrantfile to open VM with GUI. Try reload, and see what is the exact error at which it is getting stuck and try fixing that. Also click on Settings, go to Network tab and make sure that your Cable Connected option is selected.
Once GUI is enabled try reloading and once the login screen is up, you can login with the username vagrant and the password is the same as the username. You need to open up /etc/default/grub. Add the following to the bottom of the file and save the file: GRUB_RECORDFAIL_TIMEOUT=2. Run sudo update-grub. Shutdown the VM and run vagrant up.

Question 17

What worked for me is vagrant destroy and then vagrant up The drawback is it deletes all the database and you need to run your migrations again.