Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Windows: timeout when starting ubuntu-16.04 #719

Closed
ferrarimarco opened this issue Nov 17, 2016 · 5 comments
Closed

Windows: timeout when starting ubuntu-16.04 #719

ferrarimarco opened this issue Nov 17, 2016 · 5 comments

Comments

@ferrarimarco
Copy link

Hi everyone.

I get a timeout when starting an ubuntu 16.04 box.

Specs:

  • OS: Windows 7 x64
  • Vagrant: 1.8.6
  • Virtualbox: 5.1.8

I deleted all the boxes I had in my Vagrant setup just to be sure to start fresh.

Here is a log of the command line: Vagrant cmd

After enabling the GUI, I see that the box starts in Emergency mode, see my screenshot:

image

At first it seemed related to #688 but it's not the case (the cable set as "connected" in Virtualbox).

Thanks

@ferrarimarco ferrarimarco changed the title Timeout when starting ubuntu-16.04 version 2.3.0 Timeout when starting ubuntu-16.04 Nov 17, 2016
@cheeseplus cheeseplus changed the title Timeout when starting ubuntu-16.04 Windows: timeout when starting ubuntu-16.04 Nov 18, 2016
@ferrarimarco
Copy link
Author

Pressing CTRL-D boots into default mode. If you do this while Vagrant is trying to connect, it works.

@cheeseplus
Copy link
Contributor

Has this been resolved by Vagrant 1.9.x? I seem to remember a linkage between these builds and this issue.

@ferrarimarco
Copy link
Author

@cheeseplus I'll try and let you know.

@ferrarimarco
Copy link
Author

@cheeseplus I tried with the latest Vagrant and I am not able to reproduce the issue anymore. Is there anything in the Vagrant changelog that makes you think this is solved? If so maybe this can be closed.

@cheeseplus
Copy link
Contributor

There are several fixes regarding network as well as Windows (some subprocess fixes among other things) so pretty confident this was ironed out between 1.8.7-1.9.1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants