You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Expected the started VM to have the defined IP (or at least MAC to set DHCP-reservation).
Actual behavior
Settings regarding networking are mostly ignored or not used (thankfully at least defining the bridge interface works).
I tried some of the options alone as also combined in different order, nothing worked to set a static ip in any way, vm always is set to DHCP. Also when only setting MAC to a specific value, its a new one every "vagrant up", so this way I can not even set DHCP reservation.
Steps to reproduce
vagrant init generic/debian9
set in Vagrantfile: config.vm.network "public_network", bridge: "<hvhost_nic>", mac: "00155d0dabc7", ip: "192.168.1.2", type: "static", auto_config: false
vagrant up
References
I found similar issues but none of them regarding provider hyperv...
The text was updated successfully, but these errors were encountered:
Vagrant version
2.2.0
Host operating system
Windows Server 2012 R2 [Version 6.3.9600] (German)
Guest operating system
generic/debian9
Vagrantfile
Debug output
https://gist.github.com/vchrizz/d2711be3d206e69a68c5288ba5b6d7a1
Expected behavior
Expected the started VM to have the defined IP (or at least MAC to set DHCP-reservation).
Actual behavior
Settings regarding networking are mostly ignored or not used (thankfully at least defining the bridge interface works).
I tried some of the options alone as also combined in different order, nothing worked to set a static ip in any way, vm always is set to DHCP. Also when only setting MAC to a specific value, its a new one every "vagrant up", so this way I can not even set DHCP reservation.
Steps to reproduce
config.vm.network "public_network", bridge: "<hvhost_nic>", mac: "00155d0dabc7", ip: "192.168.1.2", type: "static", auto_config: false
References
I found similar issues but none of them regarding provider hyperv...
The text was updated successfully, but these errors were encountered: