7

Using a new install of Laravel with Laravel Homestead I've been trying to get Vagrant to boot, but it keeps timing out. I tried using the Default virtual switch, as well as the DockerNAT and NewInternalVirtualSwitch which is a virtual switch I added using the Hyper-V Manager.

I know I can leave the provider as VirtualBox and turn off Hyper-V, but since we use Vagrant and Docker for different application doing this over the last couple days has become tedious since Docker for Windows on Windows 10 Pro requires Hyper-V to be on so each time you have to shut down and restart in either direction.

Has anyone gotten Laravel Homestead to work using the Hyper-V provider, and what steps did you have to take to get networking to work which appears to be the issue?

Homestead.yaml

ip: 192.168.10.10
memory: 2048
cpus: 1
provider: hyperv
authorize: ~/.ssh/example/id_rsa.pub
keys:
    - ~/.ssh/example/id_rsa
folders:
    -
        map: 'D:\Projects\example\server'
        to: /home/vagrant/server
sites:
    -
        map: server.app
        to: /home/vagrant/server/public
databases:
    - example
name: example
hostname: example

Vagrant Up

Bringing machine 'example' up with 'hyperv' provider...
==> example: Verifying Hyper-V is enabled...
==> example: Importing a Hyper-V instance
    example: Please choose a switch to attach to your Hyper-V instance.
    example: If none of these are appropriate, please open the Hyper-V manager
    example: to create a new virtual switch.
    example:
    example: 1) DockerNAT
    example: 2) Default Switch
    example: 3) NewInternalVirtualSwitch
    example:
    example: What switch would you like to use? 3
    example: Cloning virtual hard drive...
    example: Creating and registering the VM...
    example: Setting VM Integration Services
    example: Successfully imported a VM with name: ubuntu-16.04-amd64_1
==> example: Starting the machine...
==> example: Waiting for the machine to report its IP address...
    example: Timeout: 120 seconds
    example: IP: fe80::215:5dff:fe38:107
==> example: Waiting for machine to boot. This may take a few minutes...
    example: SSH address: fe80::215:5dff:fe38:107:22
    example: SSH username: vagrant
    example: SSH auth method: private key <--- Stalls out for a couple minutes

Error

Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

Update

Also tried tip 4 using an external virtual switch and it makes it further, but still fails with an error while trying to assign a hostname:

==> example: Machine booted and ready!
==> example: Setting hostname...
No host IP was given to the Vagrant core NFS helper. This is
an internal error that should be reported as a bug.
Daniel A. White
  • 187,200
  • 47
  • 362
  • 445
mtpultz
  • 17,267
  • 22
  • 122
  • 201

3 Answers3

1

Edit: After setting it all up and testing workflow, I went back to VirtualBox + Homestead and disabled Hyper V. The bottom line is that Windows and Linux are not very compatible with each other and while Hyper V is native to Windows, everything that follows won't be and even simple tasks like copying files and setting permissions require a lot of labor.

I will leave my answer below, maybe someone else or I will come back to it in the future.

I just spent a day trying to get it to work and I couldn't but I came up with a solution that works better for me at least so I'll share it here.

If your workstation runs Windows 10 Pro with Hyper V and you know how to set up your production server, then it might work for you.

The idea is to give up on Homestead and set up your local server just like you do the production server but on Hyper V:

  1. Enable Hyper V
  2. Download your server OS image (Ubuntu 18.04 for me) and create a virtual machine with it.
  3. Choose what you need from the list of software included in homestead and install those on the virtual machine (for me its Nginx, PHP, PostgreSQL, Git, Python, and Composer).

At this point you pretty much have your custom made Homestead on Hyper V. Log into the virtual machine, copy its ip (it should show it upon login but if not, here is a command to bring it up on Ubuntu ip addr show eth0 | grep inet | awk '{ print $2; }' | sed 's/\/.*$//'), enter it into the browser window and it should bring the default Nginx frontpage up.

It's pretty easy, but the problem is that this ip is dynamic and it will keep resetting. The toughest part is to make it static.

  1. Set ip in the Hyper-V manager to static right click the virtual machine -> Settings -> Network Adapter -> Advanced Features. Reboot everything

  2. Set ip to static in the OS in virtual machine (guide for Ubuntu 18.04). Note that ip address of the host Hyper V vEthernet adapter (ipconfig on Win 10 to bring it up) is the gateway address for the virtual machine OS.

So pros and cons from my perspective.

Pros:

  • Works faster and cleaner on Windows + Hyper V than on Windows + Oracle Virtual Box
  • Customizable and updatable. The only way to update Homestead seems to be delete it and download the new one.

Cons:

  • Hard to set up if you are not familiar with your production server setup
  • Setting up static IP is really a painful lot of hacking
  • Accessing files between Linux and Windows requires Samba dependency
  • Managing permissions of Linux files accessed through Windows is complicated
  • Linux guest doesn't seem to have access to GPU through Hyper V
Arthur Tarasov
  • 3,517
  • 9
  • 45
  • 57
0

This problem may happen because by default, the Hyper-V switches are treated as Public network; the Windows firewall blocks access to virtual machines.

One easy but dangerous workaround is to simply turn off the Windows firewall. You can do that to test whether this is your problem, but of course do not leave the firewall off.

A better solution is to disable the firewall only for the network switch (or switches). This cannot be done in the GUI; you need an elevated PowerShell for that.

set-NetFirewallProfile -DisabledInterfaceAliases NewInternalVirtualSwitch,DockerNAT,Default

Note that if you want to disable the firewall for multiple switches, you must specify all of them in a single call to Set-NetFirewallProfile.

An even better solution would be to change the switches to private network, but I am not aware of any way to do that.

Kevin Keane
  • 1,506
  • 12
  • 24
0

Had similar issues here (on Windows 10 Home) trying to run Docker along side Homestead. I can't say for sure what did the trick but I ended up with this:

  1. In Windows features turn on:
    • Virtual Machine Platform
    • Windows Hypervisor Platform
    • Windows Subsystem for Linux
  2. Used HyperVSwitch to turn on even more Hyper-V (just turning it on as a "Windows feature" is not enough!) https://unclassified.software/en/apps/hypervswitch
  3. Restart Windows
  4. In the VirtualBox manager disabled "Adapter 2" for the Homestead machine (Settings > Network > Adapter 2 > uncheck Enable Network Adapter)
  5. Run the Homestead machine as normally.

Adapter 2 will be turned on again once you restart the Homestead machine But it seams that it now works fine in combination with all the Hyper-V settings.

Since it was a lot of trail, error and restarting of servers I'm not sure what exactly did the trick but I hope it helps some people in their quest to run Docker and Homestead together. I know now at least that it's possible :)

Arno van Oordt
  • 2,912
  • 5
  • 33
  • 63