KVM: log more details when minikube is failed to start

[ilya-zuyev]

ATM, if minikube is faiiled to start with kvm driver the logs are not very informative:

I0519 13:34:43.422786  164784 main.go:128] libmachine: (minikube) DBG | I0519 13:34:43.422686  165018 retry.go:31] will retry after 9.953714808s: waiting for machine to come up
I0519 13:34:53.379360  164784 main.go:128] libmachine: (minikube) DBG | domain minikube has defined MAC address 52:54:00:b6:34:03 in network mk-minikube
I0519 13:34:53.379793  164784 main.go:128] libmachine: (minikube) DBG | unable to find current IP address of domain minikube in network mk-minikube
I0519 13:34:53.379829  164784 main.go:128] libmachine: (minikube) DBG | I0519 13:34:53.379705  165018 retry.go:31] will retry after 15.120437328s: waiting for machine to come up
I0519 13:35:08.502351  164784 main.go:128] libmachine: (minikube) DBG | domain minikube has defined MAC address 52:54:00:b6:34:03 in network mk-minikube
I0519 13:35:08.502779  164784 main.go:128] libmachine: (minikube) DBG | unable to find current IP address of domain minikube in network mk-minikube
I0519 13:35:08.503645  164784 main.go:128] libmachine: (minikube) KVM machine creation complete!
I0519 13:35:08.503778  164784 client.go:171] LocalClient.Create took 1m6.867506221s
I0519 13:35:10.504966  164784 start.go:129] duration metric: createHost completed in 1m8.91454672s
I0519 13:35:10.505033  164784 start.go:80] releasing machines lock for "minikube", held for 1m8.914751391s
W0519 13:35:10.505316  164784 out.go:235] * Failed to start kvm2 VM. Running "minikube delete" may fix it: creating host: create: Error creating machine: Error in driver during machine creation: IP not available after waiting: machine minikube didn't return IP after 1 minute
* Failed to start kvm2 VM. Running "minikube delete" may fix it: creating host: create: Error creating machine: Error in driver during machine creation: IP not available after waiting: machine minikube didn't return IP after 1 minute
I0519 13:35:10.509795  164784 out.go:170] 

W0519 13:35:10.509971  164784 out.go:235] X Exiting due to GUEST_PROVISION: Failed to start host: creating host: create: Error creating machine: Error in driver during machine creation: IP not available after waiting: machine minikube didn't return IP after 1 minute
X Exiting due to GUEST_PROVISION: Failed to start host: creating host: create: Error creating machine: Error in driver during machine creation: IP not available after waiting: machine minikube didn't return IP after 1 minute
W0519 13:35:10.509981  164784 out.go:424] no arguments passed for "* \n" - returning raw string
W0519 13:35:10.509989  164784 out.go:235] * 

Printing more details, like the output of virsh net-info/net-dumpxml/dominfo/dumpxml could help a lot to investigate such issues

[anuj-8march]

I am facing similar issue ,minikube is not getting started and getting error as

10708 out.go:235] Failed to start hyperv VM. Running "minikube delete" may fix it: provision: IP not found 10708 out.go:170] 10708 out.go:235] X Exiting due to GUEST_PROVISION: Failed to start host: provision: IP not found 10708 out.go:424] no arguments passed for " \n" - returning raw string

[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

[sharifelgamal]

More logging seems like a good idea. Help wanted!