Minikube: hyperv: "minikube stop" fails (Shutting down 0% until it eventually times out)

[shahiddev]

BUG REPORT
Please provide the following details:

Environment: Windows 10 Pro 1803

Minikube version (use minikube version): v0.28.0

• OS (e.g. from /etc/os-release): Windows 10 Pro 1803
• VM Driver (e.g. cat ~/.minikube/machines/minikube/config.json | grep DriverName): Hyper-v
• ISO version (e.g. cat ~/.minikube/machines/minikube/config.json | grep -i ISO or minikube ssh cat /etc/VERSION): v0.28.0
• Install tools:
• Others:

What happened: Minikube stop fails to stop minikube VM

What you expected to happen: VM stops

How to reproduce it (as minimally and precisely as possible): With running minikube, perform minikube stop

Output of minikube logs (if applicable):

Anything else do we need to know:
Clean install of Minikube 0.28.0 (deleted .minikube folder)
Command sits with powershell overlay showing Shutting down 0% until it eventually times out
Trying to shutdown via Hyper-V manager/Powershell doesn't work either
Opening VM in hyper-v shows command prompt - may not be relevant?

[shahiddev]

Have rolled back to 0.27.0 to verify that minikube stop works in that version which it does

[gitfool]

Same environment and same problem here. Also, if I try to stop minikube from Hyper-V Manager I get the following error:

[gbraad]

This is very likley unrelated to Minikube, as we only issue commands to the
hypervisor. If the manager even fails, it is related to the host and the
hypervisror. Please check your event log on Windows

On Wed, Jun 20, 2018 at 5:37 AM, Sean Fausett [e-mail]
wrote:

Same environment and same problem here. Also, if I try to stop minikube
from Hyper-V Manager I get the following error:

[image: image]
https://user-images.githubusercontent.com/750121/41625429-eef6fa90-746c-11e8-895c-95d3f4005973.png

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/minikube/issues/2914#issuecomment-398554460,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAHZrFaM4Lf9V_ctu2ejQnJwiUBC2wUks5t-W8UgaJpZM4Utd8V
.

--

Gerard Braad | http://gbraad.nl
[ Doing Open Source Matters ]

[F21]

I am seeing this issue. Shutdown takes a very long time and fails with this error:

Stopping local Kubernetes cluster...
Error stopping machine:  Error stopping host: minikube: exit status 1
================================================================================
An error has occurred. Would you like to opt in to sending anonymized crash
information to minikube to help prevent future errors?
To opt out of these messages, run the command:
        minikube config set WantReportErrorPrompt false
================================================================================

Once the shutdown fails, the machine reverts to "running" inside the Hyper-V manager. I then use Hyper-V to turn off the machine.

[shahiddev]

@gbraad I'll dig a little deeper later but I reverted back to 0.27.0 and it works fine, upgrade to 0.28.0 and it stops working. So there seems to be something unusual going on with 0.28.0

Edited to add, if I connect to the VM and login I can then issue sudo poweroff -p and it shuts down fine.

Nothing blatantly obvious in the hyper-v logs, probably closest thing of interest I've found is

'minikube' has encountered a fatal error.  The guest operating system reported that it failed with the following error codes: ErrorCode0: 0x8, ErrorCode1: 0x81000004100E0000, ErrorCode2: 0x7FB9E02E643F, ErrorCode3: 0x40000000, ErrorCode4: 0x7FFDF78C75A0.  If the problem persists, contact Product Support for the guest operating system.

EDIT: Actually same error is logged for 0.27.0 but it doesn't impact shutdown on that version

[poagester]

i can confirm this is occuring with windows 10 pro 1703 with minikube .28 as well. My error message is:

C:\WINDOWS\system32>minikube stop minikube
Stopping local Kubernetes cluster...
Error stopping machine: Error stopping host: minikube: exit status 1

I will try to update this pc and see if that works, if not i will use the suggested downgrade for minikube.

upgrading to 1803 with Minikube v28 had the same results
downgrading to Minikube v27 works as normal

[discosultan]

Quite annoying indeed. I've found

$ minikube ssh
$ sudo poweroff

to be the fastest workaround.

[LazerFX]

Thanks for the minikube ssh | sudo poweroff workaround for this issue - even telling Hyper-V to shut the device down did not work (Presumably because it was in a frozen // not responding state).

Is there any further information those of us who have this problem can provide to assist in resolving? I've not seen anything particularly nasty in the event logs or similar...

---

Edit
I have noticed that the sudo shutdown in minikube 0.27.0 does an immediate shutdown, whereas in minikube 0.28.0, it schedules the shutdown for one minute in the future. I don't know if the infrastructure issues a sudo shutdown in the background, but if it does and gets into a hang or race condition with itself re-issuing the command, it will never actually shutdown...

[wlei07]

The same issue with minikube 0.28.0 on windows 10

[gbraad]

@LazerFX @wlei07 can any of you try to use minishift to verify if we have the same issue? If this issue is reproducible we might be able to dig into this deeper...

[gbraad]

@shahiddev I noticed @LazerFX has observed the command shutdown gets scheduled for after one minute. This could mean the shutdown will happen...

In code, Stop-VM is triggered from a powershell session:

https://github.com/kubernetes/minikube/blob/33fce13254f02801d8674f2887100d9127cd2445/vendor/github.com/docker/machine/drivers/hyperv/hyperv.go#L346

So, I wonder what causes this difference in behaviour...

[shahiddev]

@gbraad I've certainly waited for over 1min (in fact over 5mins) and it doesn't shutdown.
My suspicions were around how Hyper-V interacts with the Linux VM but I couldn't find anything useful to help with this. I did experiment with disabling the hyper-v integration services which includes an option for Guest OS shutdown and disabling this causes an immediate error.

I'm preparing for a talk tomorrow so don't want to mess with my minikube installation today but can try and have another go at this later this week.

[LazerFX]

@gbraad I'm sorry, I don't know what minishift is, but I can certainly try and Google it when I'm in the office on the machine tomorrow, see if I can diagnose the issue. Any tips on what you're looking for, I'd appreciate :-D

I'm quite a neophyte to the whole kubernetes infrastructure, so I "don't know what I don't know" as the saying goes - I don't know the holes in my knowledge where I should be able to fill in.

[gbraad]

Minishift is a fork of minikube and we share a lot and work together on
issues where possible.

Instead of kubernetes we deploy openshift, which an Enterprise grade
kubernetes deployment.

Details on minishift.io

I haven't see this happen on out tool, but could be related to config. So
this is why I would like you to try.

On Jul 17, 2018 04:37, "Peter Street" [e-mail] wrote:

@gbraad https://github.com/gbraad I'm sorry, I don't know what minishift
is, but I can certainly try and Google it when I'm in the office on the
machine tomorrow, see if I can diagnose the issue. Any tips on what you're
looking for, I'd appreciate :-D

I'm quite a neophyte to the whole kubernetes infrastructure, so I "don't
know what I don't know" as the saying goes - I don't know the holes in my
knowledge where I should be able to fill in.

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
https://github.com/kubernetes/minikube/issues/2914#issuecomment-405373867,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAHZoGJS81GRhFrjGTZET50xgYSIJj0ks5uHPl4gaJpZM4Utd8V
.

[LazerFX]

Just rolled up a minishift environment, based on minishift version v1.21.0+a8c8b37, and that is capable of successfully shutting down using minishift stop.

Based on other comments, I also tried the Stop-VM minikube command mentioned above. It puts a 0% progress-bar in the PowerShell window, and nothing continues. Looking in the SSH, I see there is a long-running -bash command:

$ sudo ps all
F   UID   PID  PPID PRI  NI    VSZ   RSS WCHAN  STAT TTY        TIME COMMAND
4     0  2052     1  20   0   9240   448 -      Ss+  tty1       0:00 /sbin/getty
4     0  2069     1  20   0   9240   452 -      Ss+  ttyS0      0:00 /sbin/getty
0  1001  4065  4064  20   0  16236  3432 -      Ss   pts/0      0:00 -bash
4     0  4267  4065  20   0  20316   688 -      R+   pts/0      0:00 ps all

That wasn't there prior to the minikube stop command being triggered.

[gbraad]

Hmmm... so this is very isolated. We (minishift) use the stock libmachine
drivers and library, while minikube pulled them in-repo. I will have a look
if I can find something that can explain this.

On Tue, Jul 17, 2018 at 8:12 PM, Peter Street [e-mail]
wrote:

Just rolled up a minishift environment, based on minishift version
v1.21.0+a8c8b37, and that is capable of successfully shutting down using minishift
stop.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/minikube/issues/2914#issuecomment-405560739,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAHZoz1HQ4d6bEsdeCPAwZYV6sE5Ljzks5uHdTHgaJpZM4Utd8V
.

--

Gerard Braad | http://gbraad.nl
[ Doing Open Source Matters ]

[shahiddev]

looks like minikube 0.28.1 also has this issue.

[LazerFX]

Was there an update to the ISO for 0.28? Can this be isolated as a potential source - i.e. the OS not responding properly? Can an 0.27 ISO be used on 0.28?

[shahiddev]

@LazerFX I just did the same thing you did with minikube ssh but I can see that Bash command is already running before the shutdown was initiated. I ran minikube stop in a different window whilst connected via minikube SSH

[shahiddev]

@gbraad Looks like MiniShift is using the latest version of Docker Machine (0.15) where as Minikube isn't. I wanted to update to the latest version anyway so would it make sense to just update to that? I'm a bit of a noob on this project so don't know the best way of doing that.

[gbraad]

We will discuss anyway with @dlorenc to move away from libmachine (to our
fork at machine-drivers/machine) as they entered maintenance mode (no new
features, only bugfixes)... even adding fixes have been slow these days.

On Thu, Jul 19, 2018, 01:13 Shahid Iqbal [e-mail] wrote:

@gbraad https://github.com/gbraad Looks like MiniShift is using the
latest version of Docker Machine (0.15) where as Minikube isn't. I wanted
to update to the latest version anyway so would it make sense to just
update to that? I'm a bit of a noob on this project so don't know the best
way of doing that.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/minikube/issues/2914#issuecomment-406006992,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAHZk8Mz3Pz4I8QxgfsuEeR8HPPNT_0ks5uH2y-gaJpZM4Utd8V
.

[saostad]

Same Problem here:

win 10 enterprice verion 1803
Docker 18.06.0-ce
kubectl 1.11.0
minikube v0.28.2

[kognise]

Same problem with the same exact information as @saostad. Is there a way to temporarily fix this?

[shahiddev]

only minikube ssh and then sudo poweroff

[kognise]

@shahiddev That works. I discovered that downgrading works too, though.

[idrm]

You can combine the commands to issue a shutdown in one line:

minikube ssh "sudo poweroff"

[kognise]

Could minikube just be updated to run that command for minikube stop?

[gbraad]

Minkube uses docker-machin to issue a shutdown using the hypervisor
management tools. this would be acpi call. Surely minikube could use an
sshcommand instead, but the issue is with submachine... And this library is
in maintenance mode. I also haven't seen this issue with our fork yet...
Which we are in the process of adding to minikube. I'll keep an eye on this
issue and see if the library change fixes this.

On Aug 23, 2018 09:39, "Felix Mattick" [e-mail] wrote:

Could minikube just be updated to run that command for minikube stop?

—
You are receiving this because you were mentioned.

Reply to this email directly, view it on GitHub
https://github.com/kubernetes/minikube/issues/2914#issuecomment-415248809,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAHZqijtlxNuNFf-pAjewnl8leEiwSmks5uTgfCgaJpZM4Utd8V
.

[zmbq]

I have exactly the same issue on Windows 10 pro. Stopping the cluster with poweroff worked, but then the cluster couldn't be started again. I had to uninstall, remove ~/.minikube and install version 0.27 for everything to work.

[kognise]

Yes, that was how I solved it, too.

On Sep 4, 2018, at 10:33 AM, Itay Zandbank [e-mail] wrote:

I have exactly the same issue on Windows 10 pro. Stopping the cluster with poweroff worked, but then the cluster couldn't be started again. I had to uninstall, remove ~/.minikube and install version 0.27 for everything to work.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

[seancheung]

Downgrading minikube from 0.28.2 to 0.27 solves everything.
No need to remove directory ~/.minikube, just run minikube delete before starting again.

minikube delete
minikube config set bootstraper localkube
minikube config set kubernetes-version v1.10.0
minikube config set vm-driver hyperv
minikube config set hyperv-virtual-switch <your-vswitch-name>

Downgrading with chocolatey:

choco install -y --force minikube --version 0.27

Start

minikube start

[ibrahimelement]

Also running into this problem on the latest version:

OS: Windows 10 Pro (17134)
VM-Driver: HyperV
Minikube: v.0.30.0

I can shutdown minikube by manually typing shutdown now in the Hyper-V Manager.

[meurig]

Same here:

OS: Windows 10 Pro (17134)
VM-Driver: HyperV
Minikube: v.0.30.0

I can shut it down with:
minikube ssh "sudo poweroff"

I downgraded to 0.27 as follows:

minikube ssh "sudo poweroff"
minikube delete
choco uninstall minikube
choco install minikube --version 0.27
minikube start --vm-driver hyperv --hyperv-virtual-switch "Primary Virtual Switch"

I can then stop it with:
minikube stop

[gbraad]

This a a duplicate of an earlier reported issue. This has been in several
releases already. After the move to machine-drivers/machine we can look
into this

On Wed, Oct 10, 2018, 16:45 Meurig Freeman [e-mail] wrote:

Same here:

OS: Windows 10 Pro (17134)
VM-Driver: HyperV
Minikube: v.0.30.0

I can shut it down with:
minikube ssh "sudo poweroff"

I downgraded to 0.27 as follows:

minikube ssh "sudo poweroff"
minikube delete
choco uninstall minikube
choco install minikube --version 0.27
minikube start --vm-driver hyperv --hyperv-virtual-switch "Primary Virtual Switch"

I can then stop it with:
minikube stop

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/minikube/issues/2914#issuecomment-428489332,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAAHZg6N7Hzj1Nc7lAxsAEjOuWMMJiV_ks5ujbOUgaJpZM4Utd8V
.

[worthwhileindustries]

used minikube installer fresh install, hyperv driver, minikube vm never shuts down

C:\Users\Tristan
λ minikube version
minikube version: v0.30.0

C:\Users\Tristan
λ minikube stop
Stopping local Kubernetes cluster...
Error stopping machine:  Error stopping host: minikube: exit status 1
================================================================================
An error has occurred. Would you like to opt in to sending anonymized crash
information to minikube to help prevent future errors?
To opt out of these messages, run the command:
        minikube config set WantReportErrorPrompt false
================================================================================
Please enter your response [Y/n]:
C:\Users\Tristan
λ Stopping local Kubernetes cluster... Error stopping machine:  Error stopping host: minikube: exit status 1

[worthwhileindustries]

fresh install with windows installer, hyperv, win 10. It does show that it's shutting down in hyperv but, then the status goes away and nothing happens.

[m1o1]

Same problem here. And running minikube stop puts my minikube VM in a "Shutting down..." state seemingly forever, and I can't turn it off / delete it, since "device or resource busy". When I right click at this point, it doesn't show an option to "Turn Off", but if I hit Delete on the minikube VM, nothing seems to change in the Hyper-V manager, but that option shows up in the right-click menu.

[mpp-shahi]

Is there an update to this issue?

[AlanCarlyle]

Still happening here as well....

OS: Windows 10 Pro (17134)
VM-Driver: HyperV
Minikube: v.0.31.0 _(just updated a couple of days again)_

Using minikube ssh to do a shutdown is getting pretty old....
Any chance of a fix for the new year?

[bardware]

Experienced this with minikube version: v0.32.0

[deoren]

Experienced this with minikube version: v0.32.0

Same, but after reading further up it seems the developers already know this. For anyone going to the bottom of the thread first, see these workarounds:

• https://github.com/kubernetes/minikube/issues/2914#issuecomment-401562007
• https://github.com/kubernetes/minikube/issues/2914#issuecomment-402075939
• https://github.com/kubernetes/minikube/issues/2914#issuecomment-415137290

[tstromberg]

I think that calling 'ssh sudo poweroff' sounds like a reasonable approach before falling back on the ACPI path. Is anyone on this thread up to sending in a PR to address this? Thanks!

[vxavictor513]

Still happening on v0.35.0

[tstromberg]

@vxavictor513 - Do you mind attaching the output of:

minikube stop --alsologtostderr -v=8

Thanks!

[vxavictor513]

@tstromberg - This is what I got after running the command and waiting for 10 minutes.

$ minikube stop --alsologtostderr -v=8
W0308 07:02:16.215679   20084 root.go:145] Error reading config file at C:\Users\user\.minikube\config\config.json: open C:\Users\user\.minikube\config\config.json: The system cannot find the file specified.
I0308 07:02:16.219677   20084 notify.go:121] Checking for updates...
:   Stopping "minikube" in hyperv ...
Stopping "minikube"...
[executing ==>] : C:\windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive ( Hyper-V\Get-VM minikube ).state
[stdout =====>] : Running

[stderr =====>] :
[executing ==>] : C:\windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive Hyper-V\Stop-VM minikube

I force-cancelled the minikube stop command by Ctrl+C, then minikube status shows it is still up.

$ minikube status
host: Running
kubelet: Running
apiserver: Running
kubectl: Correctly Configured: pointing to minikube-vm at 192.168.1.213

[robintanner]

FWIW, I experienced a lot of these errors when setting up minikube via chocolatey w/ powershell on windows 10. minikube delete followed by recreating eventually worked after a few tries.

[bjorn-ali-goransson]

Just had a scare with this when the kube wouldn't stop. Just followed the simple steps from the tutorial. Thought a computer restart would do it, but it got stuck at "Restarting your computer" for about 10 minutes. Luckily, though, in the end, it actually restarted.

[FrauleinGela]

yeah, I deleted my ~/.minikube folder + minikube virtual machine and run process : minikube start --vm-driver=x --kubernetes-version="vx.xx.x" and works 👍

[Enoch-Ye]

Same problem here

Windows 10 Enterprise 1803
Docker version 18.09.2
Kubectl v1.10.11
Minikube v1.0.0

[blueelvis]

@tstromberg I have also seen this where the machine in Hyper-V refuses to Power off even from the manager. I tried both Reset and ACPI Shutdown and it still didn't work. Strangely this has happened only with minikube for me till now. I would like to take a stab at this once I push the documentation of all the available arguments.

[Valgard]

Same problem here

Windows 10 Pro 1903
Docker v18.09.2
Kubectl v1.15.0
Minikube v1.2.0

Output from minikube stop:

* Stopping "minikube" in hyperv ...
* Stopping "minikube" in hyperv ...
* Stopping "minikube" in hyperv ...
* Stopping "minikube" in hyperv ...
* Stopping "minikube" in hyperv ...

X Unable to stop VM: Temporary Error: Stop: minikube: exit status 1
Temporary Error: Stop: minikube: exit status 1
Temporary Error: Stop: minikube: exit status 1
Temporary Error: Stop: minikube: exit status 1
Temporary Error: Stop: minikube: exit status 1

* Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
  - https://github.com/kubernetes/minikube/issues/new

Output from minikube stop --alsologtostderr -v=8:

I0702 14:50:50.622640   20504 notify.go:128] Checking for updates...                                                                                            * Stopping "minikube" in hyperv ...                                                                                                                             Stopping "minikube"...
[executing ==>] : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive ( Hyper-V\Get-VM minikube ).state
[stdout =====>] : Running

[stderr =====>] :
[executing ==>] : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive Hyper-V\Stop-VM minikube
[stdout =====>] :
[stderr =====>] : Hyper-V\Stop-VM : Der Status von "minikube" konnte nicht geändert werden.
In Zeile:1 Zeichen:1
+ Hyper-V\Stop-VM minikube
+ ~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Stop-VM], VirtualizationException
    + FullyQualifiedErrorId : OperationFailed,Microsoft.HyperV.PowerShell.Commands.StopVM
                                                                                                                                                                                                                                                                                                                                I0702 15:00:52.605171   20504 utils.go:126] error: Temporary Error: Stop: minikube: exit status 1 - sleeping 1s                                                 I0702 15:00:53.611320   20504 utils.go:115] retry loop 1                                                                                                        * Stopping "minikube" in hyperv ...                                                                                                                             Stopping "minikube"...
[executing ==>] : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive ( Hyper-V\Get-VM minikube ).state
[stdout =====>] : Running

[stderr =====>] :
[executing ==>] : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive Hyper-V\Stop-VM minikube
[stdout =====>] :
[stderr =====>] : Hyper-V\Stop-VM : Der Status von "minikube" konnte nicht geändert werden.
In Zeile:1 Zeichen:1
+ Hyper-V\Stop-VM minikube
+ ~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Stop-VM], VirtualizationException
    + FullyQualifiedErrorId : OperationFailed,Microsoft.HyperV.PowerShell.Commands.StopVM
                                                                                                                                                                                                                                                                                                                                I0702 15:10:55.198539   20504 utils.go:126] error: Temporary Error: Stop: minikube: exit status 1 - sleeping 1s                                                 I0702 15:10:56.201604   20504 utils.go:115] retry loop 2                                                                                                        * Stopping "minikube" in hyperv ...                                                                                                                             Stopping "minikube"...
[executing ==>] : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive ( Hyper-V\Get-VM minikube ).state
[stdout =====>] : Running

[stderr =====>] :
[executing ==>] : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive Hyper-V\Stop-VM minikube
[stdout =====>] :
[stderr =====>] : Hyper-V\Stop-VM : Der Status von "minikube" konnte nicht geändert werden.
In Zeile:1 Zeichen:1
+ Hyper-V\Stop-VM minikube
+ ~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Stop-VM], VirtualizationException
    + FullyQualifiedErrorId : OperationFailed,Microsoft.HyperV.PowerShell.Commands.StopVM


