Problem: Cannot start minikube with hyperv driver in Windows 10 #1523
Comments
|
Do you have Hyper-V installed on the same system? If so, Hyper-V claims exclusivity of the Vt-x extensions. In the case of Hyper-V you are unable to run two hypervisors. This is a reported known fact. You likely have a previously defined instance of minikube. Can you remove this first before trying to run |
|
@gbraad I have mention it in my post, if that was disabled, cannot open |
|
Again, Hyper-V claims exclusivity of the Virtual Extensions. This means VirtualBox will not be able to use them. You have probably started You need to delete this instance first, before you can start again with the Hyper-V driver. Just editing the hypervisor driver in the config is not enough. Config options do NOT change when respecified with the start command. This is a 'known' issue... |
|
I had to manually delete the minikube directory on windows10 as well to make it work. It would be cool if minikube start had a flag like And in any case it is common that cached config is overwritten by written config which is overwritten by shell arguments. This is just the natural way people expect things to work. |
|
@gbraad I faced the same issue - basically I screwed up my setup by deleting the minikube VM manually. That resulted in facing #459. Then I ran "minikube delete" which resulted in some failures, and tried starting it - for which I ended up here, despite specifying hyperv driver in the command line, receiving the mentioned failures (seemed like it's trying to use VBox instead..). What worked for me was to delete the .minikube folder (I couldn't find anything VBox related mentioned in config.json file) and then run "minikube start --vm-driver hyperv --hyperv-virtual-switch External". It's back online now. |
|
I reached here because I got the same original symptom just because I copy-pasted the command from the web and the "-" on the command line was something else, maybe Unicode. I didn't get any warning from minikube that I was passing funny parameters. |
|
I uninstalled minikube, which ran without complaint (Windows 10, uninstaller). But it left behind the virtual disk, which was consuming 20GB of disk space. So I manually deleted the minikube VM ( Stopping the VM Manager Service allowed me to clean up. Docker VM is still running ... |
I have used following command and its doesn't work:
$ cat ~/.minikube/machines/minikube/config.json | grep DriverName"DriverName": "virtualbox",minikube.exe start --vm-driver="hyperv" --hyperv-virtual-switch="Primary Virtual Switch"But I have found another problem, if you set
--vm-driver hypervargument tominikube, it doesnot overrideconfig.jsonfile value if it isvirtualbox, and still assumevirtualboxdriver.and also I have to change
DriverNameinconfig.jsonfile tohypervin path.minikube\machines\minikube, andminikubegive me following error:Platform:
Windows 10Please not that
hyper-vfeature is enabled in my system and docker itself works fine.And log is:
PS C:\kubernetes> $env:HYPERV_VIRTUAL_SWITCH="Primary Virtual Switch"PS C:\kubernetes> ./minikube.exe start --vm-driver hyperv --hyperv-virtual-switch="Primary Virtual Switch" --v=9The text was updated successfully, but these errors were encountered: