Vagrant 1.9.7 displays warning about a box compatibility with VMware

[Wojciech Sciesinski]

After updating to Vagrant 1.9.7 following messages are displayed under booting machine based on a package created with packer-ubuntu-1604 project.

VMware-test git:(master) > vagrant up
Bringing machine 'vm1' up with 'vmware_workstation' provider...
==> vm1: Cloning VMware VM: 'ubuntu1604-my'. This can take some time...
==> vm1: Verifying vmnet devices are healthy...
==> vm1: Preparing network adapters...
WARNING: The VMX file for this box contains a setting that is automatically overwritten by Vagrant
WARNING: when started. Vagrant will stop overwriting this setting in an upcoming release which may
WARNING: prevent proper networking setup. Below is the detected VMX setting:
WARNING: 
WARNING:   ethernet0.pcislotnumber = "33"
WARNING: 
WARNING: If networking fails to properly configure, it may require this VMX setting. It can be manually
WARNING: applied via the Vagrantfile:
WARNING: 
WARNING:   Vagrant.configure(2) do |config|
WARNING:     config.vm.provider :vmare_workstation do |vmware|
WARNING:       vmware.vmx["ethernet0.pcislotnumber"] = "33"
WARNING:     end
WARNING:   end
WARNING: 
WARNING: For more information: https://www.vagrantup.com/docs/vmware/boxes.html#vmx-whitelisting
==> vm1: Starting the VMware VM...
==> vm1: Waiting for machine to boot. This may take a few minutes...
    vm1: SSH address: 192.168.86.130:22
    vm1: SSH username: vagrant
    vm1: SSH auth method: private key
==> vm1: Machine booted and ready!
==> vm1: Forwarding ports...
    vm1: -- 22 => 2222
    vm1: SSH address: 192.168.86.130:22
    vm1: SSH username: vagrant
    vm1: SSH auth method: private key
==> vm1: Setting hostname...
==> vm1: Configuring network adapters within the VM...
==> vm1: Waiting for HGFS to become available...
==> vm1: Enabling and configuring shared folders...
    vm1: -- /home/<username>Vagrant/Ansible-Random/VMware-test: /vagrant
VMware-test git:(master)  >

The Vagrantfile content

# -*- mode: ruby -*-
# vi: set ft=ruby :

Vagrant.configure("2") do |config|
  config.ssh.username = "vagrant"
  config.ssh.insert_key = false

  config.vm.box_check_update = false

  # create vm1 node
  config.vm.define :vm1 do |vm1_config|
    vm1_config.vm.box = "ubuntu1604-my"
    vm1_config.vm.hostname = "powershell"
    vm1_config.vm.network :private_network, ip: "192.168.86.129"
    #vm1_config.vm.synced_folder "./sources/", "/vagrant"#, disabled: true
    vm1_config.vm.provider "vmware_workstation" do |vb|
      vb.memory = "2048"
      vb.gui = true
    end
  end

end

[Wojciech Sciesinski]

The related pull request: builder/vmware: Add vmx_remove_ethernet_interfaces #4927.

[Jeff Geerling]

Interesting... I wonder what the suggested fix is (for builders, vs. adding a patchy/hacky fix in a Vagrantfile)?

[Wojciech Sciesinski]

I analyze a content of vmx files for box and provisioned machines (with and without hacks) - more hopefully soon.

[Jeff Geerling]

Note that I'm not supporting VMware anymore in my projects; see #42