Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Minikube installation error-solution #19739

Open
FathimaFazl opened this issue Oct 1, 2024 · 3 comments
Open

Minikube installation error-solution #19739

FathimaFazl opened this issue Oct 1, 2024 · 3 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@FathimaFazl
Copy link

What Happened?

For the error : VT-X/AMD-V should be enabled in BIOS which is mandatory

This cannot be found in my BIOS settings. I tried the below command to resolve this issue and the minikube started normally.

minikube start --no-vtx-check

Attach the log file

Screenshot 2024-10-01 180429

Operating System

Windows

Driver

VirtualBox

@T-Lakshmi
Copy link

@FathimaFazl,
Thanks for raising the issue.

For the error : VT-X/AMD-V should be enabled in BIOS which is mandatory. This cannot be found in my BIOS settings

Unfortunately this is one of the existing bug which not fixed yet but for workarround you can use --no-vtx-check to skip this validation.

--no-vtx-check Disable checking for the availability of hardware virtualization before the vm is started (virtualbox driver only)

@T-Lakshmi
Copy link

Related issues: #4816, #3706, #14017

/kind bug

@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Dec 4, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 4, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

4 participants