machine: add parallels support

[denji]

xhyve will not work on older iMac, CPU core the presence of support VT-d will not help. Paralells works along with VMware Fusion.

1. xhyve will not working without the Hypervisor.framework.
2. Hypervisor.framework will not working VT-x without (EPT & Unrestricted Mode)

Hypervisor.framework

Generally, machines with an Intel VT-x feature set that includes Extended Page Tables (EPT) and Unrestricted Mode are supported. You can determine the availability of Hypervisor APIs on a particular machine at runtime with the sysctl(8) command, passing kern.hv_support as an argument.

• https://developer.apple.com/reference/hypervisor
• https://discussions.apple.com/thread/7663673
• https://twitter.com/couac/status/730119794020732929
• Jenkins - https://github.com/Parallels/jenkins-parallels
• Decide supported virtualization providers #261

[k8s-ci-robot]

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please follow instructions at https://github.com/kubernetes/kubernetes/wiki/CLA-FAQ to sign the CLA.

Once you've signed, please reply here (e.g. "I signed it!") and we'll verify. Thanks.

---

• If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA data and verify that your email is set on your git commits.
• If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.

If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[minikube-bot]

Can one of the admins verify this patch?

[minikube-bot]

Can one of the admins verify this patch?

[codecov-io]

Current coverage is 34.81% (diff: 0.00%)

Merging #953 into master will decrease coverage by 0.07%

@@             master       #953   diff @@
==========================================
  Files            43         43          
  Lines          1978       1982     +4   
  Methods           0          0          
  Messages          0          0          
  Branches          0          0          
==========================================
  Hits            690        690          
- Misses         1152       1156     +4   
  Partials        136        136          

Powered by Codecov. Last update e52833a...cd00210

[denji]

I signed it!

[dlorenc]

@minikube-bot test this please

[dlorenc]

@minikube-bot ok to test

[dlorenc]

Thanks for the PR. We're trying to keep our test matrix low by only supporting a few virtualization systems per platform, but we have had quite a few requests for parallels. Would you mind explaining the benefits of parallels over xhyve? That's where we've been spending most of our time.

[denji]

It's very simple: xhyve will not work on older iMac, CPU core the presence of support VT-d will not help. Paralells works along with VMware Fusion.

1. xhyve will not working without the Hypervisor.framework.
2. Hypervisor.framework will not working VT-x without (EPT & Unrestricted Mode)

Hypervisor.framework

Generally, machines with an Intel VT-x feature set that includes Extended Page Tables (EPT) and Unrestricted Mode are supported. You can determine the availability of Hypervisor APIs on a particular machine at runtime with the sysctl(8) command, passing kern.hv_support as an argument.
$ sysctl kern.hv_support
kern.hv_support: 0

• https://developer.apple.com/reference/hypervisor
• https://discussions.apple.com/thread/7663673
• https://twitter.com/couac/status/730119794020732929
• Jenkins - https://github.com/Parallels/jenkins-parallels

[cblecker]

I agree with @denji 's points and assessment of the advantages, and would definitely support inclusion of a parallels provider.

[uoryon]

I would definitely support inclusion of a parallels provider, too. And why this pr not proceed to deal with?

[ivanfioravanti]

Any news on this one? Parallels is supported and works very well on Docker-Machine, why shouldn't you include it?

[cadavre]

Bringing this up with +1.

Would you mind explaining the benefits of parallels over xhyve?

I'm not quite aware of any benefits, but you – team Minikube – shall consider one: if someone is already using Parallels for their needs, why one should install another vm if supporting Parallels is so simple according to this PR's commit diff?

[troyfontaine]

It looks like the XHYVE driver overrides the Docker for Mac docker-machine, so if you also still want to use the Docker provided version you may have some hoops to jump through in that regard. With how small of a change it is to support it, is it that bad of a trade off?

[SailingYYC]

+1, Parallels is a performant and supported virtualization platform on Mac. xhyve doesn't seem nearly as stable as Docker's implementation of hypervisor.framework.

[fejta-bot]

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]

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
/remove-lifecycle stale

[troyfontaine]

/remove-lifecycle rotten

[rhooper]

I'm another person that would really like to see parallels support added into minikube.
I really dislike having more than one hypervisor running, as I've run into random networking, hangs, and performance issues when using multiple hypervisors.

[bassam]

+1 for parallels support. If the issue is keeping the test matrix small, then merge this PR and mark parallels support experimental or unsupported.

[fejta-bot]

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]

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

[cadavre]

/remove-lifecycle rotten

[fejta-bot]

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

[troyfontaine]

/remove-lifecycle stale

[tstromberg]

mind addressing the merge conflicts? I'd like to see about getting this included as an experimental driver (meaning: not initially covered by our CI)

[RA489]

@denji This PR needs rebase. Also Please look at the failing tests.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: denji
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: tstromberg

If they are not already assigned, you can assign the PR to them by writing /assign @tstromberg in a comment when ready.

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[tstromberg]

Thank you for your contribution!