DC Challenges - VMware Issues

Issues with VMware

I heard some reports that there were some issues with some of the VMs working in VMware Player/Workstation.

The short version is that the VMs would boot up, but networking wasn't working at all.

I did some digging and came across this video which explains why it wasn't working (I recommend reading the comments as well).

What it comes down to is this:

If you're using Bridged Networking, VMware Player apparently gets "confused" working out which network card it should use when you have multiple Network Interface Cards (NICs).

And so, it does nothing.

There used to be a utility called "vmnetcfg.exe" that used to help fix this, but VMware in their infinite wisdom decided to exclude it from more recent versions of VMware Player.

You can, however, still get a copy by downloading the full VMware Workstation, but you'll need to install it (which uninstalls VMware Player), copy the file to another location, uninstall VMware Workstation, reinstall VMware Player, and then copy the "vmnetcfg.exe" file into the C:\Program Files (x86)\VMware\VMware Player folder.

Then you just need to follow the instructions in the video.

Also take note, that I've had to apply a workaround to avoid issues with the way that recent versions of Linux name their network interfaces (Predictable Network Interface Names). I found that when they were being imported into VMware, /etc/network/interfaces would need to be manually updated to reflect the different names.

The short version is that this can be disabled via Grub, so this is what I have done. The main interface will now show up as eth0 instead of enp0s3 or ens33.

Alternatively, just switch to VirtualBox and avoid all the hassle.

You can even have VMware Player and VirtualBox installed at the same time (like I currently do).

Contact

If you do happen to have any problems with these VMs, please let me know. I can't guarantee I will fix any problems, but I'll do my best.

I can be contacted via Twitter - @DCAU7