Vagrant 1.9.5 & VMware Workstation 12.5.6 - Networks not coming up

[Ian Koenig]

day at 13:03

Hi,

I'm running into an issue with the Vagrant Plugin for VMware on Windows 10.

• VMware Workstation Pro 12.5.6 
  
• Vagrant 1.9.5 
  
• VMware Workstation Plugin 4.0.19
  

My Vagrantfile:

BOX_IMAGE = "centos/7"
Vagrant.configure("2") do |config|
    config.vm.define "service" do |subconfig|
       subconfig.vm.box = BOX_IMAGE
       subconfig.vm.hostname = "service"
       subconfig.vm.network :private_network, ip: "192.168.47.50"
    end
end

When I do a vagrant up, it gives an error of

======== 

==> service: Setting hostname... 

The following SSH command responded with a non-zero exit status. 

Vagrant assumes that this means the command failed!

# Update sysconfig 

sed -i 's/\(HOSTNAME=\).*/\1service/' /etc/sysconfig/network

# Update DNS 

sed -i 's/\(DHCP_HOSTNAME=\).*/\1"service"/' /etc/sysconfig/network-scripts/ifcfg-*

# Set the hostname - use hostnamectl if available 

echo 'service' > /etc/hostname 

if command -v hostnamectl; then 

hostnamectl set-hostname --static 'service' 

hostnamectl set-hostname --transient 'service' 

else 

hostname -F /etc/hostname 

fi

# Prepend ourselves to /etc/hosts 

grep -w 'service' /etc/hosts || { 

sed -i'' '1i 127.0.0.1\tservice\tservice' /etc/hosts 

}

# Restart network 

service network restart

Stdout from the command:

/bin/hostnamectl 

Restarting network (via systemctl): [FAILED]

Stderr from the command:

Job for network.service failed because the control process exited with error code. See "systemctl status network.service 

" and "journalctl -xe" for details. 

===============

What I see is in the settings for that VM, it is setup for the private_network adapter to be set to say "vmnet19". The adapter in VMware Workstation is named "VMnet19" which is case sensitive. If I change the adapter to be "VMnet19" in the VMX file, it works as expected.

Any thoughts on how to fix it or when VMware Workstation broke it?  

[Alvaro Miranda Aguilera]

Hello

Can you send an email to support @ hashicorp.com ?

Thanks

alvaro

[Ian Koenig]

Thanks.  Ticket #3782 made on this.

[Ian Koenig]

There's been zero movement other than having someone assigned.  What can we do to have someone engage on this?  

[Ian Koenig]

How can I get this moving Alvaro?   This is holding up a potentially decent sized order of vagrant-vmware-workstation plugin.   We can't use virtualbox in our environment due to other security software we utilize (it causes virtualbox to BSOD the windows systems) and the capabilities that vagrant offers is HUGE for what we are doing.   VMware Workstation doesn't trigger this BSOD in my testing and if I could prove it to work with vagrant as a true PoC we can go ahead.  

I see in the debug output where the hiccup in the code is

Thanks.   

[Ian Koenig]

Thanks for helping on this Alvaro.

[Chris Gannon]

Hi Ian, 

What was the resolution to this issue? We're seeing a similar issue in our environment. 

Regards, 

Chris