-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
error provisioning host: Hyper-V PowerShell Module is not available #9040
Comments
Could you please test to see if this command fixes your problem:
Then run:
The additional logging here will help us to see what the underlying command line is that docker-machine is attempting to execute. I found some related issues here:
Once we can confirm that the problem is fixed, I will update the error message to point directly to this solution. |
@tstromberg Tried with above commands no luck below is the error screenshot |
@khsabhishek are you sure your windows supports virtualization ? |
@medyagh Yes it supports and was working before not sure all of a sudden its broken. I have provided my screenshots above. |
@rajurh do you mind trying to crate a VM manuallly using hyper-v manager to see if it allows you ? yet I would like minikube to provide a better error. https://minikube.sigs.k8s.io/docs/drivers/hyperv/ also if you install docker, you can user our newest driver, docker driver. minikube delete --all |
@medyagh No luck, with docker driver we have limitations like ingress controller addons, etc. |
@rajurh I wonder if you still have this issue, to me it sounds like there is something about your hyperv installation, do you mind sharing your hperv virtual switch by clicking on the hyperv manager ? and see if you can create a new virtual switch and pass it to minikube using the flag
|
@medyagh Thanks for checking - Yes issue still exists. I tried creating a new switch as shown in the below screenshot and referencing in minikube command no luck still the same error |
the error message seems to be hyperv not configured correctly. |
@khsabhishek do you have this problem, I wonder if you have tried our docker driver? for more information on the docker driver checkout: |
Regrettably @khsabhishek , there isn't enough information in this issue to make it actionable, and a long enough duration has passed, so this issue is likely difficult to replicate. If you can provide any additional details, such as: |
minikube start All you need is Docker (or similarly compatible) container or a Virtual Machine environment, and Kubernetes is a single command away: minikube start Installing... 😄 minikube v1.25.2 on Microsoft Windows 10 Enterprise 10.0.19042 Build 19042 ❌ Exiting due to PR_HYPERV_MODULE_NOT_INSTALLED: Failed to start host: creating host: create: precreate: Hyper-V PowerShell Module is not available |
How do I check whether my Hyper-V is working properly or not? |
I am getting the exact same error while installing creating a minikube also I see not Hyper-V manger in my system. (I am using windows 11) |
If you're running Windows, make sure you are not using Home. Home does not support the Hyper-V components necessary. You need Pro or higher. |
just run into this, windows home is my issue I assume, guess using minikube is not possible or is likely this can be handled ina future release? |
A few years ago there was a preview in a Windows Insider build running kubernetes on Home, but I'm not sure what happened to it. There are a number of options for local kubernetes, I'm not sure if any of them can fake a hypervisor or not. Most documentation doesn't discern the different editions of Windows so it's hard to tell until things don't work. |
hyper=v is fine, docker and podman run fine so not sure what is missing |
Container on windows sucks!!! |
C:\Users\khsab>minikube start --driver=hyperv
! StartHost failed, but will try again: creating host: create: precreate: Hyper-V PowerShell Module is not available
X error provisioning host: Failed to start host: creating host: create: precreate: Hyper-V PowerShell Module is not available
*
The text was updated successfully, but these errors were encountered: