Static IP Address Is Not Assigned to Windows Guest with VMWare Provider

[vitaminac]

Vagrant version

Vagrant 2.2.19. This is the latest version by the time of 2022-Apri-17.

Host operating system

• Windows 11 Home 21H2 build version 22000.613
  • OS Version that is obtained from systeminfo command: 10.0.22000 N/A Build 22000
• VMWare Workstation 16 Pro version 16.2.3 build-19376536
• Vagrant VMWare Utility version 1.0.21
• Vagrant VMware Desktop plugin version 3.0.1

Guest operating system

Derived from Windows 7 Ultimate SP1 2019 ISO, os version is 6.1.7601 Service Pack 1 Build 7601 that is obtained from systeminfo command.

Vagrantfile

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

Vagrant.configure("2") do |config|
  config.vm.box = "vitamina/Windows7"
  config.vm.box_version = "2.0"
  config.vm.communicator = "winrm"
  config.vm.network "private_network", ip: "192.168.50.15"
  config.vm.provider "vmware_desktop" do |vm|
      # Display the VMWare GUI when booting the machine
      vm.gui = true
  end
end

Debug output

The output of command vagrant up --provider=vmware_desktop --debug is

https://gist.github.com/vitaminac/5f265f71af18866429628ed2d3f82065

Expected behavior

The output of ipconfig in guest contains 192.168.50.15

Actual behavior

The output of of ipconfig in guest is

Steps to reproduce

1. Install VMWare Workstation 16 Pro
2. Install Vagrant VMware Utility
3. Install Vagrant VMware Desktop plugin
4. Reset VMWare network configuration by going to application Virtual Network Editor > Restore Defauls (This step is optional if you have clean install of previous softwares, just to ensure you have same initial network setting as I have)
5. Execute vagrant up --provider=vmware_desktop with Vagrantfile that I've provided
6. Execute ipconfig in Windows guest after the provision is done

References

• Vagrant IPs are not getting assigned correctly #12707
• vagrant private_networks & VMware #10256
• Vmware provider is not using static ip #5461
• VMWare Workstation Secondary Network Adapters on Windows #5000
• Issue with VMware provider
• Vagrant: Private Networks
• Vagrant: VMWare Provider Installation
• Vagrant: VMWare Provider Configuration
• How to Create a Windows7 Vagrant Base Box

[ChristoWolf]

If I remember correctly, I encountered the same issue quite some time ago.
Unfortunately, I don't have the possibility to check at the moment, and I can't find according documentation (which I know exists), but I'm pretty sure that auto_config does not work for the VMware provider.

I'll try to check again in my own documentation if that was the reason as soon as I can.
Maybe it was also part of the vagrant up stdout, but I couldn't find it in yours.
Worst case, you would have to configure the NIC on your own during provisioning.

[ChristoWolf]

@vitaminac: I even remembered the issue, so I remembered correctly :)
In particular the solution was exactly what I suggested before.