Vagrant/Virtualbox fails on looking for network devices most of the time, and when it does actually boot it takes at least 15 minutes to do so.

CodeLyfe

unread,

Dec 10, 2017, 11:52:53 PM12/10/17

to Vagrant

My host is Windows 10 Home. (Fall Creators Update)

When I run the `vagrant up` command I either can't get vagrant to boot into the machine or if it does eventually succeed and boot it takes 15 minutes or more to do so.

What can I do to fix this and have Vagrant & Virtualbox working together properly.

Virtualbox version: 5.2.2

Vagrant version: 2.0.1

My box is just an Ubuntu 14.04 box for Ruby on Rails development. It works fine on other systems, (Mac, Linux).

So far I've tried disabling the Firewall as well as disabling & enabling the Virtualbox Host-Only adapter.

I have set vgui = true so I can see what is going on inside the VM.

In the VM it tries to find the network device, then retries again after 10 seconds, then again after 120 seconds. Then it "gave up" looking for the network device and runs an init. The network device appears immediately after the init. Then it spends about 5 minutes configuring the network interfaces. When it completed it booted into Ubuntu with a login prompt.

Once the login prompt is shown, Vagrant stops retrying and shows Machine booted and ready. It then took another 10 minutes configuring and enabling network interfaces, then finally mounts the shared folder and gives me a command prompt.

When it fails I get what you see below.

Any help will be greatly appreciated!

This is what I get when I run `vagrant up`:

λ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'dev_box'...
==> default: Matching MAC address for NAT networking...
==> default: Setting the name of the VM: Dev_default_1512943736797_96012
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    default: Adapter 2: bridged
==> default: Forwarding ports...
    default: 3000 (guest) => 3000 (host) (adapter 1)
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> 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
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'unknown' state. Please verify everything is configured
properly and try again.

If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.

The primary issue for this error is that the provider you're using
is not properly configured. This is very rarely a Vagrant issue.

Alvaro Miranda Aguilera

unread,

Dec 11, 2017, 12:39:58 PM12/11/17

to vagra...@googlegroups.com

try a different box.

hashicorp/precise64

do yo have that private key?

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.

GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/eea05fbb-4678-46c8-adc8-b7a83bb24b21%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Alvaro

CodeLyfe

unread,

Dec 11, 2017, 2:54:09 PM12/11/17

to Vagrant

It's not the box. The box works fine on my Linux and Mac systems.

To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/eea05fbb-4678-46c8-adc8-b7a83bb24b21%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--
Alvaro

CodeLyfe

unread,

Dec 11, 2017, 5:08:33 PM12/11/17

to Vagrant

I got it working. Not sure if it's one of the new Windows security "features" or what, but when I updated to the Fall Creators Update, Windows Firewall is now blocking ports that were previously open on my computer.

To get Vagrant working properly again I created a rule to allow TCP connections on port 22. It works fine now.

Reply all

Reply to author

Forward