Minikube: Disable automatic checkpoints when using Hyper-V

Created on 6 Apr 2018 · 8Comments · Source: kubernetes/minikube

Is this a BUG REPORT or FEATURE REQUEST? (choose one): Feature Request

I've recently started using minikube with Hyper-V on my Windows 10 machine, since Docker for Windows has a hard requirement on Hyper-V. Hyper-V enables automatic checkpoints by default, however, because automatic checkpoints are created on bootup, it takes a while during boot and shutdown to merge the checkpoints.

I don't think there is too much benefit having automatic checkpoints enabled for the minikube VM. It might be a good idea to disable the automatic checkpoints setting when creating the VM in Hyper-V.

Please provide the following details:

Environment:

Minikube version (use minikube version): minikube version: v0.25.2

OS (e.g. from /etc/os-release): Windows 10 64-bit 1709 (latest updates)
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.25.1
Install tools: Docker for Windows, skaffold
Others:

chyperv kinfeature lifecyclrotten

Source

F21

👍3

Most helpful comment

Hey thanks for the issue. I think we can disable this feature.

r2d4 on 9 Apr 2018

❤2 👍2

All 8 comments

Hey thanks for the issue. I think we can disable this feature.

r2d4 on 9 Apr 2018

❤2 👍2

You can change the behaviour using the hyperv manager. At the moment I can not recall if the driver supported this. It is part of libmachine, so @r2d4 this would be one of those improvements we can put on our wishlist.

gbraad on 13 Apr 2018

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 12 Jul 2018

/remove-lifecycle stale

F21 on 12 Jul 2018

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

fejta-bot on 10 Oct 2018

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

fejta-bot on 9 Nov 2018

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

fejta-bot on 9 Dec 2018

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.