-
Notifications
You must be signed in to change notification settings - Fork 70
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
Machine didn't return an IP after 120 seconds, aborting #29
Comments
Hi! yes, please issue Thanks |
Thanks, Weird, I thought I tried that, but here is my update:
|
@nlzet |
@pecigonzalo |
Ok, ill test with that version once i have my windows dev box nearby, could you check the vmx file in the meantime? because it seems it might not be finding the key that contains the MAC address there, so it doesnt know what IP to use for the connection. |
Here it is:
|
@nlzet I would say try removing the file and running again. Seems like vmware did not generate a Mac address for you. I just tried, W10, Workstation 12 and it works. |
Aha, it works now. Sad thing is I tried multiple solutions at once, so I don't know the real solution.
|
@nlzet Didnt knew you had Hyper-V, im 99% sure that was the issue, so the VM never started and would never get a MAC Address so the the driver cant find the IP to connect. You can use this method to easily switch between them: To be able to use both, albeit you will need to reboot to switch. |
@pecigonzalo Thanks for you information, I didn't know this. From the documentation of Docker I knew that when I installed Docker for Windows + Hyper-V that Docker with Virtualbox would stop working, but I didn't knew it would give a conflict with VMWare. Probably because I don't know anything about VMWare, but I wanted to try this solution to see if the performance of shared folders on VMWare was better than VirtualBox. |
Hi @pecigonzalo , sorry for commenting on a closed issue, however, I've tried all the approaches discussed previously and I'm still getting a "Machine didn't return an IP after 120 seconds, aborting". About what I've done:
After that (the following command was execute with and without disk size):
As shown, the log Error finding VMware root: The system cannot find the file specified presents some info that could be useful. [Silly question] Could it related to the fact that VMWare is installed in a non-usual path? Apart from that, Hyper-V is disabled here and also in BIOS. So I don't think this could be causing much trouble. Any clue on this issue would be more than appreciated. Thanks in advance, |
I almost forget to mention - dev.vmx
And also VMware Workstation version: 12.5.7 build-5813279 |
@fernandoabcampos Would you mind opening a new issue and just referencing this one? |
@pecigonzalo sure. I created the #45 many thanks. |
Hi I just tried this setup but I can't seem to get it working.
History:
Versions:
You probably want some extra debugging output, but how do I get this? I tried running this with a --debug flag, but that gave me:
The text was updated successfully, but these errors were encountered: