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

Hyper-V from within WSL #8700

davidtwco opened this Issue Jun 20, 2017 · 9 comments


Copy link

davidtwco commented Jun 20, 2017

Vagrant version

Vagrant 1.9.5 inside and outside WSL.

Host operating system

Windows/Bash for Windows

Guest operating system




Debug output

vagrant status --debug

Expected behavior

Listed status of Hyper-V VMs.

Actual behavior

Hyper-V was said to be unavailable.

Steps to reproduce

  1. Install Vagrant within WSL and follow Vagrant documentation on WSL.
  2. Use the Hyper-V provider in a Vagrantfile.
  3. Try to use Vagrant from within WSL.




This comment has been minimized.

Copy link

nigh8w0lf commented Jul 1, 2017

It's the same on the latest Version: 1.9.6
running vagrant up --provider=hyperv from within WSL, you get the below message.

_The provider 'hyperv' that was requested to back the machine
'default' is reporting that it isn't usable on this system. The
reason is shown below:

The Hyper-V provider only works on Windows. Please try to
use another provider._


This comment has been minimized.

Copy link

chrisroberts commented Jul 5, 2017

Hi there,

The WSL support in Vagrant is still very new and currently only the VirtualBox and Docker providers are supported. Other providers will gain support over time and I have labeled this issue as an enhancement.



This comment has been minimized.

Copy link

pierrebeaucamp commented Jul 6, 2017

Thanks for looking into this.
I just wanted to add that Docker on Windows is also using Hyper-V under the hood. Unfortunately that means that you can't run Virtualbox and Docker side-by-side. Vagrant integration with Hyper-V would be a real life-saver for anyone who needs Docker in their workflow.


This comment has been minimized.

Copy link

ironland commented Aug 9, 2017


has there been any progress on this? I was thinking of setting up my environment using vagrant within WSL and Hyper-V as the provider. Is this still possible?


This comment has been minimized.

Copy link

davidtwco commented Aug 9, 2017

@ironland You'll need to have a separate Command Prompt or PowerShell window open for running Vagrant commands. This means that your project will need to be in the Windows filesystem rather than the WSL filesystem.


This comment has been minimized.

Copy link

farmerbean commented Nov 16, 2017

I've also got this issue with Windows10 CU - I've aliased vagrant to the Windows exe but getting same issue.


This comment has been minimized.

Copy link

wilmardo commented Mar 29, 2018

Is there any progress on this?
Came accross this issue today for exact the reaseon @pierrebeaucamp states above, I would like to use Docker and Vagrant on the same host. To bad this isn't possible at the moment :/


This comment has been minimized.

Copy link

nocsi commented Apr 24, 2018

The vagrant hyper-v provider needs access to Hyper-V powershell module -- which isn't exposed directly from WSL. Easiest thing to do is just to open a powershell prompt from WSL (/mnt/c/Windows/System32/WindowsPowerShell/v1.0/powershell.exe) and use vagrant in that manner.

@chrisroberts chrisroberts modified the milestones: 2.1, 2.1.0 Apr 24, 2018

@chrisroberts chrisroberts self-assigned this Apr 25, 2018

@chrisroberts chrisroberts modified the milestones: 2.1.0, 2.1.1 May 2, 2018

@chrisroberts chrisroberts modified the milestones: 2.1.1, 2.1.2 May 4, 2018


This comment has been minimized.

Copy link

strarsis commented May 15, 2018

@nocsi: I need to run other *nix based tools like ansible. Although ansible can be installed on Windows (cmd), it won't work without adjustments because it expects different paths (like user home paths).

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