Separate names with a comma.
Discussion in 'General Questions' started by IvanD@Parallels, Jun 22, 2020.
Maybee it depends on the size of the RAM, I'm using 40GB.
Please, see the solution in this thread:
The Issue is related to Parallels hypervisor kext. You can switch to the Apple hypervisor under "Hardware - > CPU & Memory -> Advanced Settings" of your VM's settings, works for now until Parallels can fix it with an update.
Hi Mike, any Idea if this not works? I tried and my VM shows only then waiting circle an then the make freeze. If choose Parallels at the Hypervisor, my iMac is crashing emidiatly, so the behavior is different, but not working )):
I tried this with a Linux VM and it works. Unfortunately I had a Windows VM that was suspended (not shut down) when I ran the update for Beta 5. Is there anyway to force power off state on a suspended VM so I can make the configuration change? Not worried about data loss - its a test machine.
New issue, when I upgraded to Big Sur Beta 5 everytime I try to load one of the VM's my Mac crashes. EVERYTIME.
Thank you so much for this. I can tell you for Big Sur Beta 5 and Parallels Desktop 16, this works!
Remove the VM from PD, then add it back in. The VM should show up in its own window, then you can go into the menu and stop the VW.
If you are on the VM preferences dialog and these settings are disabled because the VM is suspended then just select the Actions-Stop menu. That will force the VM to shutdown and allow you to make this change. Worked like a charm for me!
This worked for me, too. Many thanks!
Great that this works, but its anyone else having atrocious performance with the Apple Hypervisor? Windows 10 barely boots and logging in is next to impossible. It won't use more than 10-15% CPU.
It works indeed but the guests systems run significantly slower. I hope the fix can come pretty soon.
Same here, actually I updated BS on Wednesday and yesterday Parallels was working fine, I launched it today and exactly the same thing, Mac crashes :S
Had the same issue... after changing to "Apple" hypervisor under hardware my windows now boots without causing a crash... thanks EvanR for the work-a-round
Network is dead after upgrading to Big Sur beta5. I have tried almost every option in network setup page
indeed, this solved the issue. I had instant crashes when booting Win10 Pro. Solved for now....
I crash after a few minutes upon signing in to my computer, after upgrading to Big Sur 20A5354i. I do not have to try to open a VM. I deleted Parallels, thinking that would solve the issue, but it still is affecting my machine.
I found some network issues, I added a manual dns in preferences (on macos) and it seemed to work
I'm not sure why, but as soon as I changed to Apple hypervisor my VM does work but very often it hangs, or works slowly - it becomes unresponsive. This is not a workable solution! - Using public Beta 2 20A5354i
How can I make this change when the computer crashes before Parallels can load?
It might be that you have parallels set up to start in the background when computer starts, and start a VM also when parallel starts, and if that's the case, you are going to be stuck