Network Initialization Failed

[StephenB13]

Hi everyone.

I haven't managed to find any threads with anyone having this same problem. I just downlaoded Parallels Lite to try out running an older version of MacOS to test some things. Whenever I launch a VM I immediately get a message saying: "Network Initialization Failed. Your virtual machine will continue working normally but will have no network connection."

This happens long before the OS loads (or in the case just now after trying again, even before the OS has been installed). I've tried all of the suggested network troubleshooting option but most don't apply (I'm not running windows and the problem seems to be in Parallels not in the OS itself), and none of the others work.

I have selected "shared networking." But I have also noticed that I don't even have the option to choose bridged, and when I look at my network options it doesn't even list any of my network hardware.

I'm at a loss for what to do. I've restarted my Mac, I've uninstalled and reinstalled Parallels. I've installed parallels tools. Again the problem seems to be in parallels itself (or something in my host OS), not in the OS that's being hosted.

I'v attached a few screenshots of what I'm seeing. Please let me know if you have any questions or need any further information.

I'm running MacOS High Sierra updated to the latest version (though obviously I haven't installed Mojave yet). on my host computer. It's a 2017 5k iMac. 24GB of RAM.

Any suggestions?

 

[PaulM50]

Hi, I have upgraded to big sur beta 8, ran that command above, then recreated my vm and it works

 

[JesseH1]

sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist && sudo killall -9 configd

Yup, that did it for me too, after upgrading to Big Sur dev beta 8 (build 20A5374i).

I didn't need to recreate my VM or even restart it -- I started it back up from a suspended state and the bridged networking came up without missing a beat.

 

[RomainP1]

Same update to beta 8, I re imported my Bootcamp and still have the problem
ID 350260888

 

[Jon Drover]

Upgraded to dev beta 8, ran the script, and networking is working again.

 

[PeterH44]

Got it working but only as root, after running the shellscript.
Found no solution for the regular user. Anyone?

 

[Maria@Parallels]

Same update to beta 8, I re imported my Bootcamp and still have the problem
ID 350260888

Hello, did you try the Terminal command above?

 

[Maria@Parallels]

Got it working but only as root, after running the shellscript.
Found no solution for the regular user. Anyone?

The issue is still under investigation with Parallels Engineering Team.
We will update once solution will be available.

 

[GonzaloE1]

Same issue!

 

[Maria@Parallels]

Same issue!

Hello, please share with us your Parallels Desktop and macOS version.

Did you try to run the following command in Terminal while Parallels Desktop was not started:
sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist && sudo killall -9 configd

 

[EgieD]

I'm having the same issue and yes I ran the command. Still can't connect...

 

[Dr.m17]

me too the same issue

 

[jazzamac]

I ran the command and deleted my VM and created a new one. The VM had network access but my MacBookPro didn't (I couldn't get to any websites or network shares). As soon as I shut down the VM my MacBookPro was back to normal. I tried setting the VM to both shared and bridged network mode and it made no difference.

Uploaded the support logs: 350484011

 

[DonaldA3]

• macOS 11.0 Beta (20A5374i) [Big Sur]
• Parallels 16.0.1 (48919)
• Windows 10 Pro ISO

Ran the following command:
sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist && sudo killall -9 configd

Still getting the network error.

 

[Blondey]

I have the same problem!

- macOS Big Sur Beta 11.0 (20A5374i)
- Parallel Desktop 16.0.1​

 

[Blondey]

I also ran this command, but the error remained:
sudo rm /Library/Preferences/SystemConfiguration/NetworkInterfaces.plist && sudo killall -9 configd

 

[PaulM50]

Hi, I have upgraded to big sur beta 8, ran that command above, then recreated my vm and it works

Actually I missed a step in this. What I had to do was go into parallels preferences and restore defaults int he networking part. It seemed to keep creating new vnet adapters each time i fired up a vm. putting it back to defaults, then running that command, i notice it used the 2 default adapters, shared and host only, and then it works

 

[Sathiya@Parallels]

Actually I missed a step in this. What I had to do was go into parallels preferences and restore defaults int he networking part. It seemed to keep creating new vnet adapters each time i fired up a vm. putting it back to defaults, then running that command, i notice it used the 2 default adapters, shared and host only, and then it works

Nice to know that you were able to sort out the issue. Please get back to us for any further queries.

 

[ZeroCoolSpain]

Hi!!
I have found the solution. I know that if you open parallells in root session it works but I want to open parallells with my user session.

The solution?

sudo -b / Applications / Parallels \ Desktop.app/Contents/MacOS/prl_client_app

Try it and tell me.

 

[ZeroCoolSpain]

May be you need re-create VM

 

[PeterH44]

Hi!!
I have found the solution. I know that if you open parallells in root session it works but I want to open parallells with my user session.

The solution?

sudo -b / Applications / Parallels \ Desktop.app/Contents/MacOS/prl_client_app

Try it and tell me.

sudo -b?
for what command?