Funnily enough, it was when I started to heavily use Docker (for SimsLoader) and upgrading one of my laptops to Windows 10 that led me to using Vagrant with Hyper-V. Hyper-V is really cool. Docker runs "natively" under it and it's fast. Really fast.
Unfortunately, Microsoft's work to get all their cool stuff to function with all the opensource tools the Linux ecology has been working with for years. There have been a few posts on this, but they weren't sufficient or complete for me to get up and running.
So, this post is to track and list all the necessary steps to be successful with Vagrant and Hyper-V. These steps have been validated in Windows 10. They may work in Windows 8.1 - if they do, could someone tell me?
Also, if you have cool Powershell scripts to do any of these manual steps, please let me know. Ideally, there's a script that does the "only Once" stuff and a script that does the "Occasionally" stuff.
Stuff you do only Once
This enables the Hyper-V virtualization provider.
- Launch "Turn Windows features on or off"
- Scroll down to select "Hyper-V"
If you installed the "native" Docker, then you've probably already done this step.
Create a virtual switch
This provides the basis for networking within Hyper-V. Unlike Virtualbox, Hyper-V doesn't auto-create networks for you.
- Launch "Hyper-V Manager"
- Click on "Virtual Switch Manager..." (right-hand side)
- Select "Internal"
- Click on "Create Virtual Switch"
- Name the switch "Shared"
- Select the "Internal Network" radio button
- Click "Ok"
- Exit the "Hyper-V Manager" window
Connect the virtual switch to an existing network
This is required if you want your Vagrant-launched VM to get a DHCP-assigned IP address. Again, unlike Virtualbox, Hyper-V networks don't auto-allocate IP addresses.
- Go to "Control Panel > Network and Internet > Network Connections"
- Select a network connection with Internet (likely your Wireless)
- Right-click, select "Properties"
- Select the "Sharing" tab
- Click the "Allow other network users to connect through this computer's Internet connection"
- Select "vEthernet (Shared)"
- Click "Ok"
- Exit the "Network Connections" window
Disable SMB idle disconnects
Again, unlike Virtualbox, Hyper-V doesn't provide a file-sharing mechanism. (Granted, vboxfs isn't the greatest, but at least it's immediately functional). So, Vagrant uses SMB sharing. By default, Windows hosts will disconnect the SMB connection if it's idle for too long, which requires you to reboot your VM to reconnect the shared folder.
- In an administrative powershell, run "net config server /autodisconnect:-1"
Note: this may or may not be what you want to do for other purposes, particularly if you use SMB for other purposes.
Stuff you will have to do occasionally
Resharing the network with your virtual switch
If your internet-enabled network changes, you will need to attach your virtual switch to it. For example, if you switch from wireless to wired.
If your sharing network changes, you will need to reconnect your virtual switch. For example, if you go from home to work or work to Starbucks.
I haven't experienced any problems if I put my laptop to sleep, but awaken onto the same network, but that is also a possible time you may have to reshare your network.
Stuff you will have to do all the time
Launching a VM
- Open a terminal with administrative privileges. (Hyper-V requires this.)
- "vagrant up"
- You will be asked for your windows username/password to mount shared folders.
- Make sure it's the Windows username/password
- Depending on how your laptop is setup, you may or may not have to add a domain to that. (mmouse vs. mmouse@disney)