Not able to connect to VM on Windows 7

[jaden]

Vagrant version

Vagrant 1.9.0

Provider & Provider version

VirtualBox 5.0.30 r112061

Host operating system

Windows 7 x64 Ultimate SP1

Homestead.yaml

---
ip: "192.168.10.10"
memory: 1024
cpus: 1
provider: virtualbox

authorize: ~/.ssh/id_rsa.pub

keys:
    - ~/.ssh/id_rsa

folders:
    - map: D:\Dev\projects
      to: /home/vagrant/projects

sites:
    - map: '~^(?<project>.+)\.app$'
      to: /home/vagrant/projects/\$project/public

databases:
    - homestead

Vagrant up output

https://gist.github.com/jaden/ea07b79d9f55e84d80244486b84fbac6

Expected behavior

192.168.10.10 should have been set as the static IP

Actual behavior

The VM appears to hang, but the console shows the following message (updating until the 5 minutes have elapsed)

[*** ] A start job is running for Raise network interface (2min 35s / 5min 3)

Once the VM boots, it has no static ip, as ifconfig shows:

enp0s3    Link encap:Ethernet  HWaddr 08:00:27:b5:5b:5e
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:144901 errors:0 dropped:0 overruns:0 frame:0
          TX packets:39078 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:69 errors:0 dropped:0 overruns:0 frame:0
          TX packets:69 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1
          RX bytes:36681 (36.6 KB)  TX bytes:36681 (36.6 KB)

Steps to reproduce

1. Run vagrant up with the laravel/homestead box version 0.6.0 on a Windows 7 host.
2. Wait for the 5 minute time-out

Using the previous box version (0.5.0) by adding the following line to Homestead.yaml sets the static IP and boots up normally:
version: "0.5.0"

[svpernova09]

Try running vagrant destroy -f to destroy your VM and then delete the .vagrant folder where you have Homestead installed.

[jaden]

I did that. I also went one step further to take homestead out of the equation. I created a new folder, ran vagrant init then pointed at the latest homestead box. Both attempts resulted in the same behavior.

[jaden]

In order to rule out an issue with my configuration, I reproduced this on another Windows 7 x64 machine on a different network and got the same result.

[svpernova09]

Where you using Virtualbox 5.0.x in both machines? I've had to update all of my systems to 5.1.x since Vagrant 1.8 started giving me troubles.

This thread seems to also suggest upgrading Virtualbox may help: chef/bento#682

[jaden]

Yes, 5.0.x on both. I thought 5.0.18 was the latest version. Thanks for the pointer to 5.1. I'll upgrade and report back.

[svpernova09]

Note: You can't upgrade from 5.0.x -> 5.1.x from the app, you'll want to download the 5.1.x installer, install it, then also upgrade the extensions. It should prompt you to install the new extension on launch.

[jaden]

5.1 fixed the issue. I can use homestead 0.6.0 now. Thanks for the help!

[svpernova09]