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

Ensure Virtualbox connect the LAN cable #382

Closed
wants to merge 1 commit into from

Conversation

JulienTant
Copy link
Contributor

Somehow, Some friends and I are unable to create a working homestead with Virtualbox with just a vagrant up, because the LAN adapter has it's cable "disconnected" in VB settings. So we have to vagrant up to initialize our box, vagrant halt to shut it down, then go to VB settings to force the cable connection, and finally vagrant up to make it work.

This simple line ensure that the cable will be connected in VB and solves our problem.

Somehow, Some friends and I are unable to create a working homestead with Virtualbox with just a `vagrant up`, because the LAN adapter has it's cable "disconnected" in VB settings. So we have to `vagrant up` to initialize our box, `vagrant halt` to shut it down, then go to VB settings to force the cable connection, and finally `vagrant up` to make it work. 

This simple line ensure that the cable will be connected in VB and solves our problem.
@svpernova09
Copy link
Contributor

Thanks for the PR, can you please fill out a new issue so I can verify the bug: https://github.com/laravel/homestead/issues/new

@JulienTant
Copy link
Contributor Author

Sure

@svpernova09
Copy link
Contributor

Closing pending any further logs showing current version of Homestead and Virtualbox is still causing the error #383

@ralf57
Copy link

ralf57 commented Feb 6, 2017

@svpernova09 I had the same issue and, for several reasons, I can't update to VirtualBox 5.1.
I think this little PR should be merged since it benefits those who cannot be on the latest VBox

@svpernova09
Copy link
Contributor

@ralf57 I'm sorry you're stuck on Virtualbox 5.0, but it just isn't feasible for us to continue to support that version due to too many issues with 5.0 and Vagrant 1.8.x+ and several base boxes (not only the ones we use and create)

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

Successfully merging this pull request may close these issues.

None yet

3 participants