medyagh
commented
3 years ago Hi @harskum we dont have integration tests for vmware, I wonder if you have tried our Docker driver ? that is our most prefered driver if you install docker.
Closed harskum closed 3 years ago
medyagh
commented
3 years ago Hi @harskum we dont have integration tests for vmware, I wonder if you have tried our Docker driver ? that is our most prefered driver if you install docker.
tstromberg
commented
3 years ago This seems to be the crux of the matter:
executing: /Applications/VMware Fusion.app/Contents/Public/vmrun start /Users/harshit/.minikube/machines/minikube/minikube.vmx nogui
ServiceImpl_Opener: PID 7197
Error: The operation was canceledIf you manually run this command, what happens:
"/Applications/VMware Fusion.app/Contents/Public/vmrun" start /Users/harshit/.minikube/machines/minikube/minikube.vmx nogui
harskum
commented
3 years ago @tstromberg I get the same error if I run the command you gave
medyagh
commented
3 years ago @harskum we had a few updates for our vmware driver, have u tried latets version of minikube? Meanwhile have you tried out newest driver Docker Driver with latest version of minikube? you could try minikube delete minikube start --driver=docker
for more information on the docker driver checkout: https://minikube.sigs.k8s.io/docs/drivers/docker/
harskum
commented
3 years ago @medyagh I have been using docker as a workaround, which is working fine for my use case. Thanks everyone for looking into this! I'll go ahead and close this issue.
EricoCartmanez
commented
3 years ago If you have Virtual Box installed:
minikube delete
minikube start --driver=virtualbox
Scanz-beep
commented
3 years ago VMware Workstation 16 Player
minikube start --driver vmware
* minikube v1.22.0 on Microsoft Windows 10 Enterprise 10.0.18363 Build 18363
* Using the vmware driver based on user configuration
* Downloading VM boot image ...
> minikube-v1.22.0.iso.sha256: 65 B / 65 B [-------------] 100.00% ? p/s 0s
> minikube-v1.22.0.iso: 242.95 MiB / 242.95 MiB [] 100.00% 8.09 MiB p/s 30s
* Starting control plane node minikube in cluster minikube
* Downloading Kubernetes v1.21.2 preload ...
> preloaded-images-k8s-v11-v1...: 502.14 MiB / 502.14 MiB 100.00% 8.11 MiB
* 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
X 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, abortingFunny thing latest minikube version advises to use vmware driver instead of my existing virtualbox driver (which I chose because of this problem)
And the problem is still there....
langyan1022
commented
2 years ago I had the same problem. After viewing the debug information, it is found that the status of the virtual machine cannot be obtained normally after starting the virtual machine.
I try to start the virtual machine directly, the virtual machine can start normally （without nogui）
with nogui
But after executing minikube start, the newly opened window executes vmrun.exe list and the result is that there is no running virtual machine，
Below is the log file during execution logs.txt
What should I do to get it working?
jimmbelll
commented
1 year ago I get this error:
X 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
It's because it's using an absolute path name to vmrun.exe, but I installed it elsewhere:
executing: C:\Program Files (x86)\VMware\VMware Workstation\vmrun.exe list
My location is in the path, so if minikube didn't specify the absolute path, it should work.
spowelljr
commented
1 year ago @jimmbelll minikube uses exec.LookPath("vmrun") to get the vmrun binary, that's how it's getting the address in your log. That binary location will exist from the first start of the cluster though as it's saved to the config. Is it possible you started minikube, then moved the location of vmrun and not it doesn't work?
jimmbelll
commented
1 year ago @jimmbelll minikube uses
exec.LookPath("vmrun")to get thevmrunbinary, that's how it's getting the address in your log. That binary location will exist from the first start of the cluster though as it's saved to the config. Is it possible you started minikube, then moved the location ofvmrunand not it doesn't work?
Pretty sure I didn't move it. Can I tweak the config to specify it? (I couldn't figure out how.) Is exec.LookPath() a GO language thing? I could put it in the PATH env before firing it up? (Pretty sure I tried that though.) Thanks for the response.
This is my first time using minikube, so forgive me if this issue is trivial. I tried searching for a solution, but couldn't find anything helpful. I tried doing
minikube deletebefore runningminikube start, but I am hitting the same issue. I have given all permissions to VMWare Fusion in system preferences, and also, VMWare Fusion is running when I am trying to runminikube start. I tried updating the kvm2 driver too by running the command below, but even that didn't helpcurl -LO https://storage.googleapis.com/minikube/releases/latest/docker-machine-driver-kvm2 \ && sudo install docker-machine-driver-kvm2 /usr/local/bin/Steps to reproduce the issue:
minikube startFull output of failed command:
Full output of
minikube startcommand used, if not already included:Optional: Full output of
minikube logscommand: