Minikube: virtualbox: Unable to start VM. creating: Maximum number of retries (5) exceeded

[adarsh-m]

I am trying to spin up VM using minikube but facing issue.

The exact command to reproduce the issue
minikube start --vm-driver=virtualbox

The full output of the command that failed:
minikube v1.7.2 on Microsoft Windows 10 Pro 10.0.17763 Build 17763

• Using the virtualbox driver based on user configuration
• Creating virtualbox VM (CPUs=2, Memory=2000MB, Disk=20000MB) ...
  *
  X Unable to start VM. Please investigate and run 'minikube delete' if possible: create: creating: Maximum number of retries (5) exceeded
  *
• minikube is exiting due to an error. If the above message is not useful, open an issue:
  
  
  
  • https://github.com/kubernetes/minikube/issues/new/choose
  
  

The output of the minikube logs command:
command runner: getting ssh client for bootstrapper: Error dialing tcp via ssh client: dial tcp 127.0.0.1:22: connectex: No connection could be made because the target machine actively refused it.
*

• minikube is exiting due to an error. If the above message is not useful, open an issue:
  
  
  
  • https://github.com/kubernetes/minikube/issues/new/choose
  
  

The operating system version: Windows 10 pro

[SaiBalaguru]

I am facing the same issue. Someone please help!

[timramone]

Have the same issue

[s709t]

i'm facing the same issue, this has become annoying, that error doesn't show anything relevant

[premanr]

I am also getting same issue, any workaround?

[SaiBalaguru]

If you are connected to your corporate network - disconnect. So connect to a restriction free one.
Secondly, after creating a kubernetes folder in C drive, type "kubectl config"
then "minikube config" .
Now "minikube start".
Then "minikube SSH".

This helps for Oracle Virtual Box in windows 10.

[derektumulak]

I am running into the same issue here, running HyperV on Windows 10.

[tstromberg]

@adarsh-m - are you still running into this?

It would be helpful to get this information:

minikube start --alsologtostderr -v=3

That should reveal the source of the failure. I'm betting there is a VirtualBox misconfiguration or corruption of some sort.

[tstromberg]

@derektumulak - Sorry to hear that. Please open another issue for non-virtualbox issues, with the output of minikube start --alsologtostderr -v=3.

It would also be helpful to know if minikube start --driver=docker works.

[derektumulak]

Hi Thomas, thank you for the reply but unfortunately I don't have this
environment up and running any longer.

Best,
-Derek

On Thu, Mar 19, 2020 at 12:11 PM Thomas Strömberg [e-mail]
wrote:

@derektumulak https://github.com/derektumulak - Sorry to hear that.
Please open another issue for non-virtualbox issues, with the output of minikube
start --alsologtostderr -v=3.

It would also be helpful to know if minikube start --driver=docker works.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/minikube/issues/6631#issuecomment-601364919,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIHB2XBGK5QODOAGIDLZADRIJU4NANCNFSM4KU7VQLQ
.

[tstromberg]

Closed, as this creation behavior no longer occurs in minikube v1.7.

[VRay27]

@tstromberg Hi, I am facing the same issue.
Windows, Virtual Box
minikube start --vm-driver=virtualbox

Error : libmachine: Error dialing TCP: dial tcp 127.0.0.1:22: connectex: No connection could be made because the target machine actively refused it.

minikube version: v1.12.3

Could you please advise?