minikube with VMWare Workstation - IP not found for MAC 00:0c:29:6f:1e:d2 in DHCP leases

[mudskipperwathotmail]

hi there, I tried to start minikube with VMWare Workstation (15.1.0 on windows 10). and got the err below. and the content of the workstation net conf file attached after. any ideas? thanks.

===minikube error msg:

C:\WINDOWS\system32>minikube start --driver vmware

• minikube v1.25.2 on Microsoft Windows 10 Enterprise 10.0.18363 Build 18363
• Using the vmware driver based on existing profile
• Starting control plane node minikube in cluster minikube
• Updating the running vmware "minikube" VM ... ! StartHost failed, but will try again: provision: IP not found for MAC 00:0c:29:6f:1e:d2 in DHCP leases
• Updating the running vmware "minikube" VM ...

===vmware workstation net conf

#

Configuration file for VMware port of ISC 2.0 release running on

Windows.

#

This file is generated by the VMware installation procedure; it

is edited each time you add or delete a VMware host-only network

adapter.

#

We set domain-name-servers to make some clients happy

(dhclient as configued in SuSE, TurboLinux, etc.).

We also supply a domain name to make pump (Red Hat 6.x) happy.

# allow unknown-clients; default-lease-time 1800; # default is 30 minutes max-lease-time 7200; # default is 2 hours

Virtual ethernet segment 1

Added at 03/14/20 09:30:46

subnet 192.168.111.0 netmask 255.255.255.0 { range 192.168.111.128 192.168.111.254; # default allows up to 125 VM's option broadcast-address 192.168.111.255; option domain-name-servers 192.168.111.1; option domain-name "localdomain"; default-lease-time 1800; max-lease-time 7200; } host VMnet1 { hardware ethernet 00:50:56:C0:00:01; fixed-address 192.168.111.1; option domain-name-servers 0.0.0.0; option domain-name ""; }

End

Virtual ethernet segment 8

Added at 03/14/20 09:30:46

subnet 192.168.74.0 netmask 255.255.255.0 { range 192.168.74.128 192.168.74.254; # default allows up to 125 VM's option broadcast-address 192.168.74.255; option domain-name-servers 192.168.74.2; option domain-name "localdomain"; option netbios-name-servers 192.168.74.2; option routers 192.168.74.2; default-lease-time 1800; max-lease-time 7200; } host VMnet8 { hardware ethernet 00:50:56:C0:00:08; fixed-address 192.168.74.1; option domain-name-servers 0.0.0.0; option domain-name ""; option routers 0.0.0.0; }

End

[spowelljr]

Hi @mudskipperwathotmail, thanks fore reporting your issue with minikube!

I'll need more in-depth minikube logging to be able to debug this issue, could you please run minikube logs --file=logs.txt and then upload the log file to this issue, thanks!

[mudskipperwathotmail]

hi Steven, thanks so much for looking into it. here is the log file, i also pasted the content of the vmnetdhcp.leases file below as to be compared with the vmnetdhcp.conf:

• ==> Audit <==

• ---------	------	----------	---------------------	---------	--------------------------------	--------------------------------		Command	Args	Profile	User	Version	Start Time	End Time
  --help		minikube	DESKTOP-KUNRATV\mud	v1.25.2	Tue, 22 Mar 2022 16:01:54 AEDT	Tue, 22 Mar 2022 16:01:54 AEDT
  delete		minikube	DESKTOP-KUNRATV\mud	v1.25.2	Tue, 22 Mar 2022 19:22:16 AEDT	Tue, 22 Mar 2022 19:22:21 AEDT
  ---------	------	----------	---------------------	---------	--------------------------------	--------------------------------

• ==> Last Start <==

• Log file created at: 2022/03/28 22:59:14 Running on machine: DESKTOP-KUNRATV Binary: Built with gc go1.17.7 for windows/amd64 Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg I0328 22:59:14.930300 6216 out.go:297] Setting OutFile to fd 88 ... I0328 22:59:14.933296 6216 out.go:344] TERM=,COLORTERM=, which probably does not support color I0328 22:59:14.933296 6216 out.go:310] Setting ErrFile to fd 92... I0328 22:59:14.933296 6216 out.go:344] TERM=,COLORTERM=, which probably does not support color I0328 22:59:15.033512 6216 out.go:304] Setting JSON to false I0328 22:59:15.042636 6216 start.go:112] hostinfo: {"hostname":"DESKTOP-KUNRATV","uptime":545195,"bootTime":1647923560,"procs":210,"os":"windows","platform":"Microsoft Windows 10 Enterprise","platformFamily":"Standalone Workstation","platformVersion":"10.0.18363 Build 18363","kernelVersion":"10.0.18363 Build 18363","kernelArch":"x86_64","virtualizationSystem":"","virtualizationRole":"","hostId":"5c907cdf-74ca-4e61-9d02-96233e85c715"} W0328 22:59:15.042636 6216 start.go:120] gopshost.Virtualization returned error: not implemented yet I0328 22:59:15.139096 6216 out.go:176] minikube v1.25.2 on Microsoft Windows 10 Enterprise 10.0.18363 Build 18363 I0328 22:59:15.202841 6216 notify.go:193] Checking for updates... I0328 22:59:15.212867 6216 config.go:176] Loaded profile config "minikube": Driver=vmware, ContainerRuntime=docker, KubernetesVersion=v1.23.3 I0328 22:59:15.289561 6216 main.go:130] libmachine: Found binary path at C:\Program Files\docker-machine-driver\docker-machine-driver-vmware.exe I0328 22:59:15.292642 6216 main.go:130] libmachine: Launching plugin server for driver vmware I0328 22:59:19.143408 6216 main.go:130] libmachine: Plugin server listening at address 127.0.0.1:63810 I0328 22:59:19.153531 6216 main.go:130] libmachine: () Calling .GetVersion I0328 22:59:19.157534 6216 main.go:130] libmachine: Using API Version 1 I0328 22:59:19.157534 6216 main.go:130] libmachine: () Calling .SetConfigRaw I0328 22:59:19.158536 6216 main.go:130] libmachine: () Calling .GetMachineName I0328 22:59:19.158536 6216 main.go:130] libmachine: (minikube) Calling .DriverName I0328 22:59:19.160528 6216 driver.go:344] Setting default libvirt URI to qemu:///system I0328 22:59:19.235959 6216 main.go:130] libmachine: Found binary path at C:\Program Files\docker-machine-driver\docker-machine-driver-vmware.exe I0328 22:59:19.235959 6216 main.go:130] libmachine: Launching plugin server for driver vmware I0328 22:59:19.296987 6216 main.go:130] libmachine: Plugin server listening at address 127.0.0.1:63812 I0328 22:59:19.301092 6216 main.go:130] libmachine: () Calling .GetVersion I0328 22:59:19.301946 6216 main.go:130] libmachine: Using API Version 1 I0328 22:59:19.301946 6216 main.go:130] libmachine: () Calling .SetConfigRaw I0328 22:59:19.302464 6216 main.go:130] libmachine: () Calling .GetMachineName I0328 22:59:19.303184 6216 main.go:130] libmachine: (minikube) Calling .DriverName I0328 22:59:19.382311 6216 out.go:176] Using the vmware driver based on existing profile I0328 22:59:19.392360 6216 start.go:281] selected driver: vmware I0328 22:59:19.392360 6216 start.go:798] validating driver "vmware" against &{Name:minikube KeepContext:false EmbedCerts:false MinikubeISO:https://storage.googleapis.com/minikube/iso/minikube-v1.25.2.iso KicBaseImage:gcr.io/k8s-minikube/kicbase:v0.0.30@sha256:02c921df998f95e849058af14de7045efc3954d90320967418a0d1f182bbc0b2 Memory:4000 CPUs:2 DiskSize:20000 VMDriver: Driver:vmware HyperkitVpnKitSock: HyperkitVSockPorts:[] DockerEnv:[] ContainerVolumeMounts:[] InsecureRegistry:[] RegistryMirror:[] HostOnlyCIDR:192.168.59.1/24 HypervVirtualSwitch: HypervUseExternalSwitch:false HypervExternalAdapter: KVMNetwork:default KVMQemuURI:qemu:///system KVMGPU:false KVMHidden:false KVMNUMACount:1 DockerOpt:[] DisableDriverMounts:false NFSShare:[] NFSSharesRoot:/nfsshares UUID: NoVTXCheck:false DNSProxy:false HostDNSResolver:true HostOnlyNicType:virtio NatNicType:virtio SSHIPAddress: SSHUser:root SSHKey: SSHPort:22 KubernetesConfig:{KubernetesVersion:v1.23.3 ClusterName:minikube Namespace:default APIServerName:minikubeCA APIServerNames:[] APIServerIPs:[] DNSDomain:cluster.local ContainerRuntime:docker CRISocket: NetworkPlugin: FeatureGates: ServiceCIDR:10.96.0.0/12 ImageRepository: LoadBalancerStartIP: LoadBalancerEndIP: CustomIngressCert: ExtraOptions:[{Component:kubelet Key:housekeeping-interval Value:5m}] ShouldLoadCachedImages:true EnableDefaultCNI:false CNI: NodeIP: NodePort:8443 NodeName:} Nodes:[{Name: IP: Port:8443 KubernetesVersion:v1.23.3 ContainerRuntime:docker ControlPlane:true Worker:true}] Addons:map[] CustomAddonImages:map[] CustomAddonRegistries:map[] VerifyComponents:map[apiserver:true system_pods:true] StartHostTimeout:6m0s ScheduledStop: ExposedPorts:[] ListenAddress: Network: MultiNodeRequested:false ExtraDisks:0 CertExpiration:26280h0m0s Mount:false MountString:C:\Users\mud:/minikube-host Mount9PVersion:9p2000.L MountGID:docker MountIP: MountMSize:262144 MountOptions:[] MountPort:0 MountType:9p MountUID:docker BinaryMirror: DisableOptimizations:false} I0328 22:59:19.425722 6216 start.go:809] status for vmware: {Installed:true Healthy:true Running:false NeedsImprovement:false Error: Reason: Fix: Doc: Version:} I0328 22:59:19.706343 6216 cni.go:93] Creating CNI manager for "" I0328 22:59:19.706343 6216 cni.go:167] CNI unnecessary in this configuration, recommending no CNI I0328 22:59:19.706343 6216 start_flags.go:302] config: {Name:minikube KeepContext:false EmbedCerts:false MinikubeISO:https://storage.googleapis.com/minikube/iso/minikube-v1.25.2.iso KicBaseImage:gcr.io/k8s-minikube/kicbase:v0.0.30@sha256:02c921df998f95e849058af14de7045efc3954d90320967418a0d1f182bbc0b2 Memory:4000 CPUs:2 DiskSize:20000 VMDriver: Driver:vmware HyperkitVpnKitSock: HyperkitVSockPorts:[] DockerEnv:[] ContainerVolumeMounts:[] InsecureRegistry:[] RegistryMirror:[] HostOnlyCIDR:192.168.59.1/24 HypervVirtualSwitch: HypervUseExternalSwitch:false HypervExternalAdapter: KVMNetwork:default KVMQemuURI:qemu:///system KVMGPU:false KVMHidden:false KVMNUMACount:1 DockerOpt:[] DisableDriverMounts:false NFSShare:[] NFSSharesRoot:/nfsshares UUID: NoVTXCheck:false DNSProxy:false HostDNSResolver:true HostOnlyNicType:virtio NatNicType:virtio SSHIPAddress: SSHUser:root SSHKey: SSHPort:22 KubernetesConfig:{KubernetesVersion:v1.23.3 ClusterName:minikube Namespace:default APIServerName:minikubeCA APIServerNames:[] APIServerIPs:[] DNSDomain:cluster.local ContainerRuntime:docker CRISocket: NetworkPlugin: FeatureGates: ServiceCIDR:10.96.0.0/12 ImageRepository: LoadBalancerStartIP: LoadBalancerEndIP: CustomIngressCert: ExtraOptions:[{Component:kubelet Key:housekeeping-interval Value:5m}] ShouldLoadCachedImages:true EnableDefaultCNI:false CNI: NodeIP: NodePort:8443 NodeName:} Nodes:[{Name: IP: Port:8443 KubernetesVersion:v1.23.3 ContainerRuntime:docker ControlPlane:true Worker:true}] Addons:map[] CustomAddonImages:map[] CustomAddonRegistries:map[] VerifyComponents:map[apiserver:true system_pods:true] StartHostTimeout:6m0s ScheduledStop: ExposedPorts:[] ListenAddress: Network: MultiNodeRequested:false ExtraDisks:0 CertExpiration:26280h0m0s Mount:false MountString:C:\Users\mud:/minikube-host Mount9PVersion:9p2000.L MountGID:docker MountIP: MountMSize:262144 MountOptions:[] MountPort:0 MountType:9p MountUID:docker BinaryMirror: DisableOptimizations:false} I0328 22:59:19.708342 6216 iso.go:123] acquiring lock: {Name:mk951fe2280e431bf0b2c2a5b8c92a1f98347429 Clock:{} Delay:500ms Timeout:10m0s Cancel:} I0328 22:59:20.236303 6216 out.go:176] Starting control plane node minikube in cluster minikube I0328 22:59:20.237259 6216 preload.go:132] Checking if preload exists for k8s version v1.23.3 and runtime docker I0328 22:59:20.254229 6216 preload.go:148] Found local preload: C:\Users\mud.minikube\cache\preloaded-tarball\preloaded-images-k8s-v17-v1.23.3-docker-overlay2-amd64.tar.lz4 I0328 22:59:20.255299 6216 cache.go:57] Caching tarball of preloaded images I0328 22:59:20.257648 6216 preload.go:174] Found C:\Users\mud.minikube\cache\preloaded-tarball\preloaded-images-k8s-v17-v1.23.3-docker-overlay2-amd64.tar.lz4 in cache, skipping download I0328 22:59:20.257648 6216 cache.go:60] Finished verifying existence of preloaded tar for v1.23.3 on docker I0328 22:59:20.258166 6216 profile.go:148] Saving config to C:\Users\mud.minikube\profiles\minikube\config.json ... I0328 22:59:20.264571 6216 cache.go:208] Successfully downloaded all kic artifacts I0328 22:59:20.275562 6216 start.go:313] acquiring machines lock for minikube: {Name:mk37cf32262a030d3afda08677a6863da3870a22 Clock:{} Delay:500ms Timeout:13m0s Cancel:} I0328 22:59:20.275562 6216 start.go:317] acquired machines lock for "minikube" in 0s I0328 22:59:20.275562 6216 start.go:93] Skipping create...Using existing machine configuration I0328 22:59:20.275562 6216 fix.go:55] fixHost starting: I0328 22:59:20.306628 6216 main.go:130] libmachine: Found binary path at C:\Program Files\docker-machine-driver\docker-machine-driver-vmware.exe I0328 22:59:20.306628 6216 main.go:130] libmachine: Launching plugin server for driver vmware I0328 22:59:20.340046 6216 main.go:130] libmachine: Plugin server listening at address 127.0.0.1:63814 I0328 22:59:20.341412 6216 main.go:130] libmachine: () Calling .GetVersion I0328 22:59:20.341924 6216 main.go:130] libmachine: Using API Version 1 I0328 22:59:20.341924 6216 main.go:130] libmachine: () Calling .SetConfigRaw I0328 22:59:20.342919 6216 main.go:130] libmachine: () Calling .GetMachineName I0328 22:59:20.342919 6216 main.go:130] libmachine: (minikube) Calling .DriverName I0328 22:59:20.343919 6216 main.go:130] libmachine: (minikube) Calling .GetState I0328 22:59:20.351247 6216 main.go:130] libmachine: (minikube) DBG | executing: C:\Program Files (x86)\VMware\VMware Workstation\vmrun.exe list I0328 22:59:21.163051 6216 main.go:130] libmachine: (minikube) DBG | Total running VMs: 3 I0328 22:59:21.163051 6216 main.go:130] libmachine: (minikube) DBG | C:\Users\mud.minikube\machines\minikube\minikube.vmx I0328 22:59:21.163051 6216 main.go:130] libmachine: (minikube) DBG | E:\SZ_Apps\VMWare\Windows Server 2016\Windows Server 2016.vmx I0328 22:59:21.163051 6216 main.go:130] libmachine: (minikube) DBG | E:\SZ_Apps\VMWare\Win7\Windows 7 x64.vmx I0328 22:59:21.198209 6216 fix.go:108] recreateIfNeeded on minikube: state=Running err= W0328 22:59:21.198209 6216 fix.go:134] unexpected machine state, will restart: I0328 22:59:21.204206 6216 out.go:176] Updating the running vmware "minikube" VM ... I0328 22:59:21.204206 6216 main.go:130] libmachine: (minikube) Calling .DriverName I0328 22:59:21.205207 6216 machine.go:88] provisioning docker machine ... I0328 22:59:21.205207 6216 main.go:130] libmachine: (minikube) Calling .DriverName I0328 22:59:21.205207 6216 main.go:130] libmachine: (minikube) Calling .GetMachineName I0328 22:59:21.206208 6216 buildroot.go:166] provisioning hostname "minikube" I0328 22:59:21.206208 6216 main.go:130] libmachine: (minikube) Calling .GetMachineName I0328 22:59:21.207205 6216 main.go:130] libmachine: (minikube) Calling .GetSSHHostname I0328 22:59:21.210205 6216 main.go:130] libmachine: (minikube) DBG | executing: C:\Program Files (x86)\VMware\VMware Workstation\vmrun.exe list I0328 22:59:22.027098 6216 main.go:130] libmachine: (minikube) DBG | Total running VMs: 3 I0328 22:59:22.027098 6216 main.go:130] libmachine: (minikube) DBG | C:\Users\mud.minikube\machines\minikube\minikube.vmx I0328 22:59:22.027098 6216 main.go:130] libmachine: (minikube) DBG | E:\SZ_Apps\VMWare\Windows Server 2016\Windows Server 2016.vmx I0328 22:59:22.027098 6216 main.go:130] libmachine: (minikube) DBG | E:\SZ_Apps\VMWare\Win7\Windows 7 x64.vmx I0328 22:59:22.064233 6216 main.go:130] libmachine: (minikube) DBG | executing: C:\Program Files (x86)\VMware\VMware Workstation\vmrun.exe getGuestIPAddress C:\Users\mud.minikube\machines\minikube\minikube.vmx -wait I0328 22:59:52.151817 6216 main.go:130] libmachine: (minikube) DBG | MAC address in VMX: 00:0c:29:6f:1e:d2 I0328 22:59:52.154859 6216 main.go:130] libmachine: (minikube) DBG | Trying to find IP address in configuration file: C:\ProgramData\VMware\vmnetdhcp.conf I0328 22:59:52.174853 6216 main.go:130] libmachine: (minikube) DBG | Following IPs found map[00:50:56:c0:00:01:192.168.111.1 00:50:56:c0:00:08:192.168.74.1] I0328 22:59:52.174853 6216 main.go:130] libmachine: (minikube) DBG | Trying to find IP address in leases file: C:\ProgramData\VMware\vmnetdhcp.leases I0328 22:59:52.224367 6216 machine.go:91] provisioned docker machine in 30.9802864s I0328 22:59:52.279730 6216 fix.go:57] fixHost completed within 32.0041678s I0328 22:59:52.279730 6216 start.go:80] releasing machines lock for "minikube", held for 32.0041678s W0328 22:59:52.296249 6216 start.go:570] error starting host: provision: IP not found for MAC 00:0c:29:6f:1e:d2 in DHCP leases W0328 22:59:52.307243 6216 out.go:241] ! StartHost failed, but will try again: provision: IP not found for MAC 00:0c:29:6f:1e:d2 in DHCP leases I0328 22:59:52.308236 6216 start.go:585] Will try again in 5 seconds ... I0328 22:59:57.309124 6216 start.go:313] acquiring machines lock for minikube: {Name:mk37cf32262a030d3afda08677a6863da3870a22 Clock:{} Delay:500ms Timeout:13m0s Cancel:} I0328 22:59:57.309797 6216 start.go:317] acquired machines lock for "minikube" in 672.1µs I0328 22:59:57.309797 6216 start.go:93] Skipping create...Using existing machine configuration I0328 22:59:57.309797 6216 fix.go:55] fixHost starting: I0328 22:59:57.334786 6216 main.go:130] libmachine: Found binary path at C:\Program Files\docker-machine-driver\docker-machine-driver-vmware.exe I0328 22:59:57.334786 6216 main.go:130] libmachine: Launching plugin server for driver vmware I0328 22:59:57.371821 6216 main.go:130] libmachine: Plugin server listening at address 127.0.0.1:63826 I0328 22:59:57.374437 6216 main.go:130] libmachine: () Calling .GetVersion I0328 22:59:57.375372 6216 main.go:130] libmachine: Using API Version 1 I0328 22:59:57.375372 6216 main.go:130] libmachine: () Calling .SetConfigRaw I0328 22:59:57.375905 6216 main.go:130] libmachine: () Calling .GetMachineName I0328 22:59:57.375905 6216 main.go:130] libmachine: (minikube) Calling .DriverName I0328 22:59:57.376422 6216 main.go:130] libmachine: (minikube) Calling .GetState I0328 22:59:57.377452 6216 main.go:130] libmachine: (minikube) DBG | executing: C:\Program Files (x86)\VMware\VMware Workstation\vmrun.exe list I0328 22:59:57.920957 6216 main.go:130] libmachine: (minikube) DBG | Total running VMs: 3 I0328 22:59:57.920957 6216 main.go:130] libmachine: (minikube) DBG | C:\Users\mud.minikube\machines\minikube\minikube.vmx I0328 22:59:57.920957 6216 main.go:130] libmachine: (minikube) DBG | E:\SZ_Apps\VMWare\Windows Server 2016\Windows Server 2016.vmx I0328 22:59:57.920957 6216 main.go:130] libmachine: (minikube) DBG | E:\SZ_Apps\VMWare\Win7\Windows 7 x64.vmx I0328 22:59:57.944946 6216 fix.go:108] recreateIfNeeded on minikube: state=Running err= W0328 22:59:57.944946 6216 fix.go:134] unexpected machine state, will restart: I0328 22:59:57.950202 6216 out.go:176] * Updating the running vmware "minikube" VM ... I0328 22:59:57.950202 6216 main.go:130] libmachine: (minikube) Calling .DriverName I0328 22:59:57.950778 6216 machine.go:88] provisioning docker machine ... I0328 22:59:57.950778 6216 main.go:130] libmachine: (minikube) Calling .DriverName I0328 22:59:57.950778 6216 main.go:130] libmachine: (minikube) Calling .GetMachineName I0328 22:59:57.950778 6216 buildroot.go:166] provisioning hostname "minikube" I0328 22:59:57.950778 6216 main.go:130] libmachine: (minikube) Calling .GetMachineName I0328 22:59:57.950778 6216 main.go:130] libmachine: (minikube) Calling .GetSSHHostname I0328 22:59:57.951817 6216 main.go:130] libmachine: (minikube) DBG | executing: C:\Program Files (x86)\VMware\VMware Workstation\vmrun.exe list I0328 22:59:58.531014 6216 main.go:130] libmachine: (minikube) DBG | Total running VMs: 3 I0328 22:59:58.531014 6216 main.go:130] libmachine: (minikube) DBG | C:\Users\mud.minikube\machines\minikube\minikube.vmx I0328 22:59:58.531014 6216 main.go:130] libmachine: (minikube) DBG | E:\SZ_Apps\VMWare\Windows Server 2016\Windows Server 2016.vmx I0328 22:59:58.531014 6216 main.go:130] libmachine: (minikube) DBG | E:\SZ_Apps\VMWare\Win7\Windows 7 x64.vmx I0328 22:59:58.560141 6216 main.go:130] libmachine: (minikube) DBG | executing: C:\Program Files (x86)\VMware\VMware Workstation\vmrun.exe getGuestIPAddress C:\Users\mud.minikube\machines\minikube\minikube.vmx -wait

