Homestead: Virtualbox doesn't connect the network adapter cable

[JulienTant]

Vagrant version

Vagrant 1.9.0

Provider & Provider version

Virtualbox 5.0.30 ; Virtualbox 5.0.10 ; Virtualbox 5.1.2

Host operating system

Sierra ; Windows 10

Homestead.yaml

---
ip: "192.168.10.10"
memory: 2048
cpus: 1
hostname: reploc
name: reploc
provider: virtualbox

authorize: ~/.ssh/id_rsa.pub

keys:
    - ~/.ssh/id_rsa

folders:
    - map: "/Users/a/Sites/Reploc"
      to: "/home/vagrant/reploc"

sites:
    - map: homestead.app
      to: "/home/vagrant/reploc/public"

databases:
    - homestead

# blackfire:
#     - id: foo
#       token: bar
#       client-id: foo
#       client-token: bar

# ports:
#     - send: 50000
#       to: 5000
#     - send: 7777
#       to: 777
#       protocol: udp

Vagrant up output

https://gist.github.com/JulienTant/f81d9f9b2bafa76a784946400214314f

Expected behavior

Vagrant creates a virtualbox machine with a connected cable

Actual behavior

Vagrant creates a virtualbox machine with a disconnected cable

Steps to reproduce

1. vagrant destroy
2. vagrant up

Steps to fix manually

1. vagrant destroy
2. vagrant up
3. vagrant halt
4. Go to the VM VB settings to connect the cable manually
5. vagrant up

References

• https://github.com/mitchellh/vagrant/issues/7648
• Fix proposal : https://github.com/laravel/homestead/pull/382

[JulienTant]

This is not per say an homestead issue, but as you can see in the PR a single line will fix the problem.

[wesleyhf]

I had the same problem. I solved by updating Virtualbox and vagrant to latest version.

[svpernova09]

Please ensure each system is running Virtualbox 5.1.x. Also make sure you're using a recent version of Homestead (3.1 or newer).

If you upgrade Virtualbox and Homestead and still have issues, please post logs and please comment here and I'll reopen/investigate.

[sebastiaanluca]

This still proves to be an issue using Homestead 4.0.1, laravel/homestead 1.0.1 box, VirtualBox 5.0.30 (the latest as of today, 5.1.x is not out yet?), and vagrant 1.9.1 (also just updated). Times out while setting up network interfaces. New box and Homestead setup as of today.

I enabled "cable connected" in VirtualBox settings (while it was running) and it continued to boot after setting up the network interfaces. Is a vagrant of Homestead fix still pending to be released or is this an unsolved bug? Let me know how I can provide additional details.

Also see https://github.com/chef/bento/issues/682#issuecomment-251865276.

— I'm on a Mac btw. Also applied fix https://github.com/laravel/homestead/pull/382/commits/44a588fc254ad7c71a7254e5a42bf5d4e1a18e27 and boots fine now.

[svpernova09]

@sebastiaanluca You have to manually download Virtualbox 5.1, you can't upgrade from 5.0.x -> 5.1.x from inside the Virtualbox App.

[sebastiaanluca]

@svpernova09 I downloaded the latest version from their site (today) and installed it, yet it shows 5.0.30 while the site now displays 5.1? Very weird. Will try again.

[pvledoux]

Same problem here since I upgraded to homestead 4.0.2. I upgraded to VirtualBox 5.0.1 but with no effect, still have this message when I boot the box:

Then Vagrant timeout.

[pvledoux]

I saw the explanation here a bit late. Just checking the Connect Cable setting in VirtualBox do the trick.

[svpernova09]

@pvledoux Upgrade to Virtualbox 5.__1__ By downloading the installer fresh from their website.