Minikube start --vm-driver=virtualbox ---> failed to start virtualbox VM

[Johnstx]

What Happened?

minikube start --vm-driver=virtualbox
😄 minikube v1.33.1 on Ubuntu 22.04
✨ Using the virtualbox driver based on existing profile
👍 Starting "minikube" primary control-plane node in "minikube" cluster
🤷 virtualbox "minikube" VM is missing, will recreate.
🔥 Creating virtualbox VM (CPUs=2, Memory=3000MB, Disk=20000MB) ...
🤦 StartHost failed, but will try again: recreate: creating host: create: creating: write |1: broken pipe
🤷 virtualbox "minikube" VM is missing, will recreate.
🔥 Creating virtualbox VM (CPUs=2, Memory=3000MB, Disk=20000MB) ...
😿 Failed to start virtualbox VM. Running "minikube delete" may fix it: recreate: creating host: create: creating: write |1: broken pipe

❌ Exiting due to GUEST_PROVISION: error provisioning guest: Failed to start host: recreate: creating host: create: creating: write |1: broken pipe

Hey guys, I need some support with fixing this fail i ecountered while running 'minikube start using virtualbox as the vm_driver.'

• I'm using a WSL
• PC virtualization is enabled
• Installed Virtualbox using windows(GUI) and have linked the env of the binary to my /usr/bin/

I'll appreciate any ideas

Attach the log file

minikube logs --file=log.txt

❌ Exiting due to GUEST_STATUS: Unable to get control-plane node minikube host status: state: machine does not exist

Operating System

Windows

Driver

VirtualBox

[kundan2707]

/kind support

[kundan2707]

@Johnstx some instability has been observed with virtualbox in pas too.
can you share version of virtualbox you are using?

[kundan2707]

Try once after deleting minikube and check if it still persists.

[kundan2707]

/triage needs-information

[Johnstx]

@Johnstx some instability has been observed with virtualbox in pas too. can you share version of virtualbox you are using?

Thanks @kundan2707 I'm using the virtualbox 7.0.20

[Johnstx]

Try once after deleting minikube and check if it still persists.

Already deleted and reinstalled. Same problem persists

[k8s-triage-robot]

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