Minishift doesn't recognize --virtualbox-no-vtx-check or --no-vtx-check

[Larswa]

General information

• Minishift version: v1.34.3+4b58f89
• OS: Linux / macOS / Windows Windows 10 Pro 20H2 19042.685
• Hypervisor: KVM / Hyper-V / VirtualBox / hyperkit HyperV installed along with VirtualBox V 6.1.16

Steps to reproduce

Since earlier this year, Virtualbox 6.1.x has been working with and using the Hyper-V API that Windows 10 Pro exposes. This means that we can run a Virtualbox on windows with HyperV installed (and active). I use that with Minikube and vagrant. With minikube I need to use the --no-vtx-check when starting, like this:
minikube start --vm-driver virtualbox --no-vtx-check

And then I get a nice Virtual box machine with all the goodness of Virtual Box networking. (As HyperV networking api is non existant, I prefer this)

Expected

When I do the same with minishift, I would expect the same result.

minishift start --vm-driver virtualbox --no-vtx-check
or
minishift start --vm-driver virtualbox --virtualbox-no-vtx-check

gives the errors below:

Actual

I get an error unknown flag: --no-vtx-check or in the last case unknown flag: --virtualbox-no-vtx-check

I don't understand that, because if I do this:
minishift start --vm-driver virtualbox I get this error.
Either use Hyper-V as a driver, or disable the Hyper-V hypervisor. (To skip this check, use --virtualbox-no-vtx-check)
But that flag doesnt work as shown above.

Are these "Ignore vtx" flags not implemented in Minishift?

Logs

You can start Minishift with minishift start --show-libmachine-logs -v5 to collect logs.
Please consider posting this on http://gist.github.com/ and post the link in the issue.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.