Windows VM crashing Mac ( Big Sur) on start

N

nanoplane

Bit poster
So I'm on Big Sur latest beta and I just upgraded / installed Parallels 16 and now my Windows VM crashes the mac when I try to start it. Parallels starts fine but when I try to start my Windows 10 VM, the screen goes black and you get the mac "crashed" screen with the multi-language white text and the mac reboots.
 
PeterJ18 said:
  1. Quit Parallels Desktop.
  2. Go to System Preferences > Security & Privacy > General, then click Allow button and enable (re-enable) Parallels International GmbH kernel extension.
  3. Restart the Mac and start Parallels Desktop and virtual machine again.
Click to expand...
I had already done that so now, I'm not given the option to "re enable".
Parallels starts up fine but the ma is crashes when I try to start a VM
 
same issue here, upgraded from 15 > 16 not were running good. Updated to latest Big Sur (build 20A5354i) parallels start but when you bootup a VM > mac crashes
 
I am also having my mac crash when starting a VM. Parallels worked fine prior to the 20A5354i update that installed this weekend.
 
I was experiencing the same issue. I asked @ParallelsCares if there was a fix, and here is their response:

"Hi- please change the hypervisor to Apple under VM configuration > Hardware > CPU & Memory> Advanced > Hypervisor > Apple then check."

I followed these steps and it worked for me! I am on a Macbook Air running Big Sur Public Beta 2, with a Windows 10 VM.
 
SimpleMath said:
I was experiencing the same issue. I asked @ParallelsCares if there was a fix, and here is their response:

"Hi- please change the hypervisor to Apple under VM configuration > Hardware > CPU & Memory> Advanced > Hypervisor > Apple then check."

I followed these steps and it worked for me! I am on a Macbook Air running Big Sur Public Beta 2, with a Windows 10 VM.
Click to expand...

It works!!! Thank u~~~
 
SimpleMath said:
I was experiencing the same issue. I asked @ParallelsCares if there was a fix, and here is their response:

"Hi- please change the hypervisor to Apple under VM configuration > Hardware > CPU & Memory> Advanced > Hypervisor > Apple then check."

I followed these steps and it worked for me! I am on a Macbook Air running Big Sur Public Beta 2, with a Windows 10 VM.
Click to expand...
it works!! thx
 
SimpleMath said:
I was experiencing the same issue. I asked @ParallelsCares if there was a fix, and here is their response:

"Hi- please change the hypervisor to Apple under VM configuration > Hardware > CPU & Memory> Advanced > Hypervisor > Apple then check."

I followed these steps and it worked for me! I am on a Macbook Air running Big Sur Public Beta 2, with a Windows 10 VM.
Click to expand...

Worked for me as well, Thanks!!
 
SimpleMath said:
I was experiencing the same issue. I asked @ParallelsCares if there was a fix, and here is their response:

"Hi- please change the hypervisor to Apple under VM configuration > Hardware > CPU & Memory> Advanced > Hypervisor > Apple then check."

I followed these steps and it worked for me! I am on a Macbook Air running Big Sur Public Beta 2, with a Windows 10 VM.
Click to expand...
I tried this but it won't give me access to the Hypervisor drop down. IT's greyed out. How do i get access to that area?
 
Here is a workaround to updating your Hypervisor setting if you cannot make the change in the configuration - due to being unable to resume the VM.
  1. Locate your VM file for this virtual machine.
  2. Right click on the VM file and select "Show Contents".
  3. Locate the file (which should be at or near the top) that is called "config.pvs"
  4. Open this file with TextEdit.
  5. Select the ENTIRE file and copy it.
  6. Open another text file on your desktop and paste the copied contents into this new file. Name it whatever you like, and save it. This is your backup in case there is a catastrophic problem.
  7. In the "config.pvs" file, locate this line:
    <HypervisorType>0</HypervisorType>
  8. Change the "0" to "1".
  9. Save the file
  10. Now retry starting your VM.
This was what Parallels Support just did for me, and it works now.

Hope this is helpful.
 
LeeFuller said:
Here is a workaround to updating your Hypervisor setting if you cannot make the change in the configuration - due to being unable to resume the VM.
  1. Locate your VM file for this virtual machine.
  2. Right click on the VM file and select "Show Contents".
  3. Locate the file (which should be at or near the top) that is called "config.pvs"
  4. Open this file with TextEdit.
  5. Select the ENTIRE file and copy it.
  6. Open another text file on your desktop and paste the copied contents into this new file. Name it whatever you like, and save it. This is your backup in case there is a catastrophic problem.
  7. In the "config.pvs" file, locate this line:
    <HypervisorType>0</HypervisorType>
  8. Change the "0" to "1".
  9. Save the file
  10. Now retry starting your VM.
This was what Parallels Support just did for me, and it works now.

Hope this is helpful.
Click to expand...

I am having the same issues but how do I access the VM file if I cannot get into the Window 10 OS?
 
I actually figured out the VM file and changed the 0 to 1 and went through those steps but when you say to retry starting the VM, it still crashes on me.
 
How
SimpleMath said:
I was experiencing the same issue. I asked @ParallelsCares if there was a fix, and here is their response:

"Hi- please change the hypervisor to Apple under VM configuration > Hardware > CPU & Memory> Advanced > Hypervisor > Apple then check."

I followed these steps and it worked for me! I am on a Macbook Air running Big Sur Public Beta 2, with a Windows 10 VM.
Click to expand...
How do I get to the hypervisor if I can't even get the VM to open without my Mac crashing? How did he get you in?
 
RebeccaK2 said:
I actually figured out the VM file and changed the 0 to 1 and went through those steps but when you say to retry starting the VM, it still crashes on me.
Click to expand...
That's odd, Rebecca. Hmm. Are you 100% certain you are editing the correct file? We had this happen on three of our machines, and this fix corrected all of them. Hmmm..
 
You must log in or register to reply here.
Back
Top