no workaround for minikube start up on win 10 home

[atanu2531]

Error: [VBOX_VTX_DISABLED] create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory

C:>minikube start

• minikube v1.6.2 on Microsoft Windows 10 Home Single Language 10.0.18362 Build 18362
• Selecting 'virtualbox' driver from existing profile (alternates: [])
• Creating virtualbox VM (CPUs=2, Memory=2000MB, Disk=20000MB) ...

X Unable to start VM. Please investigate and run 'minikube delete' if possible

• Error: [VBOX_VTX_DISABLED] create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory
• Suggestion: Virtualization support is disabled on your computer. If you are running minikube within a VM, try '--vm-driver=none'. Otherwise, consult your systems BIOS manual for how to enable virtualization.
• Related issues:
  • Unable to start VM: create: precreate: This computer doesn't have VT-X/AMD-v enabled. Enabling it in the BIOS is mandatory minikube#3900
  • Better documentation needed for virtual desktop minikube#4730
• If the above advice does not help, please let us know:
  • https://github.com/kubernetes/minikube/issues/new/choose

[sftim]

It sounds like you need a computer with hardware virtualization enabled @atanu2531
Are you able to try enabling that and see if it helps?

/triage support

[erchauhannitin]

Facing same issue and i don't have access to BIOS password.
I disabled it by mistake by running one command( though it still shows Virtualization enabled in Task Manager, Performance Tab). Now minikube start is giving errors in win 10 and does not see any work around.

[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

[fejta-bot]

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

[k8s-ci-robot]

@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.