macOS Big Sur and Parallels Desktop

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.
Same exact problem here after I installed Big Sur beta on 2019 Mac Pro. The letters "t" and "y" don't work but the numbers "1" and "2" also don't work for me (this is on a bluetooth keyboard, btw). I can do a capital "T" and "Y" and ! and @. I've removed and re-installed Parallels and Toolbox, tried wired keyboards instead, tested on another VM (Ubuntu) but those same keys do not register at all.
 
Here are the solutions for all problems,
  • Before creating Catalina VM don't forget to resize disk size to 80 GB (at least)

  • Format 80 GB disc with using APF format before starting Catalina installation (otherwise you cant use 80 GB)

  • After Catalina VM installation start necessary update from Software Update, version will be 10.15.5

  • Copy "Install macOS Beta" (9 GB SUR installation file) to the Applications

  • Create 2nd Admin user and leave password blank (you will use it while login to SUR)

  • Don't install Parallels Tools

  • Copy current Catalina VM to external disk as a backup

  • Complete below process (run Terminal on the real MAC not VM)
a. On a real, supported Mac, run this command in Terminal: Code Block
ioreg -l | grep board-id

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

d. Make a note of the hardware model (mine is MacBookPro14,3)
e. 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.machwmodel="<model>"devices.smbios.boardid="<board ID>"

at the end of this process,
You will get two lines like below,

devices.machwmodel=MacBookPro13,4

devices.smbios.boardid=Mac-53FDB3D8DB9CA971
  • Shotdown the Catalina VM and put above two lines to the In the VM configuration, under Hardware -> Boot Order -> Advanced Settings -> Boot flags

  • Start Catalina VM again login with standart user (not login with the new created account)

  • Run "Install macOS Beta" from applications (copied SUR Installation file)

  • Wait approximately 45 mins. login with new account

  • Thats all
Note: In this method you don't need to login apple developer site for verification etc.
Selma0 - Is it devices.machwmodel or devices.mac_hw_model?
 
For those who have been trying to run Big Sur as a guest OS in Parallels, this solution is clean and works:

First, I did this in Parallels 15 for Mac "home edition". I'm running on a 2017 iMac w/ 32 GB RAM with Mojave as my system OS

Also, I saw almost every different error that people have been reporting and this method avoided all of them (so far, at least)

1. Make an installer DMG from the downloaded "Install macOS Beta" app. The technique to make one is available via Google but I used the one described here: https://developer.apple.com/forums/thread/649774 It's a series of 6-7 command line strings but not too tough

2. Get the correct board_id and hw_model information about your particular Mac:
  • In Terminal, on the Mac that's running Parallels type (or copy/paste)
    ioreg -l | grep board-id <- that's a dash and lower case L, then the pipe character, FYI
  • copy the Mac-xxxxxxx text for use below
  • then type:
    sysctl hw.model
  • copy the hardware model string for use below

3. Create a New VM in Parallels. Don't try upgrading a previous macOS version VM. Also, unless I state otherwise, leave settings @ their default
  • click the + button or select File->new in Parallels control center
  • select "Install Windows or another OS from...", click Continue
  • select the DMG you created in step #1, click Continue
  • name the VM and check "Customize settings before installation" & click Continue
  • Parallels will open its familiar Configuration dialog:
    • click the Hardware tab
    • I set the RAM to 8GB and processors to 4 - but I was being a bit paranoid. I think processors @ 2 is probably OK
    • for Graphics, I set Memory to 512MB with "Scaled" graphics - again, being a bit paranoid, not certain 512MB is required
    • for the Hard Disk, open Advanced Settings, click Properties and increase the size to 128GB. Click Apply, then Close
    • in Boot Order, open Advanced Settings and copy-paste the following lines: (note, Parallels failed to save these lines a couple of times until I copy-pasted them one at a time and hit return after each line - go figure. If your install fails, double-check this setting)
      devices.mac_hw_model="iMac17,1" <- replace inside the quotes with your mac model from step #2
      devices.smbios.board_id="Mac-XXXXYYYZZZ" <- replace inside the quotes with your mac board_id from step #2
  • close the Configuration dialog and click Continue
  • follow the instructions for normal installation going forward
  • while it's installing, call your parents and check in. they worry
*** Note - do NOT install Parallels Tools at any point. This is what results in the "stuck at black screen", the "won't let me log in, just kicks me out" problem and probably other issues. It's also one of the reasons why upgrading a previous macOS VM fails as it probably already has Parallels Tools installed. Like me, at this point you probably just want to get Big Sur running and can live without PT until Parallels updates it.

Many of the above steps and information was gleaned from other intrepid users posting to this forum and others and I thank you all.

regards and good luck
Steve in Seattle
(not nearly as crazy here as some have reported)
 
Finally got it working.
0. Create virtual machine and click configure to format hard drive to APFS with 90GB space
1. Install macOS Cat
2. Install all the updates
3. Create a new user account with admin right and without password
3. Shutdown
4. Insert required entry to boot option (boot flag)
6. Power On
7. Run Beta Utility.dmg to check for macOS Big Sur update
8. Download and install
9. Login as new user that you created before without password
10. Complete initial setup process
 
Hi, Did anybody face this, after installing Mac OS Big Sur on a parallels VM (upgrade from 10.15.6), I am stuck at the log-in screen, it accepts the password cursor keeps circling and then screen goes dark and comes back to the log-in screen again.
I see the same behaviour. I saw reports that it is required to have to have an account that uses an AppleID that is registered as a developer on the device. Sounds weird, and of course I can not create any account if I can not log in...
 
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.
I have the same issue - the T, Y, 1, and 2 keys do not work. You can hold down the fn key and they work, but really a strange bug...
 
This is all waaaaaaaaaaay too much trouble. I wasted 24 hours of my life on it and I refuse to waste one more second. Let me know when it works without having to mutter magic spells.
 
I see the same behaviour. I saw reports that it is required to have to have an account that uses an AppleID that is registered as a developer on the device. Sounds weird, and of course I can not create any account if I can not log in...
You should create user account after masOS Catalina is installed. Make sure the user account is created without password. After that you can continue with masOS Big Sur update. Once the update is complete please login using the user account you created before. It works....
 
This is all waaaaaaaaaaay too much trouble. I wasted 24 hours of my life on it and I refuse to waste one more second. Let me know when it works without having to mutter magic spells.
Same here as well. Yet, I was able to successfully install. Now going to do the same on VMWare workstation and see what happens.
 
I see the same behaviour. I saw reports that it is required to have to have an account that uses an AppleID that is registered as a developer on the device. Sounds weird, and of course I can not create any account if I can not log in...
You don't have to create anything on Apple website. All done within macOS Catalina - System Preference
 
Selma0 - Is it devices.machwmodel or devices.mac_hw_model?

devices.machwmodel=MacBookPro13,4
devices.smbios.boardid=Mac-53FDB3D8DB9CA971

Those info are sample, your computer devices.machwmodel and devices.smbios.boardid different, use terminal to collect information. Clear?
 
Below two lines are working on my virtual machine
devices.mac_hw_model=MacBookPro15,4
devices.smbios.board_id=Mac-53FDB3D8DB8CA971
OK thanks for the info. Yes above config did work. I did replace the model and board as, I have a older model at home.
 
I never used that and i searched for it and found nothing.
Fair enough, sorry I don't have more to offer on this situation. Hopefully someone else has something of value to add to your situation, good luck! If I discover anything, I will post here.
 
Same here as well. Yet, I was able to successfully install. Now going to do the same on VMWare workstation and see what happens.

Well, I was fool enough to let you talk me into it, so I can't blame you. I followed your instructions to the letter and got precisely the same results. Shame on me for not following my own advice and dropping the matter.

I'd strongly prefer an official, iron clad, gold-stamped solution from Parallels that's is 100% guaranteed to work. Otherwise, I won't be trying again with craptastic beta.
 
Same here as well. Yet, I was able to successfully install. Now going to do the same on VMWare workstation and see what happens.
I'm not even going to try it on a machine. I have no reason to think it wouldn't brick my machine, and I don't have the time to do recovery.
Same here as well. Yet, I was able to successfully install. Now going to do the same on VMWare workstation and see what happens.

Looking over the notes, I think it's probably the parallel tools issue. I can't find any way to completely remove parallels tools from a Catalina VM. Doesn't seem to exist anywhere. Any ideas?
 
I got the Big Sur running with an external bootable drive. The screen defaults to low res and it is slow. I tried to install the parallels tools, and it showed as successful installation, but when I restart the VM, it is still inferred as not installed. My report ID is 343177820
Were you able to resolve this issue? I am stuck at the same point...thanks
 
I see the same behaviour. I saw reports that it is required to have to have an account that uses an AppleID that is registered as a developer on the device. Sounds weird, and of course I can not create any account if I can not log in...
I was able to get past this, but NOT setting up iCloud (skip) and just create a local account. This got me past the login screen, but now I'm having the issue that the "Parallels Tools" install doesn't actually install it (or is not activated for some reason)...
 
Back
Top