===vmnetdhcp.leases

All times in this file are in UTC (GMT), not your local timezone. This is

not a bug, so please don't ask about it. There is no portable way to

store leases in the local timezone, so please don't request this as a

feature. If this is inconvenient or confusing to you, we sincerely

apologize. Seriously, though - don't ask.

The format of this file is documented in the dhcpd.leases(5) manual page.

lease 192.168.74.172 { starts 1 2020/03/16 02:52:32; ends 1 2020/03/16 03:22:32; hardware ethernet 00:0c:29:2d:a5:63; client-hostname "ansible"; } lease 192.168.74.171 { starts 6 2020/03/14 10:04:48; ends 6 2020/03/14 10:04:48; abandoned; client-hostname "ansible"; } lease 192.168.74.170 { starts 6 2020/03/14 05:39:05; ends 6 2020/03/14 05:39:05; abandoned; client-hostname "ansible"; } lease 192.168.74.169 { starts 6 2020/03/14 02:04:11; ends 6 2020/03/14 02:34:11; hardware ethernet 00:0c:29:d4:18:ed; client-hostname "sql"; } lease 192.168.74.168 { starts 6 2020/03/14 01:54:19; ends 6 2020/03/14 02:24:19; hardware ethernet 00:0c:29:ee:1f:48; client-hostname "web"; } lease 192.168.74.128 { starts 5 2020/03/13 22:03:22; ends 5 2020/03/13 22:33:22; hardware ethernet 00:0c:29:47:7b:fc; uid 01:00:0c:29:47:7b:fc; client-hostname "WIN-HUP3EM9ROL2"; } lease 192.168.74.132 { starts 2 2020/03/10 02:07:05; ends 2 2020/03/10 02:37:05; hardware ethernet 00:0c:29:20:99:c4; client-hostname "RHEL01"; } lease 192.168.74.167 { starts 2 2020/03/10 00:29:09; ends 2 2020/03/10 00:59:09; hardware ethernet 00:0c:29:11:43:82; uid 01:00:0c:29:11:43:82; client-hostname "DC01"; } lease 192.168.74.166 { starts 1 2020/03/09 05:43:49; ends 1 2020/03/09 05:45:49; hardware ethernet 00:0c:29:11:43:82; uid 01:00:0c:29:11:43:82; client-hostname "DC01"; } lease 192.168.74.165 { starts 1 2020/03/09 05:43:45; ends 1 2020/03/09 05:45:45; hardware ethernet 00:0c:29:11:43:82; uid 01:00:0c:29:11:43:82; client-hostname "DC01"; } lease 192.168.74.164 { starts 1 2020/03/09 05:43:41; ends 1 2020/03/09 05:43:41; abandoned; client-hostname "DC01"; } lease 192.168.74.163 { starts 0 2020/03/08 10:44:44; ends 0 2020/03/08 10:46:44; hardware ethernet 00:0c:29:11:43:82; uid 01:00:0c:29:11:43:82; client-hostname "DC01"; } lease 192.168.74.162 { starts 0 2020/03/08 10:44:40; ends 0 2020/03/08 10:46:40; hardware ethernet 00:0c:29:11:43:82; uid 01:00:0c:29:11:43:82; client-hostname "DC01"; } lease 192.168.74.161 { starts 0 2020/03/08 10:44:36; ends 0 2020/03/08 10:44:36; abandoned; client-hostname "DC01"; } lease 192.168.74.160 { starts 0 2020/03/08 09:03:00; ends 0 2020/03/08 09:05:00; hardware ethernet 00:0c:29:11:43:82; uid 01:00:0c:29:11:43:82; client-hostname "DC01"; } lease 192.168.74.159 { starts 0 2020/03/08 09:02:56; ends 0 2020/03/08 09:04:56; hardware ethernet 00:0c:29:11:43:82; uid 01:00:0c:29:11:43:82; client-hostname "DC01"; } lease 192.168.74.158 { starts 0 2020/03/08 09:02:51; ends 0 2020/03/08 09:02:51; abandoned; client-hostname "DC01"; } lease 192.168.74.157 { starts 5 2020/03/06 06:49:58; ends 5 2020/03/06 06:51:58; hardware ethernet 00:0c:29:11:43:82; uid 01:00:0c:29:11:43:82; client-hostname "DC01"; } lease 192.168.74.156 { starts 5 2020/03/06 06:49:55; ends 5 2020/03/06 06:51:55; hardware ethernet 00:0c:29:11:43:82; uid 01:00:0c:29:11:43:82; client-hostname "DC01"; } lease 192.168.74.155 { starts 5 2020/03/06 06:49:50; ends 5 2020/03/06 06:49:50; abandoned; client-hostname "DC01"; } lease 192.168.74.154 { starts 5 2020/03/06 01:13:09; ends 5 2020/03/06 01:15:09; hardware ethernet 00:0c:29:11:43:82; uid 01:00:0c:29:11:43:82; client-hostname "DC01"; } lease 192.168.74.153 { starts 5 2020/03/06 01:13:05; ends 5 2020/03/06 01:15:05; hardware ethernet 00:0c:29:11:43:82; uid 01:00:0c:29:11:43:82; client-hostname "DC01"; } lease 192.168.74.152 { starts 5 2020/03/06 01:13:00; ends 5 2020/03/06 01:13:00; abandoned; client-hostname "DC01"; } lease 192.168.74.151 { starts 3 2020/03/04 09:41:46; ends 3 2020/03/04 09:43:46; hardware ethernet 00:0c:29:11:43:82; uid 01:00:0c:29:11:43:82; client-hostname "DC01"; } lease 192.168.74.150 { starts 3 2020/03/04 09:41:43; ends 3 2020/03/04 09:43:43; hardware ethernet 00:0c:29:11:43:82; uid 01:00:0c:29:11:43:82; client-hostname "DC01"; } lease 192.168.74.149 { starts 3 2020/03/04 09:41:40; ends 3 2020/03/04 09:41:40; abandoned; client-hostname "DC01"; } lease 192.168.74.148 { starts 3 2020/03/04 05:10:36; ends 3 2020/03/04 05:12:36; hardware ethernet 00:0c:29:11:43:82; uid 01:00:0c:29:11:43:82; client-hostname "DC01"; } lease 192.168.74.147 { starts 3 2020/03/04 05:10:32; ends 3 2020/03/04 05:10:46; hardware ethernet 00:0c:29:11:43:82; uid 01:00:0c:29:11:43:82; client-hostname "DC01"; } lease 192.168.74.146 { starts 3 2020/03/04 05:10:28; ends 3 2020/03/04 05:10:28; abandoned; client-hostname "DC01"; } lease 192.168.74.129 { starts 2 2020/02/18 02:51:03; ends 2 2020/02/18 03:21:03; hardware ethernet 00:0c:29:e9:fa:fb; uid 01:00:0c:29:e9:fa:fb; client-hostname "WIN-BEAEMMQ88PF"; } lease 192.168.74.143 { starts 4 2019/11/07 00:34:48; ends 4 2019/11/07 01:04:48; hardware ethernet 00:0c:29:d4:18:ed; client-hostname "sql"; } lease 192.168.74.144 { starts 4 2019/11/07 00:31:02; ends 4 2019/11/07 01:01:02; hardware ethernet 00:0c:29:ee:1f:48; client-hostname "web"; } lease 192.168.74.145 { starts 4 2019/11/07 00:35:26; ends 4 2019/11/07 00:46:32; hardware ethernet 00:0c:29:2d:a5:63; client-hostname "ansible"; } lease 192.168.74.140 { starts 3 2019/11/06 12:23:02; ends 3 2019/11/06 12:23:02; abandoned; client-hostname "ansible"; } lease 192.168.74.141 { starts 3 2019/11/06 12:21:57; ends 3 2019/11/06 12:21:57; abandoned; client-hostname "web"; } lease 192.168.74.142 { starts 3 2019/11/06 12:21:12; ends 3 2019/11/06 12:21:12; abandoned; client-hostname "sql"; } lease 192.168.74.139 { starts 3 2019/11/06 06:03:22; ends 3 2019/11/06 06:03:22; abandoned; client-hostname "sql"; } lease 192.168.74.138 { starts 3 2019/11/06 05:54:39; ends 3 2019/11/06 05:54:39; abandoned; client-hostname "web"; } lease 192.168.74.135 { starts 3 2019/11/06 05:53:51; ends 3 2019/11/06 05:53:51; abandoned; client-hostname "ansible"; } lease 192.168.74.137 { starts 2 2019/11/05 10:01:11; ends 2 2019/11/05 10:01:11; abandoned; client-hostname "ubuntu"; } lease 192.168.74.136 { starts 2 2019/11/05 08:18:51; ends 2 2019/11/05 08:18:51; abandoned; client-hostname "ubuntu"; } lease 192.168.74.133 { starts 2 2019/11/05 03:54:11; ends 2 2019/11/05 03:54:11; abandoned; client-hostname "ubuntu"; } lease 192.168.74.134 { starts 2 2019/11/05 01:07:53; ends 2 2019/11/05 01:14:07; hardware ethernet 00:0c:29:7c:cd:0c; client-hostname "ubuntu"; } lease 192.168.74.130 { starts 0 2019/10/20 02:37:43; ends 0 2019/10/20 03:07:43; hardware ethernet 00:0c:29:21:32:72; uid 01:00:0c:29:21:32:72; client-hostname "windows-d7138b3"; } lease 192.168.74.131 { starts 5 2019/10/18 10:24:49; ends 5 2019/10/18 10:54:49; hardware ethernet 00:0c:29:1a:a4:c7; uid 01:00:0c:29:1a:a4:c7; client-hostname "swang-o07fuusdv"; } lease 192.168.111.128 { starts 5 2019/10/18 10:04:45; ends 5 2019/10/18 10:23:37; hardware ethernet 00:0c:29:1a:a4:c7; uid 01:00:0c:29:1a:a4:c7; client-hostname "swang-o07fuusdv"; }

[spowelljr]

Hi @mudskipperwathotmail, sorry for the delayed response.

Was this previously working and then it stopped working?

Looking at the logs, you're using an existing VMX instance but it seems the IP is not in C:\ProgramData\VMware\vmnetdhcp.conf or C:\ProgramData\VMware\vmnetdhcp.leases, if this did use to work I'm wondering if the IP got removed somehow, and based on the logs we only keep restarting the instance instead of deleting it and creating a new one.

Either way, if you try running minikube delete --all to clear out your minikube instances, and double check in VMware if the minikube VMX is deleted and if not try manually deleting it, then try starting minikube again and see if that resolves your issue or not, thanks!

[mudskipperwathotmail]

hi Steven, no worries - i was busy with other stuff lately as well, haven't had a chance to try it myself.

i tried "minikubt delete --all", then reran "minikube start --driver vmware" but the problem remained. this time i turned all my VMs off. and check out the log below, only 1 VM was running, which WAS the minikube itself. i believe 00:0c:29:6f:1e:d2 is the minikube. ---> the log posted at the end of my msg.

i also found this thread https://github.com/machine-drivers/docker-machine-driver-xhyve/issues/91, somebody had exactly the same issue, but he said it was the RAM figure of the VM that was not set right(scroll to almost the end to see his solution). i checked on mine: from my log "I0421 23:40:20.557694 7580 start_flags.go:369] Using suggested 4000MB memory alloc based on sys=16292MB, container=0MB" - does "container=0MB" sound right???

thanks Shizhen

=====the log

• ==> Audit <==

• ---------	-------	----------	---------------------	---------	--------------------------------	--------------------------------		Command	Args	Profile	User	Version	Start Time	End Time
  --help		minikube	DESKTOP-KUNRATV\mud	v1.25.2	Tue, 22 Mar 2022 16:01:54 AEDT	Tue, 22 Mar 2022 16:01:54 AEDT
  delete		minikube	DESKTOP-KUNRATV\mud	v1.25.2	Tue, 22 Mar 2022 19:22:16 AEDT	Tue, 22 Mar 2022 19:22:21 AEDT
  delete	--all	minikube	DESKTOP-KUNRATV\mud	v1.25.2	Thu, 21 Apr 2022 22:15:56 AEST	Thu, 21 Apr 2022 22:16:01 AEST
  delete	--all	minikube	DESKTOP-KUNRATV\mud	v1.25.2	Thu, 21 Apr 2022 22:29:36 AEST	Thu, 21 Apr 2022 22:29:41 AEST
  delete	--all	minikube	DESKTOP-KUNRATV\mud	v1.25.2	Thu, 21 Apr 2022 22:40:23 AEST	Thu, 21 Apr 2022 22:40:28 AEST
  delete	--all	minikube	DESKTOP-KUNRATV\mud	v1.25.2	Thu, 21 Apr 2022 23:40:01 AEST	Thu, 21 Apr 2022 23:40:04 AEST
  ---------	-------	----------	---------------------	---------	--------------------------------	--------------------------------

