+++ -102,7 +102,7 module whether WinRM is ready.")įixed hanging while configuring network adapters inside the VM. a/plugins/communicators/winrm/communicator.rb But now it seems that configuring network adapters messes up the WinRM connection, but vagrant doesn't detect anything is out of order, so it just hangs waiting for the script output.ĭiff -git a/plugins/communicators/winrm/communicator.rb b/plugins/communicators/winrm/communicator.rb This diff can be applied to /opt/vagrant/embedded/gems/gems/vagrant-1.8.1/. Well after a few hours of tinkering, I was able to add the :nic_mac_addresses capability to the vmware_fusion provider by hackily patching stuff up.
+ require_relative "cap/nic_mac_addresses" + provider_capability(:vmware_fusion, :nic_mac_addresses) do +++ -16,33 +16,27 module #]ĭiff -git a/plugins/guests/windows/plugin.rb b/plugins/guests/windows/plugin.rb a/plugins/guests/windows/cap/configure_networks.rb
So for a user of Vagrant it just behaves like the virtualbox provider then.ĭiff -git a/plugins/guests/windows/cap/configure_networks.rb b/plugins/guests/windows/cap/configure_networks.rb provider provider do | v, override|Ĭan this small part be done by the vagrant-vmware-fusion as well? network :forwarded_port, guest: 3389, host: 3389, id: "rdp", auto_correct: true config. network :forwarded_port, guest: 5985, host: 5985, id: "winrm", auto_correct: true config. configure ( VAGRANTFILE_API_VERSION ) do | config|Ĭonfig. # -*- mode: ruby -*- # vi: set ft=ruby : VAGRANTFILE_API_VERSION = "2" Vagrant. Inside the Windows 10 VM the network addresses are configured as follows: => default: Enabling and configuring shared folders.ĭefault: - /Users/stefan/code/win10: /vagrant => default: configure the network adapter. => default: on Windows is not yet supported. => default: Configuring secondary network adapters through VMware => default: Configuring network adapters within the VM. => default: Verifying vmnet devices are healthy. => default: Cloning VMware VM: 'windows_10'. Bringing machine 'default' up with 'vmware_fusion' provider.
0 kommentar(er)
