trying to run minikube on Mac M1 Pro Silicone getting an error to start

InessTaefAkamai commented 4 months ago

What Happened?

minikube start

😄 minikube v1.33.1 on Darwin 14.4.1 (arm64) ✨ Using the qemu2 driver based on existing profile 💿 Downloading VM boot image ...

minikube-v1.33.1-arm64.iso....: 65 B / 65 B [---------] 100.00% ? p/s 0s minikube-v1.33.1-arm64.iso: 361.99 MiB / 361.99 MiB 100.00% 12.23 MiB p 👍 Starting "minikube" primary control-plane node in "minikube" cluster 🔄 Restarting existing qemu2 VM for "minikube" ... OUTPUT: ERROR: qemu-system-x86_64: -accel hvf: Unknown Error

🤦 StartHost failed, but will try again: driver start: qemu-system-x86_64: -accel hvf: Unknown Error: exit status 1 🔄 Restarting existing qemu2 VM for "minikube" ... OUTPUT: ERROR: qemu-system-x86_64: -accel hvf: Unknown Error

😿 Failed to start qemu2 VM. Running "minikube delete" may fix it: driver start: qemu-system-x86_64: -accel hvf: Unknown Error: exit status 1

❌ Exiting due to GUEST_PROVISION: error provisioning guest: Failed to start host: driver start: qemu-system-x86_64: -accel hvf: Unknown Error: exit status 1

╭───────────────────────────────────────────────────────────────────────────────────────────╮ │ │ │ 😿 If the above advice does not help, please let us know: │ │ 👉 https://github.com/kubernetes/minikube/issues/new/choose │ │ │ │ Please run minikube logs --file=logs.txt and attach logs.txt to the GitHub issue. │ │ │ ╰───────────────────────────────────────────────────────────────────────────────────────────╯

Attach the log file

logs.txt

Operating System

macOS (Default)

Driver

None

spowelljr commented 4 months ago

Hi @InessTaefAkamai, I'm not quite sure how your minikube is trying to use qemu-system-x86_64 since that's only set on amd64.

        case "amd64":
                return "qemu-system-x86_64", nil

Could you try deleting the cluster with minikube delete and then try starting the cluster again and see if that resolves your isssue.

k8s-triage-robot commented 1 month ago

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

spowelljr commented 1 month ago

Hi @InessTaefAkamai, we haven't heard back from you, do you still have this issue? There isn't enough information in this issue to make it actionable, and a long enough duration has passed, so this issue is likely difficult to replicate.

I will close this issue for now but feel free to reopen when you feel ready to provide more information.

kubernetes / minikube