macOS Big Sur and Parallels Desktop

I found this here and fixed my issue.
https://developer.apple.com/forums/thread/649774


I was able to get past the "BIErrorDomain error 3" issue in Parallels as follows:

  1. On a real, supported Mac, run this command in Terminal:
Code Block
ioreg -l | grep board-id

2. Make a note of the board ID (mine is Mac-551B86E5744E2388, for example)
3. Run this command in Terminal:
Code Block
sysctl hw.model

4. Make a note of the hardware model (mine is MacBookPro14,3)
5. In the VM configuration, under Hardware -> Boot Order -> Advanced Settings -> Boot flags, enter the following (inserting the information noted above where shown):
Code Block
devices.mac_hw_model="<model>"
devices.smbios.board_id="<board ID>"


That should be enough to allow the installer to proceed.
I wonder why this is working for some and not others.
 
I am a moron. I had my values switched. :( Once I corrected that and expanded my volume to 128GB it is upgrading. I also uninstalled parallels tools just to be safe as I have seen issues with that as well.
 
I am a moron. I had my values switched. :( Once I corrected that and expanded my volume to 128GB it is upgrading. I also uninstalled parallels tools just to be safe as I have seen issues with that as well.
And now I am at the login screen with the same issues as everyone else. Enter password, spins, black screen, back to login screen. Rinse repeat.
 
how did you uninstall them? if you don't log in I don't see the disk to uninstall the tools ...
I returned the Parallels VM to a snapshot of Catalina, then asked Parallels to mount the Parallels Tools 'CD'. This has two programs, one to install the tools and the other to uninstall them.
 
I installed the Big Sur beta on a 2018 Mac Mini (host OS) and found that the "t" and "y" keys don't work in any Parallels VMs. I noticed that right away on a Windows 10 VM and also found that the keys didn't work on a Linux live boot CD. Creating a custom entry send-key for "t" and "y" does work - had to do that to enter a password :)

Other than that obviously important issue, I was pleasantly surprised that everything else seems to generally work under Big Sur.

I know this is completely unsupported by everyone involved, but any guesses on a workaround? I didn't see many options to try fiddling with in terms of keyboard settings.
Was this issue resolved? Any workaround?
 
At least you get a screen...all I have after booting is a blank (black) screen...has anyone else experiencing this?...thanks!
Did you install Parallels Tools? Seems that might be causing the blank screen. I experienced that too. I did the install again without installing Parallels Tools. I a now stuck on the login screen.
 
Another one to the chorus of user with Win10 Issues:
- 1,t,y keys fail to work (I got around that with a work around)
- Windows 10 crashes after sign in right before the desktop displays.

What workaround would that be, please? I to am highly annoyed by being unable to type the mentioned letters.
 
This might be a dumb question but, how is everyone creating their install media? Every time I try I get this error:

Code:
Couldn't extract BaseSystem to path: /Volumes/Install macOS Beta/BaseSystem
The bless of the installer disk failed.

These are the steps I followed:

Code:
hdiutil create -o /tmp/BigSur.cdr -size 10000m -layout SPUD -fs HFS+J
hdiutil attach /tmp/BigSur.cdr.dmg -noverify -mountpoint /Volumes/install_build
sudo '/Applications/Install macOS Beta.app/Contents/Resources/createinstallmedia' --volume /Volumes/install_build

At which point I get the error above.
Damn me too. Anyone have any ideas? They have the .iso on less than reputable sites and lord knows what you will get along with your OS.
 
After upgrade, my Windows 10 VM can not start, Parallels keeps telling me "To complete Parallels Desktop setup, please restart your Mac.". Then Parallels became No Responding after click any button. After restart mac, nothing changed.
Did anyone find a resolution to this? I tried the "spctl kext-consent add 4C6364ACXT" trick but that did not work.
 
I tried following DanF10's instructions to set the boot flags, but I'm still getting the BIErrorDomain error 3. Host computer is an iMac Pro running 10.15.5.

I just sent in technical data 343342137. I hope it helps.
 
Big Sur runs fine (fresh VM, fresh Big Sur installation via DMG) until I install Parallels Tools via Actions / Reinstall Parallels Tools. After the reinstallation of Parallels Tools and after all permissions are granted via System Preferences / Privacy the VM gets stuck in a black screen after the reboot.
Report ID: 343276075
Thank you for the provided tech report. We've involved Parallels Engineering team for this case.
Once we get any updates we will let you know.
 
I am unable to upgrade from 10.15.6 Beta (10G46c), I am receiving the following error:
The operation couldn't be completed. (BIErrorDomain error 3.)
I have tried installing on the same HD as the Catalina Beta and also tried adding a new HD but the same issue...
I'm using Parallels Desktop 15 Pro Edition
Version 15.1.4 (47270)
Hello, please check your inbox and reply us back.
 
I could only install Parallels 15 on Big Sur after removing a previous installation of VirtualBox. (It had kernel extensions that messed up the dependencies of Parallel's kernel extensions.) Even after getting Parallels running, its kernel extensions are still shadowed in /Library/StagedExtensions/Applications/Parallels Desktop.app, even though they successfully load. Parallels doesn't quit gracefully; I have to force-quit it.

I too noticed the bizarre bug of the "t", "y", and "2" keys not registering unless I create modifier-key-less shortcuts for them in the Parallels preferences. That's almost a usable workaround... in another bizarre twist, there's a short delay after typing shortcuts, during which no other key registers. E.g., if you type "tu" in rapid succession, you just get "t", but if you wait a little bit in between you get both characters. I hope this weird bug is easy to squash, because it's extremely annoying. :)
Hello, could you collect the tech report after the issue reproduced please?
We need it for the further issue investigation.
Looking forward to your reply.
 
Back
Top