Vagrant throwing timeout error

Vagrant
1

vagrant up
Bringing machine ‘default’ up with ‘virtualbox’ provider…
==> default: Importing base box ‘hashicorp/bionic64’…
==> default: Matching MAC address for NAT networking…
==> default: Checking if box ‘hashicorp/bionic64’ version ‘1.0.282’ is up to date…
==> default: Setting the name of the VM: test_default_1581336172268_28420
==> default: Clearing any previously set network interfaces…
==> default: Preparing network interfaces based on configuration…
default: Adapter 1: nat
default: Adapter 2: intnet
==> 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

2

As mentioned increasing the config.vm.boot_timeout parameter could help. Can you provide us the Vagrantfile?

3

Hey there -

When you bring up the vm with Vagrant, are you able to access it through the VirtualBox GUI? It’s possible the machine might not have enough resources to come up, and that’s’ why it’s timing out. If you can log into the machine through the GUI though, you might be able to see what’s going wrong…like checking to see if sshd is running and available, or if it has no networking at all.

4

-- mode: ruby --

vi: set ft=ruby :

All Vagrant configuration is done below. The “2” in Vagrant.configure

configures the configuration version (we support older styles for

backwards compatibility). Please don’t change it unless you know what

you’re doing.

Vagrant.configure(“2”) do |config|

The most common configuration options are documented and commented below.

For a complete reference, please see the online documentation at

https://docs.vagrantup.com.

Every Vagrant development environment requires a box. You can search for

boxes at https://vagrantcloud.com/search.

config.vm.box = “hashicorp/bionic64”

Disable automatic box update checking. If you disable this, then

boxes will only be checked for updates when the user runs

vagrant box outdated. This is not recommended.

config.vm.box_check_update = false

Create a forwarded port mapping which allows access to a specific port

within the machine from a port on the host machine. In the example below,

accessing “localhost:8080” will access port 80 on the guest machine.

NOTE: This will enable public access to the opened port

config.vm.network “forwarded_port”, guest: 80, host: 8080

Create a forwarded port mapping which allows access to a specific port

within the machine from a port on the host machine and only allow access

via 127.0.0.1 to disable public access

config.vm.network “forwarded_port”, guest: 80, host: 8080, host_ip: “127.0.0.1”

Create a private network, which allows host-only access to the machine

using a specific IP.

config.vm.network “private_network”, ip: “192.168.33.10”

config.vm.network “private_network”, ip: “192.168.50.4”,
virtualbox__intnet: true

Create a public network, which generally matched to bridged network.

Bridged networks make the machine appear as another physical device on

your network.

config.vm.network “public_network”

Share an additional folder to the guest VM. The first argument is

the path on the host to the actual folder. The second argument is

the path on the guest to mount the folder. And the optional third

argument is a set of non-required options.

config.vm.synced_folder “…/data”, “/vagrant_data”

Provider-specific configuration so you can fine-tune various

backing providers for Vagrant. These expose provider-specific options.

Example for VirtualBox:

config.vm.provider “virtualbox” do |vb|

# Display the VirtualBox GUI when booting the machine

vb.gui = true

# Customize the amount of memory on the VM:

vb.memory = “1024”

end

View the documentation for the provider you are using for more

information on available options.

Enable provisioning with a shell script. Additional provisioners such as

Ansible, Chef, Docker, Puppet and Salt are also available. Please see the

documentation for more information about their specific syntax and use.

config.vm.provision “shell”, inline: <<-SHELL

apt-get update

apt-get install -y apache2

SHELL

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

5 
Vagrant.configure("2") do |config|
    config.vm.box = "hashicorp/bionic64"
    config.vm.network "private_network", ip: "192.168.33.10"
    config.vm.network "private_network", ip: "192.168.50.4",
    virtualbox__intnet: true
    config.vm.network "public_network"
    config.vm.synced_folder "../data", "/vagrant_data"
    config.vm.provider "virtualbox" do |vb|
    vb.gui = true
    vb.memory = "1024"
end

config.vm.provision "shell", inline: <<-SHELL
apt-get update
apt-get install -y apache2
SHELL
config.vm.provider :virtualbox do |vb|
vb.gui = true
end
end

Just formatted the Vagrantfile. Actually testing.

6

It’s working on my machine. :confused:

7

@rahulkumartandf - If you could, please try the suggestions below as I believe they will get you closer to solving why your machine is failing to bring up that Vagrant box. Thanks.