The crash is a complete crash of the VMware process and makes the VM lose state, it's just like pulling the plug. This seems to happen when I try to connect to a VPN inside my Windows 7 VM. Locate the below (search virtualDev or e1000e) in your VM's VMX file (option+right click on your VM, select 'Open config file in editor'. I'm running my network interface in the NAT mode as if I run bridged I'll be detected as a rouge system and blocked. I'm running MacOS High Sierra (10.13.6) as my host system with VMware Fusion Professional 10.1.1.
#Vmware fusion for mac network not working upgrade
Quite a shame really, but looks like there is no choice but to pay for a new license or license upgrade if you need to keep running VMs on your Mac and want to run the latest macOS.Īfter running the new VMware for a while I am having my VM crash from time to time. In this release, if we don’t use the NIC type ‘vmxnet3’, we will have issues getting an IP Address in the VM. Previously this was an intermittent problem, but over the past three days it's become persistent and keeping me from doing my work. So there you have it, unless you have the latest version of Fusion, good luck running it on Sierra. However, after restarting I was able to get things rolling.
I decided to go for the 30-day trial to see if everything would work and installed the latest VMware Fusion 8.5. Unfortunately my 6.x license could not be used for 8.5.
That explicitly states that Sierra is supported. So, I thought I'd go and check the compatibility matrix for the 8.5 version of Fusion. I also tried restarting several times to make sure it wasn't an issue with unloaded KEXTs, that didn't help at all.Īlright at this point I was annoyed and realising that maybe I needed to upgrade. The odd thing, when running lsof, and looking for anything that had these files locked, nothing came up.
0 kommentar(er)