I0702 15:20:57.826478   20504 utils.go:126] error: Temporary Error: Stop: minikube: exit status 1 - sleeping 1s
I0702 15:20:58.831673   20504 utils.go:115] retry loop 3
* Stopping "minikube" in hyperv ...
Stopping "minikube"...
[executing ==>] : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive ( Hyper-V\Get-VM minikube ).state
[stdout =====>] : Running

[stderr =====>] :
[executing ==>] : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive Hyper-V\Stop-VM minikube
[stdout =====>] :
[stderr =====>] : Hyper-V\Stop-VM : Der Status von "minikube" konnte nicht geändert werden.
In Zeile:1 Zeichen:1
+ Hyper-V\Stop-VM minikube
+ ~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Stop-VM], VirtualizationException
    + FullyQualifiedErrorId : OperationFailed,Microsoft.HyperV.PowerShell.Commands.StopVM


I0702 15:31:00.199707   20504 utils.go:126] error: Temporary Error: Stop: minikube: exit status 1 - sleeping 1s
I0702 15:31:01.204811   20504 utils.go:115] retry loop 4
* Stopping "minikube" in hyperv ...
Stopping "minikube"...
[executing ==>] : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive ( Hyper-V\Get-VM minikube ).state
[stdout =====>] : Running

[stderr =====>] :
[executing ==>] : C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive Hyper-V\Stop-VM minikube
[stdout =====>] :
[stderr =====>] : Hyper-V\Stop-VM : Der Status von "minikube" konnte nicht geändert werden.
In Zeile:1 Zeichen:1
+ Hyper-V\Stop-VM minikube
+ ~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Stop-VM], VirtualizationException
    + FullyQualifiedErrorId : OperationFailed,Microsoft.HyperV.PowerShell.Commands.StopVM


I0702 15:41:02.817565   20504 utils.go:126] error: Temporary Error: Stop: minikube: exit status 1 - sleeping 1s
W0702 15:41:03.819005   20504 exit.go:100] Unable to stop VM: Temporary Error: Stop: minikube: exit status 1
Temporary Error: Stop: minikube: exit status 1
Temporary Error: Stop: minikube: exit status 1
Temporary Error: Stop: minikube: exit status 1
Temporary Error: Stop: minikube: exit status 1

X Unable to stop VM: Temporary Error: Stop: minikube: exit status 1
Temporary Error: Stop: minikube: exit status 1
Temporary Error: Stop: minikube: exit status 1
Temporary Error: Stop: minikube: exit status 1
Temporary Error: Stop: minikube: exit status 1

* Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
  - https://github.com/kubernetes/minikube/issues/new

[thebjorn]

I have the same versions and issues as @Valgard above, in addition.. I was following the first tutorial (https://kubernetes.io/docs/tutorials/hello-minikube/) and I could enable the heapster addon, but minikube crashed when trying to disable it:

c:\srv> minikube addons enable heapster
* heapster was successfully enabled

c:\srv> minikube addons disable heapster

X disable failed: [disabling addon deploy/addons/heapster/influx-grafana-rc.yaml.tmpl: Process exited with status 1]

* Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
  - https://github.com/kubernetes/minikube/issues/new

c:\srv> minikube addons disable heapster --alsologtostderr -v=8
I0707 18:47:39.551945   13496 notify.go:128] Checking for updates...
[executing ==>] : C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive ( Hyper-V\Get-VM minikube ).state
[stdout =====>] : Running

[stderr =====>] :
[executing ==>] : C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive ( Hyper-V\Get-VM minikube ).state
[stdout =====>] : Running

[stderr =====>] :
[executing ==>] : C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -NonInteractive (( Hyper-V\Get-VM minikube ).networkadapters[0]).ipaddresses[0]
[stdout =====>] : 192.168.1.148

[stderr =====>] :
W0707 18:47:42.377956   13496 exit.go:100] disable failed: [disabling addon deploy/addons/heapster/influx-grafana-rc.yaml.tmpl: Process exited with status 1]

X disable failed: [disabling addon deploy/addons/heapster/influx-grafana-rc.yaml.tmpl: Process exited with status 1]

* Sorry that minikube crashed. If this was unexpected, we would love to hear from you:
  - https://github.com/kubernetes/minikube/issues/new