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

Exiting due to GUEST_PROVISION: Failed to start host: creating host: create: creating: Machine didn't return an IP after 120 seconds #9381

Closed
obaidomer opened this issue Oct 2, 2020 · 5 comments
Labels
co/vmwarefusion-driver Issues with legacy VMware Fusion Driver kind/support Categorizes issue or PR as a support question. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.

Comments

@obaidomer
Copy link

obaidomer commented Oct 2, 2020

Steps to reproduce the issue:

  1. installation of minikube on MacOS
  2. run minikube start
  3. below output is thrown back.

MacOS has both VMware Fusion and VirtualBox - both give similar exception.

Full output of failed command:

Full output of minikube start command used, if not already included:

minikube start
😄 minikube v1.13.1 on Darwin 11.0
✨ Automatically selected the vmwarefusion driver
👍 Starting control plane node minikube in cluster minikube
❗ The vmwarefusion driver is deprecated and support for it will be removed in a future release.
Please consider switching to the new vmware unified driver, which is intended to replace the vmwarefusion driver.
See https://minikube.sigs.k8s.io/docs/reference/drivers/vmware/ for more information.
To disable this message, run [minikube config set ShowDriverDeprecationNotification false]
🔥 Creating vmwarefusion VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
🔥 Deleting "minikube" in vmwarefusion ...
🤦 StartHost failed, but will try again: creating host: create: creating: Machine didn't return an IP after 120 seconds, aborting
❗ The vmwarefusion driver is deprecated and support for it will be removed in a future release.
Please consider switching to the new vmware unified driver, which is intended to replace the vmwarefusion driver.
See https://minikube.sigs.k8s.io/docs/reference/drivers/vmware/ for more information.
To disable this message, run [minikube config set ShowDriverDeprecationNotification false]
🔥 Creating vmwarefusion VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
😿 Failed to start vmwarefusion VM. Running "minikube delete" may fix it: creating host: create: creating: Machine didn't return an IP after 120 seconds, aborting

❌ Exiting due to GUEST_PROVISION: Failed to start host: creating host: create: creating: Machine didn't return an IP after 120 seconds, aborting

😿 If the above advice does not help, please let us know:
👉 https://github.com/kubernetes/minikube/issues/new/choose

Optional: Full output of minikube logs command:

@obaidomer obaidomer changed the title Exiting due to GUEST_PROVISION: Failed to start host: creating host: create: creating: Machine didn't return an IP after 120 seconds, aborting Exiting due to GUEST_PROVISION: Failed to start host: creating host: create: creating: Machine didn't return an IP after 120 seconds Oct 3, 2020
@priyawadhwa priyawadhwa added the kind/support Categorizes issue or PR as a support question. label Oct 5, 2020
@sharifelgamal
Copy link
Collaborator

Yeah the vmwarefusion driver is no longer supported at all, I'd suggest trying the vmware driver instead.

@sharifelgamal sharifelgamal added co/vmwarefusion-driver Issues with legacy VMware Fusion Driver priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done. labels Oct 12, 2020
@obaidomer
Copy link
Author

Yeah the vmwarefusion driver is no longer supported at all, I'd suggest trying the vmware driver instead.

Please share the link/steps to do so on Mac.

@priyawadhwa
Copy link

Hey @obaidomer our documentation website: https://minikube.sigs.k8s.io/

Info on the vmware driver can be found here: https://minikube.sigs.k8s.io/docs/drivers/vmware/

@priyawadhwa
Copy link

Please let us know if this resolves your issue.

@obaidomer
Copy link
Author

Hi @priyawadhwa, Thank you for the documentation,

the same error occurred. For now, I have created individual VM's and moved on.

here are the logs.

minikube start --driver=vmware
😄 minikube v1.13.1 on Darwin 11.0
✨ Using the vmware driver based on user configuration
👍 Starting control plane node minikube in cluster minikube
🔥 Creating vmware VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
🔥 Deleting "minikube" in vmware ...
🤦 StartHost failed, but will try again: creating host: create: Error creating machine: Error in driver during machine creation: Machine didn't return an IP after 120 seconds, aborting
🔥 Creating vmware VM (CPUs=2, Memory=2200MB, Disk=20000MB) ...
😿 Failed to start vmware VM. Running "minikube delete" may fix it: creating host: create: Error creating machine: Error in driver during machine creation: Machine didn't return an IP after 120 seconds, aborting

❌ Exiting due to DRV_NO_IP: Failed to start host: creating host: create: Error creating machine: Error in driver during machine creation: Machine didn't return an IP after 120 seconds, aborting
💡 Suggestion: Check your firewall rules for interference, and run 'virt-host-validate' to check for KVM configuration issues. If you are running minikube within a VM, consider using --driver=none
📘 Documentation: https://minikube.sigs.k8s.io/docs/reference/drivers/kvm2/
🍿 Related issues:
#4249
#3566

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
co/vmwarefusion-driver Issues with legacy VMware Fusion Driver kind/support Categorizes issue or PR as a support question. priority/awaiting-more-evidence Lowest priority. Possibly useful, but not yet enough support to actually get it done.
Projects
None yet
Development

No branches or pull requests

3 participants