Workaround for ssh timeouts on vmwarevsphere

[zaubara]

This is a hacky workaround for an issue me and others seem to have with not being able to connect via docker-machine to our vsphere machines. I didn't find relevant discussions about the underlying issue or possible fixes. I hope to get the ball rolling.

I'm using the vmwarevsphere driver, and since I added a second stack to docker, I was no longer able to connect to boot2docker via docker-machine (direct ssh and the docker images worked fine).

To get a static IP, we have to apply a dirty startup-script (via bootsync.sh), which kills udhcpc and applies a static ip. This is probably the root of all evil here.
Since the second stack however, vmware seems to no longer report about the ipv4 adresses on the network - only ipv6, which made the GetSSHHostname-call timeout.
Adding a second network card via vsphere (eth1, which by the way boot2docker complains about and seems to expect, even on a fresh install) again gets me a dynamic IP, which I can then use to ssh via docker-machine - but without aforementioned workaround still times out.

We should probably find out, why

• no more ipv4 adresses are recognized by the host (even on the esxi admin)
• the wait gets stuck (i started using go 2 hours ago, so i whipped this up)
• and how we can apply static IPs to the VM the right way.

Thanks!

[GordonTheTurtle]

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:

$ git clone -b "master" git@github.com:zaubara/machine.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.