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
Proposed Change: Multiple NICs on HyperV provider #8849
Comments
@mwrock do you have any thoughts on this? |
I'd agree that specifying multiple network configs should result in multiple NICs. I'm not sure if this is a Hyper-V provider issue or accross all providers on windows guests. I wonder what happens on vbox for instance. |
Nah it looks like its just hyper v, basically the import action only takes the name of one vswitch, so whatever config was last in the config becomes that vswitch. Instead I have now created an action that wipes out all the network adapters on a vm and then adds them back again for each switch in config. I will try and post the PR in the next few days. |
@wiltaylor Any update on this? |
Can we please get this moving forward? There's also #9439, but it too requires @wiltaylor's signature on CLA, and it seems he hasn't been as active on GitHub recently. I am willing to give this a try, but definitely one of the must-have features IMO. |
@briancain @Jaskaranbir Was there any change with this? |
I commented on the static IP issue but it's somewhat relevant to this as well #8384 (comment) |
This a very interesting feature, are there updates in this work? |
Vagrant version
Vagrant 1.9.7
Host operating system
Windwos 10 Creative Update
Guest operating system
Any
Expected behavior
When defining multiple networks in a vagrant file it should result in multiple network cards being attached to the resultant virtual machine.
Actual behavior
The latest network entry becomes the network card added to the virtual machine.
Proposed Changes:
I am thinking of doing the following:
Out of scope: - Will probably add these later. Need to get some of the basics working first though.
The text was updated successfully, but these errors were encountered: