Stclairsoft go648/11/2023 ![]() I used to check and see what will and won't work. The big change from high sierra to big sur is that you'll lose any 32-bit programs. If you want to be even extra safe, you can use carbon copy cloner ( and make a full backup of your entire drive to another disk (and as long as Fusion isn't running, and the virtual machine is shut down (not suspended), it works for backing VM's up too. Other than the virtual machine, if you have a time machine backup, you can recover everything if it goes wrong. I do recommend shutting down, remove any external devices, and booting clean before doing it just to be extra safe. ![]() The apple upgrades generally go just fine. If you find that the permissions do not match 'drwxrwxrwt', issue the following command when logged in as an administrative user to fix them: sudo chmod 1777 /private/var/tmp The output should look something like this (date and time don't matter).: % ls -ald /private/var/tmpĭrwxrwxrwt 4 root wheel 128 Oct 30 12:40 /private/var/tmp (If you're into cut and paste, just use the first line, and don't include the %). Use the command line in the following example below in the Terminal app to make this check. After the macOS upgrade is a good time to check that this hasn't happened to you. ![]() There have been reports in this forum of something behind the scenes changing default permissions on this directory, which results in Fusion refusing to start virtual machines. Then after upgrading macOS, check permissions on the directory /private/var/tmp. Before upgrading macOS from High Sierra, to Big Sur (or later) I would manually uninstall any existing Fusion version using the instructions found in This will not touch any of your virtual machines.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |