Infrastructure vm timeout issue

C:\Users\chris\Desktop\m310-vagrant-env>vagrant up
Bringing machine ‘database’ up with ‘virtualbox’ provider…
Bringing machine ‘infrastructure’ up with ‘virtualbox’ provider…
==> database: Checking if box ‘ubuntu/trusty64’ version ‘20190429.0.1’ is up to date…
==> database: Machine already provisioned. Run vagrant provision or use the --provision
==> database: flag to force provisioning. Provisioners marked to run always will still run.
==> infrastructure: Checking if box ‘centos/7’ version ‘1905.1’ is up to date…
==> infrastructure: Clearing any previously set forwarded ports…
==> infrastructure: Fixed port collision for 22 => 2222. Now on port 2200.
==> infrastructure: Clearing any previously set network interfaces…
==> infrastructure: Preparing network interfaces based on configuration…
infrastructure: Adapter 1: nat
infrastructure: Adapter 2: hostonly
==> infrastructure: Forwarding ports…
infrastructure: 22 (guest) => 2200 (host) (adapter 1)
==> infrastructure: Running ‘pre-boot’ VM customizations…
==> infrastructure: Booting VM…
==> infrastructure: Waiting for machine to boot. This may take a few minutes…
infrastructure: SSH address: 127.0.0.1:2200
infrastructure: SSH username: vagrant
infrastructure: 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.

It seems like the infrastructure vm is unable to boot properly, what can I do?

Hey @Chris_09844

Do you have Intel Virtualization enabled through BIOS?

Do you have the most recent version of Virtual Box installed?

Yes, virtualisation enabled and most recent virtualbox installed.

when i look at the virtualbox console, the infrastructure vm gives a kernel panic - not syncing (fatal exception) .

@Chris_09844

Perhaps try to start over

vagrant destroy
vagrant up --provision

Let me know

I have successfully installed both the database and infrastructure virtual machines. My database vm can read docs from the shared folder, but the infrastructure vm won’t recognize documents in the shared folder.

When I run ‘varant reload infrastructure’ I get an error message that reads as follows:

mount -t vboxsf -o uid=id -u vagrant,gid=getent group vagrant | cut -d: -f3 home_vagrant_shared /home/vagrant/shared
mount -t vboxsf -o uid=id -u vagrant,gid=id -g vagrant home_vagrant_shared /home/vagrant/shared

The error output from the last command was:

mount: unknown filesystem type ‘vboxsf’

What am I doing wrong?

@Brandon_48087, try from Virtual Box:

1 Like