• ==> Last Start <==

• Log file created at: 2022/04/21 23:40:20 Running on machine: DESKTOP-KUNRATV Binary: Built with gc go1.17.7 for windows/amd64 Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg I0421 23:40:20.472931 7580 out.go:297] Setting OutFile to fd 5672 ... I0421 23:40:20.473469 7580 out.go:344] TERM=,COLORTERM=, which probably does not support color I0421 23:40:20.473469 7580 out.go:310] Setting ErrFile to fd 5616... I0421 23:40:20.473469 7580 out.go:344] TERM=,COLORTERM=, which probably does not support color I0421 23:40:20.483583 7580 out.go:304] Setting JSON to false I0421 23:40:20.486694 7580 start.go:112] hostinfo: {"hostname":"DESKTOP-KUNRATV","uptime":396552,"bootTime":1650151868,"procs":207,"os":"windows","platform":"Microsoft Windows 10 Enterprise","platformFamily":"Standalone Workstation","platformVersion":"10.0.18363 Build 18363","kernelVersion":"10.0.18363 Build 18363","kernelArch":"x86_64","virtualizationSystem":"","virtualizationRole":"","hostId":"5c907cdf-74ca-4e61-9d02-96233e85c715"} W0421 23:40:20.487315 7580 start.go:120] gopshost.Virtualization returned error: not implemented yet I0421 23:40:20.490729 7580 out.go:176] minikube v1.25.2 on Microsoft Windows 10 Enterprise 10.0.18363 Build 18363 I0421 23:40:20.490729 7580 notify.go:193] Checking for updates... I0421 23:40:20.491895 7580 driver.go:344] Setting default libvirt URI to qemu:///system W0421 23:40:20.497973 7580 notify.go:58] Error getting json from minikube version url: error with http GET for endpoint https://storage.googleapis.com/minikube/releases-v2.json: Get "https://storage.googleapis.com/minikube/releases-v2.json": dial tcp: lookup storage.googleapis.com: no such host I0421 23:40:20.521457 7580 out.go:176] Using the vmware driver based on user configuration I0421 23:40:20.521457 7580 start.go:281] selected driver: vmware I0421 23:40:20.521457 7580 start.go:798] validating driver "vmware" against I0421 23:40:20.521457 7580 start.go:809] status for vmware: {Installed:true Healthy:true Running:false NeedsImprovement:false Error: Reason: Fix: Doc: Version:} I0421 23:40:20.525916 7580 start_flags.go:288] no existing cluster config was found, will generate one from the flags I0421 23:40:20.557694 7580 start_flags.go:369] Using suggested 4000MB memory alloc based on sys=16292MB, container=0MB I0421 23:40:20.557694 7580 start_flags.go:397] setting extra-config: kubelet.housekeeping-interval=5m I0421 23:40:20.557694 7580 start_flags.go:813] Wait components to verify : map[apiserver:true system_pods:true] I0421 23:40:20.557694 7580 cni.go:93] Creating CNI manager for "" I0421 23:40:20.557694 7580 cni.go:167] CNI unnecessary in this configuration, recommending no CNI I0421 23:40:20.557694 7580 start_flags.go:302] config: {Name:minikube KeepContext:false EmbedCerts:false MinikubeISO: KicBaseImage:gcr.io/k8s-minikube/kicbase:v0.0.30@sha256:02c921df998f95e849058af14de7045efc3954d90320967418a0d1f182bbc0b2 Memory:4000 CPUs:2 DiskSize:20000 VMDriver: Driver:vmware HyperkitVpnKitSock: HyperkitVSockPorts:[] DockerEnv:[] ContainerVolumeMounts:[] InsecureRegistry:[] RegistryMirror:[] HostOnlyCIDR:192.168.59.1/24 HypervVirtualSwitch: HypervUseExternalSwitch:false HypervExternalAdapter: KVMNetwork:default KVMQemuURI:qemu:///system KVMGPU:false KVMHidden:false KVMNUMACount:1 DockerOpt:[] DisableDriverMounts:false NFSShare:[] NFSSharesRoot:/nfsshares UUID: NoVTXCheck:false DNSProxy:false HostDNSResolver:true HostOnlyNicType:virtio NatNicType:virtio SSHIPAddress: SSHUser:root SSHKey: SSHPort:22 KubernetesConfig:{KubernetesVersion:v1.23.3 ClusterName:minikube Namespace:default APIServerName:minikubeCA APIServerNames:[] APIServerIPs:[] DNSDomain:cluster.local ContainerRuntime:docker CRISocket: NetworkPlugin: FeatureGates: ServiceCIDR:10.96.0.0/12 ImageRepository: LoadBalancerStartIP: LoadBalancerEndIP: CustomIngressCert: ExtraOptions:[{Component:kubelet Key:housekeeping-interval Value:5m}] ShouldLoadCachedImages:true EnableDefaultCNI:false CNI: NodeIP: NodePort:8443 NodeName:} Nodes:[] Addons:map[] CustomAddonImages:map[] CustomAddonRegistries:map[] VerifyComponents:map[apiserver:true system_pods:true] StartHostTimeout:6m0s ScheduledStop: ExposedPorts:[] ListenAddress: Network: MultiNodeRequested:false ExtraDisks:0 CertExpiration:26280h0m0s Mount:false MountString:C:\Users\mud:/minikube-host Mount9PVersion:9p2000.L MountGID:docker MountIP: MountMSize:262144 MountOptions:[] MountPort:0 MountType:9p MountUID:docker BinaryMirror: DisableOptimizations:false} I0421 23:40:20.558230 7580 iso.go:123] acquiring lock: {Name:mk951fe2280e431bf0b2c2a5b8c92a1f98347429 Clock:{} Delay:500ms Timeout:10m0s Cancel:} I0421 23:40:20.562360 7580 out.go:176] Starting control plane node minikube in cluster minikube I0421 23:40:20.562360 7580 preload.go:132] Checking if preload exists for k8s version v1.23.3 and runtime docker I0421 23:40:20.562882 7580 preload.go:148] Found local preload: C:\Users\mud.minikube\cache\preloaded-tarball\preloaded-images-k8s-v17-v1.23.3-docker-overlay2-amd64.tar.lz4 I0421 23:40:20.562882 7580 cache.go:57] Caching tarball of preloaded images I0421 23:40:20.562882 7580 preload.go:174] Found C:\Users\mud.minikube\cache\preloaded-tarball\preloaded-images-k8s-v17-v1.23.3-docker-overlay2-amd64.tar.lz4 in cache, skipping download I0421 23:40:20.562882 7580 cache.go:60] Finished verifying existence of preloaded tar for v1.23.3 on docker I0421 23:40:20.563409 7580 profile.go:148] Saving config to C:\Users\mud.minikube\profiles\minikube\config.json ... I0421 23:40:20.563409 7580 lock.go:35] WriteFile acquiring C:\Users\mud.minikube\profiles\minikube\config.json: {Name:mk90e80b5ce50deb769319052c495db776cfb1af Clock:{} Delay:500ms Timeout:1m0s Cancel:} I0421 23:40:20.564453 7580 cache.go:208] Successfully downloaded all kic artifacts I0421 23:40:20.565382 7580 start.go:313] acquiring machines lock for minikube: {Name:mk37cf32262a030d3afda08677a6863da3870a22 Clock:{} Delay:500ms Timeout:13m0s Cancel:} I0421 23:40:20.565824 7580 start.go:317] acquired machines lock for "minikube" in 441.9µs I0421 23:40:20.566489 7580 start.go:89] Provisioning new machine with config: &{Name:minikube KeepContext:false EmbedCerts:false MinikubeISO:https://storage.googleapis.com/minikube/iso/minikube-v1.25.2.iso KicBaseImage:gcr.io/k8s-minikube/kicbase:v0.0.30@sha256:02c921df998f95e849058af14de7045efc3954d90320967418a0d1f182bbc0b2 Memory:4000 CPUs:2 DiskSize:20000 VMDriver: Driver:vmware HyperkitVpnKitSock: HyperkitVSockPorts:[] DockerEnv:[] ContainerVolumeMounts:[] InsecureRegistry:[] RegistryMirror:[] HostOnlyCIDR:192.168.59.1/24 HypervVirtualSwitch: HypervUseExternalSwitch:false HypervExternalAdapter: KVMNetwork:default KVMQemuURI:qemu:///system KVMGPU:false KVMHidden:false KVMNUMACount:1 DockerOpt:[] DisableDriverMounts:false NFSShare:[] NFSSharesRoot:/nfsshares UUID: NoVTXCheck:false DNSProxy:false HostDNSResolver:true HostOnlyNicType:virtio NatNicType:virtio SSHIPAddress: SSHUser:root SSHKey: SSHPort:22 KubernetesConfig:{KubernetesVersion:v1.23.3 ClusterName:minikube Namespace:default APIServerName:minikubeCA APIServerNames:[] APIServerIPs:[] DNSDomain:cluster.local ContainerRuntime:docker CRISocket: NetworkPlugin: FeatureGates: ServiceCIDR:10.96.0.0/12 ImageRepository: LoadBalancerStartIP: LoadBalancerEndIP: CustomIngressCert: ExtraOptions:[{Component:kubelet Key:housekeeping-interval Value:5m}] ShouldLoadCachedImages:true EnableDefaultCNI:false CNI: NodeIP: NodePort:8443 NodeName:} Nodes:[{Name: IP: Port:8443 KubernetesVersion:v1.23.3 ContainerRuntime:docker ControlPlane:true Worker:true}] Addons:map[] CustomAddonImages:map[] CustomAddonRegistries:map[] VerifyComponents:map[apiserver:true system_pods:true] StartHostTimeout:6m0s ScheduledStop: ExposedPorts:[] ListenAddress: Network: MultiNodeRequested:false ExtraDisks:0 CertExpiration:26280h0m0s Mount:false MountString:C:\Users\mud:/minikube-host Mount9PVersion:9p2000.L MountGID:docker MountIP: MountMSize:262144 MountOptions:[] MountPort:0 MountType:9p MountUID:docker BinaryMirror: DisableOptimizations:false} &{Name: IP: Port:8443 KubernetesVersion:v1.23.3 ContainerRuntime:docker ControlPlane:true Worker:true} I0421 23:40:20.566489 7580 start.go:126] createHost starting for "" (driver="vmware") I0421 23:40:20.571014 7580 out.go:203] Creating vmware VM (CPUs=2, Memory=4000MB, Disk=20000MB) ... I0421 23:40:20.586657 7580 main.go:130] libmachine: Found binary path at C:\Program Files\docker-machine-driver\docker-machine-driver-vmware.exe I0421 23:40:20.586657 7580 main.go:130] libmachine: Launching plugin server for driver vmware I0421 23:40:21.792112 7580 main.go:130] libmachine: Plugin server listening at address 127.0.0.1:64537 I0421 23:40:21.793162 7580 main.go:130] libmachine: () Calling .GetVersion I0421 23:40:21.793716 7580 main.go:130] libmachine: Using API Version 1 I0421 23:40:21.793716 7580 main.go:130] libmachine: () Calling .SetConfigRaw I0421 23:40:21.794251 7580 main.go:130] libmachine: () Calling .GetMachineName I0421 23:40:21.794251 7580 main.go:130] libmachine: (minikube) Calling .GetMachineName I0421 23:40:21.794251 7580 main.go:130] libmachine: (minikube) Calling .DriverName I0421 23:40:21.794798 7580 start.go:160] libmachine.API.Create for "minikube" (driver="vmware") I0421 23:40:21.794798 7580 client.go:168] LocalClient.Create starting I0421 23:40:21.794798 7580 main.go:130] libmachine: Reading certificate data from C:\Users\mud.minikube\certs\ca.pem I0421 23:40:21.795334 7580 main.go:130] libmachine: Decoding PEM data... I0421 23:40:21.795334 7580 main.go:130] libmachine: Parsing certificate... I0421 23:40:21.795334 7580 main.go:130] libmachine: Reading certificate data from C:\Users\mud.minikube\certs\cert.pem I0421 23:40:21.795334 7580 main.go:130] libmachine: Decoding PEM data... I0421 23:40:21.795334 7580 main.go:130] libmachine: Parsing certificate... I0421 23:40:21.795334 7580 main.go:130] libmachine: Running pre-create checks... I0421 23:40:21.795334 7580 main.go:130] libmachine: (minikube) Calling .PreCreateCheck I0421 23:40:21.795850 7580 main.go:130] libmachine: (minikube) Calling .GetConfigRaw I0421 23:40:21.796958 7580 main.go:130] libmachine: Creating machine... I0421 23:40:21.796958 7580 main.go:130] libmachine: (minikube) Calling .Create I0421 23:40:21.797475 7580 main.go:130] libmachine: (minikube) Downloading C:\Users\mud.minikube\cache\boot2docker.iso from file://C:/Users/mud/.minikube/cache/iso/amd64/minikube-v1.25.2.iso... I0421 23:40:22.019323 7580 main.go:130] libmachine: (minikube) Creating SSH key... I0421 23:40:22.302636 7580 main.go:130] libmachine: (minikube) Creating VM... I0421 23:40:22.378691 | Creating disk 'C:\Users\mud.minikube\machines\minikube\minikube.vmdk' I0421 23:40:22.378691 | Virtual disk creation successful. I0421 23:40:22.388478 7580 main.go:130] libmachine: (minikube) Starting minikube... I0421 23:40:22.388478 | executing: C:\Program Files (x86)\VMware\VMware Workstation\vmrun.exe start C:\Users\mud.minikube\machines\minikube\minikube.vmx nogui I0421 23:40:24.282552 7580 main.go:130] libmachine: (minikube) Waiting for VM to come online... I0421 23:40:24.283637 | executing: C:\Program Files (x86)\VMware\VMware Workstation\vmrun.exe list I0421 23:40:24.603462 | Total running VMs: 1 I0421 23:40:24.603462 | C:\Users\mud.minikube\machines\minikube\minikube.vmx I0421 23:40:24.625532 | executing: C:\Program Files (x86)\VMware\VMware Workstation\vmrun.exe getGuestIPAddress C:\Users\mud.minikube\machines\minikube\minikube.vmx -wait I0421 23:40:54.654998 | MAC address in VMX: 00:0c:29:6f:1e:d2 I0421 23:40:54.654998 | Trying to find IP address in configuration file: C:\ProgramData\VMware\vmnetdhcp.conf I0421 23:40:54.656148 | Following IPs found map[00:50:56:c0:00:01:192.168.111.1 00:50:56:c0:00:08:192.168.74.1] I0421 23:40:54.656148 | Trying to find IP address in leases file: C:\ProgramData\VMware\vmnetdhcp.leases I0421 23:40:54.658976 | Not there yet 1/60, error: IP not found for MAC 00:0c:29:6f:1e:d2 in DHCP leases

