-
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
VBoxManage.exe: error: Invalid NIC number #7417
Comments
Hi @cdreier Thank you for opening an issue. Could you please share the complete debug output as a GitHub gist? What version of VirtualBox are you using? |
Hi @sethvargo thanks a lot for your fast response! i use a fresh install from virtual box, version 5.0.20 r106931 and my complete debug output: https://gist.github.com/cdreier/9b5beb38473e9221dfe71ad04b58f73b also i tried the git bash, cmd and cmd as admin, everywhere the same issue |
Confirm the problem. It is reproduced with Windows10/Vagrant 1.8.3/VirtualBox 5.0.20 and Looks like it is caused by the recent change "Set maximum network adapters to 36 [GH-7293, GH-7286]". Indeed if change back |
@apestov This fixed my issue as well. |
thanks a lot for you fast help! everything is working again :-) |
@apestov Wow, thanks for finding a solution so quickly! I had the same problem on the same setup as you and your solution corrected it. |
@apestov Thanks! I am just getting started with Vagrant today and ran into this issue too. It's great to have it working! |
@apestov Thanks! It's working for me. |
@apestov thanks, my problem on win10 also went away after changing a value of
|
same problem with ubuntu/xenial64 and other boxes as well, the update of vagrant totally killed our workflow, we needed to downgrade immediatelly for the time being |
I confirm that changing from 36 to 8 does the job - Win7, vagrant 1.8.3, vbox 5.0.20 |
Fixed on Win10 for me too |
@apestov your solution fixed the issue for me on: |
Please release new version |
The fix worked for me too. Thanks!! |
@sethvargo Thank you for the prompt Vagrant 1.8.4 release with that issue fixed! |
Worked for me! Thanks a lot! |
It helped me. Thanks! |
many many many thanks for new release! it fixed all the issues! even nfs mounting under windows working again! |
Ran into this issue after a fresh install of Windows. Changing max_network_adapters to 8 fixes this issue for me as well. |
Worked for me, thanks!! |
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. |
any help is much appreciated!
Vagrant version
Vagrant 1.8.3
Host operating system
windows 10
Guest operating system
tried diffrent boxes, ubuntu and mint
Vagrantfile
default vagrant file, with vagrant init
Debug output
Expected behavior
box should start
Actual behavior
a lot of invalid NIC numbers
Steps to reproduce
References
#6125
cambridge-healthcare/hi_sinatra-docker#5
The text was updated successfully, but these errors were encountered: