-
Notifications
You must be signed in to change notification settings - Fork 64
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
Virtualbox Windows images need to have Virtio network driver #111
Comments
@diwu1989 thanks for proposing this fix. Which box do you use if I may ask? I can try to update only that one first and do some tests. Also, can you please confirm what is your host setup? |
I had the problem with one of my boxes with one specific Win10+VirtualBo 5.2 machine. No network device found in the Win10 VM. |
@StefanScherer thanks heaps for the information. Maybe something to do with the host OS / Vagrant version, VirtualBox (patch) version, and the guest additions constellation? I remember some issues earlier (maybe with VirtualBox 5.1) when there were several regressions across the patch versions. Anyway, @diwu1989 if you let me know which Windows box you're working with, I can try to build a test version with the above package you mention. |
@diwu1989 can this be also the root cause? hashicorp/vagrant#10448 Can you please try with the latest Vagrant (2.2.2) where it is supposed to be fixed? |
I was using gusztavvargadr/w10e |
@diwu1989 thanks for getting back on this and for the update. Good to hear it's resolved now. I agree, there are too many regressions (both for Vagrant and VirtualBox). I try to include this in the next release, to be expected later this month, after the major patches for the OSes ;) |
@diwu1989 I have now some new core OS images with the drivers included. https://app.vagrantup.com/gusztavvargadr/boxes/windows-10 I will publish an update to rest of the boxes soon. |
Please install https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/virtio-win.iso in the Windows VM.
This will resolve the issue seen in #72
The text was updated successfully, but these errors were encountered: