Big Sur Beta 6/7/8 - Network Initalization Failed

B

BrianV5

Bit poster
When starting Parallels 16.0.1 on Big Sur Beta 6, 7 or 8 -- You get a Network Initialization Failed error message.
Unable to use any networking in the virtual machine.
 
BTW -- I'll mention the only reason I'm trying parallels, is because VMWare Fusion has the exact same problem, yet a BUG report I've filed with Apple came back with "3rd party change required" --- when all of this worked under beta 5. Sounds like Parallels, VMWare and Apple need to all get along on this issue.....
 
Hello,
please try the following workaround:
  1. Shut down the virtual machine and quit Parallels Desktop.
  2. Open Terminal (Applications > Utilities > Terminal), copy and paste the following command and press Enter:
    sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist && sudo killall -9 configd
  3. Then prompted, enter your Mac's password and press Enter (Terminal doesn't show the password as you type).
  4. Restart the Mac.
 
Hello guys, we would like to inform you that Parallels Desktop update 16.1.0 has been release recently.
Please update your Parallels Desktop version to the latest build and check the issue.
Please share any results with us.
 
Hi Maria,

I am with Parallels Desktop 16.1.0 (48950) and Big Sur 11.0.1 on iMac Pro 2017.
If I choose Shared Network and run CentOS 7.8 with DHCP enabled, I can access network.
I've tried other choices (Ethernet/Default Adapter, my preferred choice), none of them works.
With working choice (Shared Network and DHCP enabled), I couldn't make Cisco VPN work... *sigh*
Tammy
 
Hello Maria,

I am with Parallels Desktop 16.1.0 (48950) and Big Sur 11.0.1 (20B29) on Mac mini (2018).
Before I used bridged-network with bond0 this is not available anymore, I tried all other adapters and the terminal solution, no change.
I cannot access the WinVM by RDP and no network connection in the VM itself.
I hope a solution will arrive soon.

Tom
 
I have Parallels Desktop Version 16.1.0 (48950) installed on an iMac (Retina 5K, 27-inch, Late 2014) (iMac 15,1; i7 and 32GB main memory).
I run several VMs with Win10. Under Catalina, all worked well with networking provided by bridged networking using "Default Adapter", with a wired ethernet connection to the built-in NIC.

After upgrading to macOS Big Sur version 11.0.1 (20B29) this didn't work anymore: Win10 couldn't connect to the network. Setting "Shared Network (recommended)" did work, but had the disadvantage that the VMs didn't integrate into the rest of my LAN anymore (DHCP, DNS, IP white list, QoS settings etc), but received addresses in a, well, parallel LAN devised by Parallels. That is, connecting to drives etc. on the LAN from the VMs is no problem, but they cannot be found by name anymore by other nodes on the LAN. Changing to "Ethernet" bridged mode didn't do the trick, by the way, and neither did the "workaround" involving deleting /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist.

After some tinkering I found that using Wifi (slow: ~ 120 Mbs), or an Apple thunderbolt-to-ethernet adapter/dongle for the ethernet cable (fast: 1 Gbs), everything did work again in bridged mode--i.e. after setting "Default Adapter" (or "Thunderbolt Ethernet" or "Wifi") the VMs had network access again, and were first-class citizens of the LAN once more.

In short, the upgrade to Big Sur seems to have "broken" the bridging functionality of Parallels Desktop for the built-in ethernet port (NIC).

If Apple is right, and it is a matter of "3rd party change required", as BrianV5 suggests, you might want to look into this.
 
Thanks to the description of MarinusB I tried with the dedicated adapters. Standard, en0 and en8 (usb-ethernet adapter) didn't work, maybe as they are on the Mac used as bond. Only an IP in 169... area could get in that configuration, acknowledged by the router but no internet connection possible with this, manual or dhcp didn't work as well. I switched on Wifi then (not preferred for me on the Mac, but toggle a try). The Wifi adapter in parallels works. So I can access the Win10 VM by RDP again and the VM has as well internet connection.
I hope that this will be solved soon. Maybe as well to allow to use the bond0 in full speed.
 
TomE4 said:
Thanks to the description of MarinusB I tried with the dedicated adapters. Standard, en0 and en8 (usb-ethernet adapter) didn't work, maybe as they are on the Mac used as bond. Only an IP in 169... area could get in that configuration, acknowledged by the router but no internet connection possible with this, manual or dhcp didn't work as well. I switched on Wifi then (not preferred for me on the Mac, but toggle a try). The Wifi adapter in parallels works. So I can access the Win10 VM by RDP again and the VM has as well internet connection.
I hope that this will be solved soon. Maybe as well to allow to use the bond0 in full speed.
Click to expand...

I found a workaround for my system. As I said. I got things working again with the ethernet wired connection using an Apple thunderbolt-to-ethernet adapter/dongle. However, when I changed its hardware settings to support MTU = 9000 (jumbo packets), networking from the VMs failed with that interface as well. And when I tried the built-in NIC ("ethernet"), with MTU = 1500 ("standard"), the VMs appeared on the network again. So it seems that Parallels Desktop bridging in Big Sur fails when you use jumbo frames! @ TomE4, maybe could you try the same?
By the way, the macOS native system is quite happy to use jumbo frames itself--it is just not working with the VMs connected in bridged mode...
 
Hi,

same problem here. With Jumbo Frames all VMs failed to communicate over the build-in 10GB Networkchip in my MacMini from 2019. If I toggle it to 1500 all works fine like bevor the update to big sur. I hope this will fix soon.
 
TomE4 said:
Hello Maria,
I am with Parallels Desktop 16.1.0 (48950) and Big Sur 11.0.1 (20B29) on Mac mini (2018).
Before I used bridged-network with bond0 this is not available anymore, I tried all other adapters and the terminal solution, no change.
I cannot access the WinVM by RDP and no network connection in the VM itself.
I hope a solution will arrive soon.
Tom
Click to expand...
Hi, just one more question; did you try the default adapter?
 
Maria@Parallels said:
Hi, just one more question; did you try the default adapter?
Click to expand...

See my initial comment of MarinusB, Saturday at 11:58 AM: I tried "default adapter", but no joy. Using the built-in Ethernet adapter with "standard" (i.e. non-Jumbo) MTU worked, as did (indirectly selecting it) setting "default adapter" (see my comment MarinusB, Sunday at 9:31 PM) Conclusion: the problem has to do with using Jumbo frames, and occurs with Big Sur--with Catalina everything worked fine. By the way, I just updated to Parallels Desktop Version 16.1.1 (49141), to no avail.
 
I have the same issue. Mac Pro, dual 10Gb, trunk ports from the switch, trying to bridge vlan 35. It worked on catalina does not work on big sur. Shared is the only thin working. I had jumbo frames on, I have tried it both ways, this is crippling. Please advise
 
since i updated my macbook pro to BIGsur i have been geting
network initialization failed
your virtual machine will continue working normally but will have no network connection
I'm also using parallels desktop business edition latest version 16.1
and I still get that error
please can anyone help
 

Attachments

  • Screenshot 2020-11-26 at 12.08.55 AM.png
    Screenshot 2020-11-26 at 12.08.55 AM.png
    189.4 KB · Views: 10
Hi, iMacPro updated to BiSur 11.0.1, Parallels Business Edition 16.1.1 (49141): Same problem! With Ethernet adapter is not working, WiFi is working fine. I have a MacBook Air and the same problem, just the reverse! WiFi not working, Etc working fine.
It seems that the upgrade has broken the card "in use"...
Please help us!
 
You must log in or register to reply here.
Back
Top