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
hyperv : Vagrant change secondary network adapter Vswitch #11073
Comments
I think the issue is locate here :
|
Hi there, Would you please provide a gist with the debug output from the first successful Thanks! |
Done : My vagrant file : Typed trigger and hyperv-set_network_adapter.ps1 are use for set IP from Windows, you can remove it vagrant cannot get IP but the problem keep the same
First Run : https://gist.github.com/mysiki/7368b9d7a33ab65068d1cf83cf14c272#file-vagrant-log-11073-run01-log
Halt : https://gist.github.com/mysiki/7368b9d7a33ab65068d1cf83cf14c272#file-vagrant-log-11073-run02-log
Powershell, show adapter and add one : Vswitch AFSS and WSL already exist Name Vagrant_adapter are set by my default, by default, Vagrant do not provide name, so adapter get default hyperV name "default connection"
Secondary UP : https://gist.github.com/mysiki/7368b9d7a33ab65068d1cf83cf14c272#file-vagrant-log-11073-run03-log
Result :
Both adapter are set to AFSS Vswitch |
Vagrant version
Vagrant 2.2.5
Host operating system
Win10 V1903 Build 18975
Guest operating system
Ubuntu : generic/ubuntu1604
Vagrantfile
Debug output
Expected behavior
Actual behavior
When first vagrant up, Actual = Expected
After other vagrant up
Steps to reproduce
References
Maybe : #10455
Details
In case of Vagrant have hard limitation on Hyper-v network, I used typed trigger and powershell script for :
In first UP, all is find, I get 2 adpater, each on the right VSwitch
In next UP, vagrant change my secondary adapter to Vswitch pass in vagrant file, instead of it already have one...
Trying to :
Until vagrant don't manager hyper-v network, we need a variable to disabled "auto network creation".
Other think, why Vagrant put all the network adapter to the Vswitch give in vagrant file ? It need to control only here adapter, than can be easy doing using the name of the network (currently vagrant do not set the name, hyper-v create a default name, but it can be a parameter of network configuration in vagrant file).
The text was updated successfully, but these errors were encountered: