Installing macOS 11 “Big Sur” on Proxmox 6 – Nicholas Sherlock (2023)

macOS 12 Monterey is now available! If you want to install that instead, check out my newer guide!

This tutorial for installing macOS Big Sur using OpenCore has been adapted for Proxmox from Kholia’s OSX-KVM project and Leoyzen’s OpenCore configuration for KVM. You can get the full sourcecode on my GitHub here.

Requirements

I’ll assume you already haveProxmox 6installed. You also need a real Mac available in order to fetch the OSK key.

Your Proxmox host computer’s CPU must support SSE 4.2, so for Intel your CPU must be at least as new as Nehalem, which was the first CPU generation to bear the “Core” i5/i7 branding. Older CPUs will cause the finder to repeatedly crash after installation completes (with an Illegal Instruction exception in the graphics code).

Modern AMD CPUs also support SSE 4.2 and will work with this guide.

First step: Create an installation ISO

Download my copy of the OSX-KVM repository using the download button, and unzip it:

https://github.com/thenickdude/OSX-KVM

First we need to install some build requirements. If you will be building the installer ISO on macOS, open up the Terminal and run this command to install the commandline tools:

xcode-select --install

If you’re building the ISO on Linux, you instead need to run this command (these are the package names for Ubuntu or similar distributions, they may need adjustment on other distributions):

sudo apt install qemu-utils make

Now in the Terminal, from the root of OSX-KVM, run:

cd scripts/bigsurmake BigSur-recovery.img

This will download the Big Sur installer from Apple’s software distribution servers and build a BigSur-recovery.img file for you. Upload this file to your Proxmox’s ISO store directory (typically /var/lib/vz/template/iso). Although we’re putting it in the ISO directory so that we can use it with Proxmox’s ISO picker later, this a raw disk image rather than a true ISO.

If you’re building the installer on macOS, you can build a full installer instead of just a recovery, which will mean that macOS won’t have to download Big Sur files during installation, and so won’t require an Internet connection. Simply ask it to build BigSur-full.img instead:

cd scripts/bigsurmake BigSur-full.img

This option is not available when building the installer on Linux.

Prepare an OpenCore image

Download the OpenCore.iso.gz file from the newest release in my repository (that says it’s Big Sur compatible), double click it to unpack it, and upload it to Proxmox’s ISO store at /var/lib/vz/template/iso. Although it has a .iso file extension, this is actually a hard disk image. (You need v12 or newer for Big Sur 11.3 or newer)

Fetch the OSK authentication key

macOS checks that it is running on real Mac hardware, and refuses to boot on third-party hardware. You can get around this by reading anauthentication key out of your real Mac hardware (the OSK key). Save the first block of C code from this page as smc_read.c. In a command prompt, change into the same directory as that file and run:

xcode-select --install # If you don't already have gccgcc -o smc_read smc_read.c -framework IOKit./smc_read

It’ll print out the 64 character OSK for you. Make a note of it.

Every Mac uses the same OSK, so don’t be surprised that it doesn’t look like a random string!

Create the VM

From the Proxmox web UI, create a new virtual machine as shown below.

(Video) How-to: Install MacOS Monterey in Proxmox 7 (Hackintosh)

In the Options page for the VM, ensure that “use tablet for pointer” is set to “Yes”.

In the Hardware page for the VM, add a second DVD drive at IDE0, set it to use your BigSur-full.img or BigSur-recovery.img.

Don’t try to start the VM just yet. First, SSH into your Proxmox server so we can make some edits to the configuration files.

Edit /etc/pve/qemu-server/YOUR-VM-ID-HERE.conf (with nano or vim). Add this line, being sure to substitute the OSK you extracted earlier into the right place:

args: -device isa-applesmc,osk="THE-OSK-YOU-EXTRACTED-GOES-HERE" -smbios type=2 -device usb-kbd,bus=ehci.0,port=2

A USB keyboard is added here because macOS doesn’t support QEMU’s default PS/2 keyboard. Ensure the args are all on a single line!

For Proxmox 7 with QEMU 6.1 or newer, also add “-global ICH9-LPC.acpi-pci-hotplug-with-bridge-support=off”.

We also need to add a -cpu argument. If your host CPU is Intel, add this to the end of the “args” line:

-cpu host,kvm=on,vendor=GenuineIntel,+kvm_pv_unhalt,+kvm_pv_eoi,+hypervisor,+invtsc

This will pass through all of the features that your CPU supports. OpenCore’s config will pretend to macOS that the CPU’s model name is Penryn for compatibility.

If your host CPU is AMD, or the above argument doesn’t work for you, use this more-compatible alternative:

-cpu Penryn,kvm=on,vendor=GenuineIntel,+kvm_pv_unhalt,+kvm_pv_eoi,+hypervisor,+invtsc,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+avx2,+aes,+fma,+fma4,+bmi1,+bmi2,+xsave,+xsaveopt,check

This pretends that your CPU is Penryn, which will keep macOS happy even if your host CPU is AMD, and adds a bunch of newer required and optional CPU features on top. Features that your host CPU doesn’t support will be ignored (a warning will be printed to the console during launch with qm start 1xx), but note that macOS won’t work without SSE4.2 support.

Now find the lines that define the two “ISOs” (ide0 and ide2), and remove the “,media=cdrom” part from them. Add “,cache=unsafe” in its place. This will treat these as hard disks rather than DVD drives.

Save your changes, return to the Options tab, and change the boot order to put IDE2 (the OpenCore image) first. Your final VM configuration file should resemble this:

args: -device isa-applesmc,osk="..." -smbios type=2 -device usb-kbd,bus=ehci.0,port=2 -cpu host,kvm=on,vendor=GenuineIntel,+kvm_pv_unhalt,+kvm_pv_eoi,+hypervisor,+invtscballoon: 0bios: ovmfbootdisk: ide2cores: 4cpu: Penrynefidisk0: vms:vm-100-disk-1,size=1Mide0: isos:iso/BigSur-full.img,cache=unsafe,size=2094688Kide2: isos:iso/OpenCore-v10.img,cache=unsafe,size=150Mmachine: q35memory: 4096name: bigsurnet0: vmxnet3=...,bridge=vmbr0,firewall=1numa: 1ostype: othervirtio0: vms:vm-100-disk-0,cache=unsafe,discard=on,size=64Gscsihw: virtio-scsi-pcismbios1: uuid=...sockets: 1vga: vmware

Configure Proxmox

On Proxmox, run “echo 1 > /sys/module/kvm/parameters/ignore_msrs” to avoid a bootloop during macOS boot. To make this change persist across Proxmox reboots, run:

echo "options kvm ignore_msrs=Y" >> /etc/modprobe.d/kvm.conf && update-initramfs -k all -u

Install Big Sur

Now start up your VM, it should boot to the OpenCore boot picker:

Press enter to boot the “Install macOS Beta” entry and the installer should appear.

Installing macOS 11 “Big Sur” on Proxmox 6 – Nicholas Sherlock (8)

If you built a recovery installer, the icon will instead be an image of a hard disk and be labelled “MacOS Base System”.

Our virtual hard drive needs to be erased/formattedbefore we can install to it, so select the Disk Utility option. Follow the steps below to format the disk:

Now we’re ready to begin installation!

(Video) This Linux PC Runs macOS Faster Than a Real Mac

After the first stage of installation, the VM will reboot 3 or 4 times in quick succession, and each time you must pick the “macOS Installer” entry (the second one here, with the hard disk icon) to continue installation. It will not be selected for you automatically:

Installing macOS 11 “Big Sur” on Proxmox 6 – Nicholas Sherlock (14)

If your keyboard isn’t responding on this screen, exit the Console tab in Proxmox and re-enter it. If you get a “prohibited” sign like this appearing, hit the Reset button on the VM to try again:

Installing macOS 11 “Big Sur” on Proxmox 6 – Nicholas Sherlock (15)

Now the installation is complete and the macOS Installer entry disappears, so pick the name of your main disk to boot (mine’s called Main).

Installing macOS 11 “Big Sur” on Proxmox 6 – Nicholas Sherlock (16)

Answer the initial install questions, and you’ll be logged on! Note that you might want to hold off on logging into your Apple ID until you’ve configured your Mac’s serial number in OpenCore.

Installing macOS 11 “Big Sur” on Proxmox 6 – Nicholas Sherlock (17)

Note that it will be really sluggish for a few minutes after the first boot while the system performs housekeeping tasks.

Make the OpenCore install permanent

We’re currently booting using OpenCore from the attached OpenCore ISO. Let’s install that to the hard drive instead. Pop open Terminal and run “diskutil list” to see what drives we have available.

Installing macOS 11 “Big Sur” on Proxmox 6 – Nicholas Sherlock (18)

Use “sudo dd if=<source> of=<dest>” to copy the “EFI” partition from the OpenCore CD and overwrite the EFI partition on the hard disk. The OpenCore CD is the small disk (~150MB) that only has an EFI partition on it, and the main hard disk is the one with the large (>30GB) Apple_APFS “Container” partition on it.

In my case these EFI partitions ended up being called disk2s1 and disk0s1 respectively, so I ran “sudo dd if=/dev/disk2s1 of=/dev/disk0s1” (note that if you get these names wrong, you will overwrite the wrong disk and you’ll have to start the installation over again!).

Now shut down the VM, and remove both the OpenCore and the Big Sur installer drives from the Hardware tab. On the Options tab, edit the boot order to place your virtio0 disk as the first disk. Boot up. If everything went well, you should see the OpenCore boot menu, and you can select your “Main” disk to boot Big Sur:

Installing macOS 11 “Big Sur” on Proxmox 6 – Nicholas Sherlock (19)

Sleep management

I found that I was unable to wake Big Sur from sleep using my mouse or keyboard. If you encounter the same problem, you can either disable system sleep in Big Sur’s Energy Saver settings to avoid the issue, or you can manually wake the VM up from sleep from Proxmox by running:

qm monitor YOUR-VM-ID-HERE 
system_wakeup
quit

Editing your OpenCore/EFI settings

The Configuration.pdf that explains the OpenCore config.plist file can be found along with the OpenCore release on my GitHub.

To mount your EFI partition in macOS so you can edit your config.plist, first check the “identifier” of your EFI partition in the terminal:

~$ diskutil list/dev/disk0 (external, physical): #: TYPE NAME SIZE IDENTIFIER 0: GUID_partition_scheme *512.1 GB disk0 1: EFI EFI 209.7 MB disk0s1 2: Apple_APFS Container disk1 511.9 GB disk0s2

Then you can mount it like so:

sudo mkdir /Volumes/EFI
sudo mount -t msdos /dev/disk0s1 /Volumes/EFI

Now you can edit /Volumes/EFI/OC/config.plist with your favourite text editor to make your changes. (TextEdit is not a great choice because it likes to insert curly quotes into the file and otherwise break things, there are some dedicated plist editors available such as XCode).

If you’re unable to boot macOS, you can edit the config.plist using the “UEFI Shell” option in the OpenCore boot menu instead.

Enter “FS0:” and press enter to open up the first available filesystem, then run “edit EFI\OC\config.plist” (if the file isn’t found, try switching to another filesystem like fs1:). When you’re done editing, press control+Q to exit, “Y” to save, then run “exit” to return to the OpenCore menu. You need to reboot for your changes to take effect.

If you prefer, you can edit config.plist from the comfort of your Proxmox host instead. If you’re booting from an attached OpenCore.img file, you can mount that file as a disk on the host. If you’re booting from the VM’s disk instead, it must be in raw format in order to be mounted (e.g. typical LVM or ZFS usage) rather than qcow2.

# Mount an OpenCore image:losetup --partscan /dev/loop0 /var/lib/vz/template/iso/OpenCore-v11.img# or a VM boot disk:losetup --partscan /dev/loop0 /dev/zvol/tank/vms/vm-100-disk-1mount /dev/loop0p1 /mnt

Now the contents of that first partition are available in /mnt, so you can edit /mnt/EFI/OC/config.plist in your favourite editor. When you’re done, do this to unmount the disk:

(Video) Part 2 - How-to: finish configuring MacOS Monterey Virtual Machine on Proxmox (Hackintosh)

umount /mnt
losetup --detach /dev/loop0

Automatic boot

In config.plist, you can set Misc/Boot/Timeout to a non-zero value to allow the default boot option be chosen automatically after that delay in seconds. I’ve disabled this by default because it causes the installer ISO to re-enter its main menu instead of continuing the second stage of installation.

You can set the default boot option by pressing control+enter on it.

Verbose boot

To boot macOS in Verbose mode to diagnose boot problems, at the OpenCore boot menu press Cmd+V before pressing enter to boot macOS (you don’t need to hold it down).

If there is a kernel panic during boot and it reboots too quickly to be read, edit config.plist to add “debug=0x100” to the kernel arguments.

Changing screen resolution

To change macOS’ screen resolution, you need to edit the UEFI/Output/Resolution setting in config.plist, the default is 1920×1080@32.

You should be able to change this to any of the modes that the system OVMF menu offers (hit F2 at the start of guest boot and choose “Device Manager/OVMF Platform Configuration” to see which resolutions are available).

Video performance

Because there is no guest video acceleration available for macOS, video performance is poor.

In Google Chrome in the guest you will need to toggle off the setting to “use hardware acceleration when available” to improve issues with elements not being drawn or flickering (especially video). Safari may be a better choice.

macOS’s built in “Screen Sharing” feature offers dramatically better framerates and latency than Proxmox’s browser-based VNC console, so if you have a real Mac to act as a viewing console, you can enable that in the VM’s “Sharing” settings and connect to the VM using the Screen Sharing app from your Mac instead:

Apparently Screen Sharing is also compatible with VNC clients like RealVNC, so you should be able to connect to it from Linux or Windows consoles using RealVNC.

The real magic bullet for video performance is to pass through a compatible video card using PCIe passthrough (though note that Big Sur, like Catalina, does not support most NVidia cards). This offers near-native performance. You can read more about how I’m using PCIe passthrough on my own installation here.

USB passthrough

Since I want to use this as my primary computer, I want to use a USB keyboard and mouse plugged directly into Proxmox, rather than sending my input through the web VNC console.

Proxmox has good documentation for USB passthrough. Basically, run “qm monitor YOUR-VM-ID-HERE”, then “info usbhost” to get a list of the USB devices connected to Proxmox:

qm> info usbhost
Bus 3, Addr 12, Port 6, Speed 480 Mb/s
Class 00: USB device 8564:1000, Mass Storage Device
Bus 3, Addr 11, Port 5.4, Speed 12 Mb/s
Class 00: USB device 04d9:0141, USB Keyboard
Bus 3, Addr 10, Port 5.1.2, Speed 12 Mb/s
Class 00: USB device 046d:c52b, USB Receiver
Bus 3, Addr 9, Port 14.4, Speed 12 Mb/s
Class 00: USB device 046d:c227, G15 GamePanel LCD
Bus 3, Addr 8, Port 14.1, Speed 1.5 Mb/s
Class 00: USB device 046d:c226, G15 Gaming Keyboard

In this case I can add my keyboard and mouse to USB passthrough by quitting qm, then running:

qm set YOUR-VM-ID-HERE -usb1 host=04d9:0141
qm set YOUR-VM-ID-HERE -usb2 host=046d:c52b

This saves the devices to the VM configuration for you. You need to reboot to have the new settingsapply. Note that the emulated USB3 device doesn’t work with macOS, so don’t set “usb3=1”.

You can also pass through USB devices by passing through an entire USB controller using Proxmox’s PCIe passthrough feature, which gives much better compatibility.

FileVault

Installing macOS 11 “Big Sur” on Proxmox 6 – Nicholas Sherlock (21)

FileVault now works with OpenCore, so you can encrypt your boot disk by using the option in macOS’ system security preferences. But be certain to keep a copy of your recovery key and keep your backups up to date.

Fixing “guest boots to UEFI shell”

If your guest ends up booting to the UEFI shell instead of showing the OpenCore boot menu, especially if you’ve just updated OpenCore to a new version, you’ll need to edit the guest’s UEFI boot entries to fix this.

(Video) How to Build a Hackintosh - Step-by-Step Guide (Install MacOS Big Sur on PC)

At the very start of guest boot, hit F2 to enter guest UEFI settings.

First we’ll remove the old entries. Choose the Boot Maintenance option, then Boot Options -> Delete Boot Option. Use the spacebar to tick any old Clover or OpenCore entries (avoid ticking the EFI Internal Shell option, you want to keep that!). Select “Commit Changes and Exit”.

Now we’ll add the correct entry for OpenCore back in. Select Add Boot Option. Navigate through the device tree to EFI/OC/OpenCore.efi (use EFI/BOOT/BOOTx64.efi instead on my “OpenCore v10” and older) and select it, name this new option “OpenCore” or similar. Again Commit Changes and Exit.

Go to the Change Boot Order and move OpenCore to the top. Commit Changes and Exit.

Now back out to the main menu and choose Reset, and you should successfully boot into OpenCore this time.

Fixing iMessage

iCloud and the App Store should already be working for you, but for iMessage support you must follow these steps to mark your network adapter as built-in:

https://dortania.github.io/OpenCore-Post-Install/universal/iservices.html#fixing-en0

Disabling SIP (System Integrity Protection)

You can disable SIP by selecting the Recovery option from the OpenCore boot menu, then use the top menu to open the Terminal and run “csrutil disable”. Then reboot.

This may be needed to run unsigned kexts or perform other hacks.

Upgrading OpenCore

Sometimes you need to update OpenCore to a new release in order to support a new macOS update. I’ll assume you don’t have any customisations to config.plist you want to save.

First take a snapshot! It’s great to be able to roll back if something goes wrong.

If you’re still able to boot macOS, you can update it from within the guest. Follow the instructions in the “Editing your OpenCore/EFI settings” section to mount your EFI partition. Then you can delete the EFI folder in there and replace it with the one from the OpenCoreEFIFolder.zip file from my OpenCore release (you’ll probably need to empty the trash to make room for the new folder). You’re done!

If you aren’t able to boot macOS, unpack and upload the new OpenCore ISO to Proxmox’s ISO store instead. Add a new CD drive to the VM that uses that ISO. Then in Proxmox’s terminal edit the VM’s config (in /etc/pve/qemu-server) to replace “media=cdrom” with “cache=unsafe” for the OpenCore drive. Now on the “Options” tab, change the boot order to put the new OpenCore drive first.

Start the VM and boot into macOS using the new OpenCore drive. From within macOS you can now follow the instructions from the “Make the OpenCore install permanent” section to install the new OpenCore image to your main macOS disk, after which the OpenCore drive can be detached from the VM.

Upgrading from macOS Catalina

First make a backup or snapshot of your system!Being able to roll back when the upgrade goes wrong is a real lifesaver.

You’ll need to update OpenCore to my v10 release before the upgrade. You can follow the instructions in the “Editing your OpenCore settings” section above to mount your EFI disk. Then you can replace the OpenCore files in the mounted “EFI” disk with the ones from the OpenCoreEFIFolder.zip file in my newest OpenCore release.

Reboot to make sure that you can still boot Catalina.

If you’re using any PCIe passthrough devices (particularly video cards) you’ll want to disable those and set “vga: vmware” instead, so you can install using Proxmox’s web console from a different machine during the upgrade. This avoids installer problems triggered by flaky video card passthrough, especially host lockups caused by the AMD Reset Bug.

(Video) Virtualizzare macOS 12 Monterey su Proxmox: Configurazione VM e Installazione - TPS

Now you can upgrade to Big Sur using the App Store like you would on a real Mac.

FAQs

Can I install macOS on proxmox? ›

OSX-PROXMOX - Run macOS on ANY Computer - AMD & Intel

XX - Next, Next & Finish (NNF). Open Proxmox Web Console -> Datacenter > NAME OF YOUR HOST > Shell. Copy, paste and execute (code below). Voilà, install macOS!

How manually install macOS Big Sur? ›

Here's how to run a standard macOS Big Sur installation:
  1. Click on the Apple icon in your menu bar > About This Mac.
  2. In the Overview section, click on Software Update.
  3. Click on Update Now to download the installer.
  4. Follow the installation instructions on your screen.
Nov 18, 2020

Why is macOS Big Sur failing to install? ›

If you're still having problems downloading macOS Big Sur, try to find the partially-downloaded macOS 11 files and a file named 'Install macOS 11' on your hard drive. Delete them, then reboot your Mac and try to download macOS Big Sur again.

Can you run Big Sur on a Hackintosh? ›

Use the program to mount the EFI partitions from both the hard drive on your Hackintosh and the USB drive called "Install MacOS Big Sur". First select one, then the other. After both partitions are mounted, you will need to copy the EFI folder from the USB EFI partition over to the hard drive EFI partition.

Is proxmox ve free? ›

The Proxmox VE source code is free, released under the GNU Affero General Public License, v3 (GNU AGPL, v3). This means that you are free to use the software, inspect the source code at any time and contribute to the project yourself.

What is proxmox used for? ›

Proxmox Virtual Environment (Proxmox VE or PVE) is an open-source software server for virtualization management. It is a hosted Type-2 hypervisor that can run operating systems including Linux and Windows on x64 hardware.

How do I do a clean install of macOS Big Sur? ›

Macintosh HD – Data in Catalina/Big Sur is where your data is stored separately to the macOS installation.
  1. Either click on the – button or go to the menu and choose Edit > Delete APFS volume.
  2. You will see a message warning you that this will permanently erase your data. Click on Delete. ...
  3. Wait while the volume is deleted.
Jan 25, 2022

How do I get macOS Big Sur installer? ›

How to get Big Sur or older installer
  1. Open the Mac App Store.
  2. Go to the Catalina page, you can click this link to Catalina on the Mac App Store.
  3. Now, if you click on Get, your Mac will offer to download the installers.
May 20, 2022

How do you clean install macOS 11? ›

Choose Apple menu > Shut Down, press and hold the power button until “Loading startup options” appears, select Options, click Continue, then follow the onscreen instructions. In the Recovery app window, select Reinstall for your macOS release, click Continue, then follow the onscreen instructions.

How long should macOS Big Sur take to install? ›

The macOS Big Sur 11.6. 8 installation could take around 10 minutes to complete. It took just around that to install the software on a MacBook Pro (2016). Your Mac might reboot itself a couple of times during the installation process, but this is perfectly normal.

Is my Mac too old for Big Sur? ›

As long as your MacBook Pro doesn't predate the late 2013 models you'll be able to run Big Sur. Note that the 2012 model that was the last MacBook Pro to ship with a DVD drive was still sold in 2016, so beware that even if you bought the MacBook Pro after 2013 it might not be compatible with Big Sur.

How long should it take to download macOS Big Sur? ›

The download of macOS Big Sur 11.6. 4 will take about 10 minutes. Your Mac may reboot several times during the process, but once the download completes, the computer should boot normally. After the download has finished, you may be prompted to log into iCloud or sign in to various apps.

Can I install macOS on virtual machine? ›

You can install Mac OS X, OS X, or macOS in a virtual machine. Fusion creates the virtual machine, opens the operating system installation assistant, and installs VMware Tools. VMware Tools loads the drivers required to optimize a virtual machine's performance.

Can you install macOS on a custom built PC? ›

No. Mac OS X can only be install on Apple hardware.

How do I install macOS on a non-Apple computer? ›

How to Install macOS on a PC Using the Installation USB
  1. From the Clover boot screen, select Boot macOS Install from Install macOS Catalina. ...
  2. Select your desired Language, and click the forward arrow.
  3. Select Disk Utility from the macOS Utilities menu.
  4. Click your PC hard drive in the left column.
  5. Click Erase.
Aug 22, 2022

Is Proxmox better than VirtualBox? ›

Comparison Results: Oracle VM VirtualBox and Proxmox VE had a similar user rating regarding ease of deployment, pricing, service and support, and ROI. However, in terms of features, Oracle VM VirtualBox users felt the solution was unstable, whereas Proxmox VE users felt some bugs needed fixing.

How much RAM does Proxmox need? ›

Memory, minimum 2 GB for OS and Proxmox VE services. Plus designated memory for guests. For Ceph or ZFS additional memory is required, approximately 1 GB memory for every TB used storage. Fast and redundant storage, best results with SSD disks.

Can I run Proxmox without subscription? ›

Proxmox VE No-Subscription Repository

You don't need a subscription key to access the pve-no-subscription repository. We recommend to configure this repository in /etc/apt/sources.

Who owns Proxmox? ›

Proxmox, as a company, was founded by Martin Maurer and Dietmar Maurer in 2005. The Proxmox company history started just shortly before the Proxmox Mail Gateway was released for the first time. In 2008 the Proxmox Virtual Environment was released in version 0.9.

Is Proxmox stable? ›

Yes ProxMox is stable, so is HyperV and ESXi but they will all have issues.

Is Proxmox bare metal? ›

Note: Proxmox VE is a bare-metal installer, please be aware that the complete server is used and all existing data will be removed.

Can macOS Big Sur be installed on Macintosh HD? ›

macOS Big Sur can't be installed on Macintosh HD

Before you attempt to install any major update to macOS, you should back up your Mac. If you use Time Machine, you can run a manual backup using that.

How do I get macOS Big Sur on unsupported Mac? ›

NEW 2022! Big Sur on Unsupported Macs [2008-2013 ... - YouTube

Can I still install Mac Big Sur? ›

You can install macOS Big Sur on any of these Mac models. If upgrading from macOS Sierra or later, macOS Big Sur requires 35.5GB of available storage to upgrade. If upgrading from an earlier release, macOS Big Sur requires up to 44.5GB of available storage.

How do I update my Mac to Big Sur? ›

To upgrade to macOS Big Sur:
  1. Back up your Mac using Time Machine.
  2. Open the macOS Big Sur page in the App Store.
  3. Select Get to download the installer.
  4. After the download is complete, the installer opens automatically.
  5. Follow the prompts to install macOS Big Sur.
Nov 17, 2021

Videos

1. How To Install macOS Monterey On Linux - Run macOS On Linux PC
(Hikmat E Ustad)
2. macOS VM: iPhone + Xcode USB! Linux/Windows USB + Xcode Passthrough using Docker-OSX and usbfluxd!
(Sick Codes)
3. Idiot Friendly! AMD/NVIDIA GPU Passthrough in Proxmox Guide
(TechHut)
4. Mac Monterey qemu virtual machine with kholia osx-kvm
(NapoleonWils0n)
5. macOS VM on Linux & Windows using Docker-OSX: How to run mac VMs (Monterey/Big Sur/Catalina)
(Sick Codes)
6. [VFIO Single GPU Passthrough] Comment faire une KVM pour le gaming ?
(Mageas)
Top Articles
Latest Posts
Article information

Author: Manual Maggio

Last Updated: 02/14/2023

Views: 5387

Rating: 4.9 / 5 (49 voted)

Reviews: 80% of readers found this page helpful

Author information

Name: Manual Maggio

Birthday: 1998-01-20

Address: 359 Kelvin Stream, Lake Eldonview, MT 33517-1242

Phone: +577037762465

Job: Product Hospitality Supervisor

Hobby: Gardening, Web surfing, Video gaming, Amateur radio, Flag Football, Reading, Table tennis

Introduction: My name is Manual Maggio, I am a thankful, tender, adventurous, delightful, fantastic, proud, graceful person who loves writing and wants to share my knowledge and understanding with you.