-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Vagrant not detect current host-only network adapters - on Windows #1544
Comments
Are you using cmd.exe, cygwin, msys, etc. (which one) |
So. I'm on Windows 8 and whenever I attempt to use host only networks with VirtualBox I get a blue screen, so I can't check this out right now, which is a huge bummer. |
Could you help by getting me the output with VAGRANT_LOG=debug set? |
Hi, sorry for answering until now. I'm going to try to reproduce the error, beacause we decide to reinstall VirtualBox and deleting all HostOnly network interfaces and the problem was fixed. |
Got it, let me know if you see it again. Closing since I haven't heard of any others having this issue. |
I ran into the same issue. It appears to only happen when you already have a host only ethernet adapter set up in VirtualBox prior to attempting to use the :private_network functionality in Vagrant. The simplest solution is to either 1) delete all previous host only ethernet adapters from VirtualBox or 2) set the ip using private_network and force the VM's nic (via VirtualBox) to use the already installed host only network... I.e. vb.customize ["modifyvm", :id, "--nic2", "hostonly", "--cableconnected2", "on", "--hostonlyadapter2", "VirtualBox Host-Only Ethernet Adapter"] Given that vboxmanage doesn't provide a great way to list already installed host only ethernet adapters, I don't see how this is readily fixable... Just my two cents. |
got it to work this way #1014 (comment) |
it works following @williambillypaul 's advice. 👍 |
Strange, I've been running for weeks with no issue, but am now seeing this. It survives me deleting all host adapters from Device Manager and restarting. I perform a vagrant up on box 1, creates 'VirtualBox Host-Only Network' adapter. I perform the vagrant up for box 2, creates 'VirtualBox Host-Only Network #2'. |
Same issue. It creates new adapter on host every time. |
If Vagrantfile contains the following:
it keeps creating new host-only interface on Windows host every next
I checked the output of
This could also be VirtualBox bug, because the ip of it's adapter on host cannot be changed.
|
I have this issue as well, sorry to not have any more info but the project I am on has this
And it's causing major pains for me running the project. Just wanted to chime in as this is still an issue for me and was hoping to raise more awareness. Thanks a lot for all the hard work. Virtualbox 5.0.10r104061 |
I found a way to get the project I was working on to work despite this issue. Basically we forced vagrant to use a very specific adapter and not the one that was generated. So something like this:
Granted this does not fix this issue; but I figured in may help someone find away around it. I currently have to remove the excess adapters by hand, but I am sure one can make a script to do that as well. |
Same experience here. Vagrant 1.7.4 running from Cygwin |
For no apparent reason I started having this problem under Windows 10 with Cygwin/Babun. I have the same issue also with Docker, so I'm pretty sure it's a problem with VirtualBox. I found that enabling VirualBox NDIS6 Bidge Networking Driver in the adapter properties seemed to have fixed the problem. I noticed it was not enabled and thought I would see what difference it made. I have since found some confirmation about this at Stack Overflow. |
Hey @AlexFdv
Did you try the suggested solution in the comment immediately prior to yours? |
Hi @courtney-miles Thank you. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
On windows as host, vagrant create a new host-only network adapter on the host, I think is because Vagrant can't identify a matching host-only network adapter and create a new one. no matter what even if the last host-only network adapter is still there.
The host-only network adapters always differs from the specified ip.
This issue just happen on windows as host, because with the same configuration on a Linux machine as host everything run as expected.
Vagrant version: 1.1.5 for windows
Host: windows 7 64 bit
Guest: centOS 6.4 32 bit
VirtualBox 4.2.10 r84104
Thank you in advance.
The text was updated successfully, but these errors were encountered: