![]() T23:19:20.686-08:00| vmx| I005: DictionaryLoad: Cannot open file "/Library/Preferences/VMware Fusion/config": No such file or directory. T23:19:13.660-08:00| vmx| I005: Vigor_EthernetScheduleReconnect: reconnect delay = 7 seconds, reconnectEthVector = 0x1 Here's what shows up in vmware.log when I try to connect the network adapter: Started all configured services on all networks $ sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli -startĮnabled hostonly virtual adapter on vmnet1Įnabled hostonly virtual adapter on vmnet8 ![]() $ sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli -stop Stopped all configured services on all networksīacked up existing network settings to backup file "/tmp/vmware.SpI1rT" $ sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli -configure $ sudo rm /Library/Preferences/SystemConfiguration/ist & sudo killall -9 configd VMWare Fusion Professional Version 12.1.0 (17195230).This is a real problem because one of the Windows apps I need phones home to a licensing server at every launch. But sometime today, it changed and none of my VMs work any more. Strangely, networking seemed to work just fine for a day or two after upgrading to Big Sur. None of these use NAT or VPN, just simple NIC configs all working prior to upgrade to Big Sur and VMware 12 Pro.Īll of my VMs are without network access under Big Sur and Fusion 12.x. Again had many linux vm's for Cisco, Aruba/HPE, etc and most of them started working again after going e1000 (nothing else works) and the "other linux/64-bit" vm's without the driver showing never complain but can never talk no matter what physical NIC I connect to them to, no matter the combination. ![]() My linux based vm's that don't specify a driver file I have worked endless days without ability to get them working. vmx file for the guest vm with e1000 again regressing back from 10gb to 1gb, but at least those vm's are back to working. none did at first but I was able to get freebsd, windows, and apple based vm's working again by replacing the vmxnet3 driver specified in the. I have many vm's and some work, some dont. Version 12.1.0 doesn't fix it for me, I no longer get the pop up stating it cannot connect to the vmNetX connection, no errors at all actually but despite the interfaces showing up in the vm nothing connects. Seems like we need to wait for the product developers to fix this bug. Tech also tried switching the adapter from NAT to bridged mode, then connect the adapter (failed), then switched back to NAT mode and connect the adapter (failed). Sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli -start Sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli -stop ![]() They didn't but I'll share them here in case others want to try it: sudo /Applications/VMware\ Fusion.app/Contents/Library/vmnet-cli -configure In case it's helpful to others, there are a few commands we ran on the command line which the tech thought might resolve these issues. Note: I also uninstalled my Bitdefender antivirus since it has a built-in VPN client (which sucks, but that's another story). Folks having the same issue can try uninstalling all VPN clients to see if their issue is resolved. I was not using a VPN but had clients installed, we uninstalled them but it did not help. Tech was initially focused on any VPN client I have on my machine since there are known issues with Fusion 12 while using a VPN. To be clear, I'm talking about the inability to connect Ethernet0 when the VM starts or when it's running. It appears to be a known issue/bug and has been escalated to engineering to resolve, the support tech tried a bunch of things with no luck so they're collecting the logs and will need more time to fix the issue. Just had my first call with VMware tech support (after waiting several weeks to get started).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |