VMware Fusion 11.0.1 Release Notes



Fusion patches for the vmxnet3 VM escape exploit and the problem where Fusion fails to start if another virtualisation tool was running before Fusion starts.

via VMware Fusion 11.0.1 Release Notes

No internet access in Windows connection


I’ve had exactly this problem from time to time in Fusion recently. A quit and start of the Fusion app was required to fix it. If I’m seeing the same problem as this then there is a fix so you don’t have to quit and start Fusion. The OP is running Fusion 7 on macOS 10.13.4 which isn’t supported.

I’m running Windows 7 in VMWare Fusion 7.1.3 on a Macbook OS 10.13.4. I’ve been running Fusion for years. Right now the network connection is not working when I’m in my office. In Windows I get a 169.xx.xx.xx IP address and “no internet connection” when in bridged connection.

Source: No internet access in Windows connection

I’m running Fusion 10.1.2 on macOS High Sierra 10.13.6 and see this problem from time to time. The command to restart the Fusion netcli is:

sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli –start
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli –stop
sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli –configure

Note that the above lines are wrapped because bleh.

HT to https://vbrownbag.com/2014/03/restart-vmware-fusion-networking-from-the-command-line/ for the CLI snippit.

“Shockwave Flash has crashed” workaround for vSphere Web (Flash) Client | virtuallyGhetto


Im using the vSphere Web Client everyday at the moment and will also preference the HTML5 version over the Flash (phtoowe) version.

Chrome 61.0.3163.100 breaks Flash though due to a patch for an undisclosed zero-day which was in use in the wild. Impacts Chrome on Mac and Windows.

See the post below from William Lam over at VMW.

On Saturday, I started to notice that logins to the vSphere Web (Flex) Client stopped working with Google Chrome. Upon a successful logon, it would immediately crash with “Shockwave Flash has…

Source: “Shockwave Flash has crashed” workaround for vSphere Web (Flash) Client | virtuallyGhetto

Check that Windows license before you P2V


Another quick tip for those of you doing P2V’s. Check that Windows license type before you start the P2V. The main thing you want to watch out for is OEM Windows licenses. OEM licenses cannot be P2V as OEM licenses are forever bound to the hardware on which they are sold.

How do you tell what sort of license is Windows using? The Product ID is the key. You can tell what channel the media & key used to install Windows was from by the product ID. See here.

Obligatory Device Manager post


This is my obligatory “how to make Device Manager display non-present devices” post. If you’ve done any Windows P2V’s you know what I’m talking about.

Here is the MSKB.

And here is the detail.

set devmgr_show_nonpresent_devices=1
start devmgmt.msc

Microsoft FUD vs VMware round 2


There’s a new Microsoft & VMware drama brewing. Before I detail it though here’s a good recap of the first one.

This new drama is about MS Exchange 2010 DAGs with virtual servers on VMware HA.

Exhibit 1a and 1b are the VMware guides for deploying this solution.

Exhibit 2 is the Microsoft response saying that the VMware best practice guides are an unsupported solution.

Exhibit 3 is VMware’s riposte telling MS to suck it up, it works, get your act together and support it.

Protect your VMs from “That Guy”


This one made me laugh.

If you need to resort to something like this I think you might want to:

  • Consider changing (enhancing?) how your employees are selected/hired.
  • Investing more money and effort in your training.