[spowelljr]

Thanks for the response @mudskipperwathotmail, I'll take a more in-depth look at the logs later, but to answer your questions about container=0MB. That's because you're using a VM driver instead of a container driver like Docker, so that's expected.

[mudskipperwathotmail]

thanks Steven. take your time. it seems to me, the problem is around these few steps:

1. the procedure tries to run vmrun.exe getGuestIPAddress C:\Users\mud.minikube\machines\minikube\minikube.vmx -wait and gets the MAC ADDR: 00:0c:29:6f:1e:d2
2. it looks up the ip in my existing vmnetdhcp.conf, which contains only 2 virtual networks: Mnet1 192.168.111.1; VMnet8 192.168.74.1; and the new minikube vm is not on either of them. on VMWare Workstation, i used assign my VMs onto these 2 virtual networks but somehow the internet stopped working, so all my VMs are on "Bridged: connected directly to the physical network(replicate physical network connection state)". for an example: my latest VM Ubuntu20.04(installed a few days ago) is not on the vmnetdhcp.conf or vmnetdhcp.leases. here is my ubuntu20.04 ip info: swang@ubuntu:~$ ip addr 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens33: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000 link/ether 00:0c:29:d7:79:f7 brd ff:ff:ff:ff:ff:ff altname enp2s1 inet 172.20.10.13/28 brd 172.20.10.15 scope global dynamic noprefixroute ens33 valid_lft 86316sec preferred_lft 86316sec inet6 fe80::d1b9:8f4a:d9a9:a61b/64 scope link noprefixroute valid_lft forever preferred_lft forever 3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default link/ether 02:42:85:98:e0:22 brd ff:ff:ff:ff:ff:ff inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0 valid_lft forever preferred_lft forever

not sure if these are misleading you or it is the clue... but if we can assign the new minikube vm to be the same, and not having to look up to those 2 virtual networks, that might fix the issue.

your thoughts?

thanks Shizhen

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages 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:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to [this](https://github.com/kubernetes/minikube/issues/13866#issuecomment-1272388147): >The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs. > >This bot triages 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: >- Reopen this issue with `/reopen` >- Mark this issue as fresh with `/remove-lifecycle rotten` >- Offer to help out with [Issue Triage][1] > >Please send feedback to sig-contributor-experience at [kubernetes/community](https://github.com/kubernetes/community). > >/close not-planned > >[1]: https://www.kubernetes.dev/docs/guide/issue-triage/ Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.