dblop.blogg.se - Busy timeout booting macos virtualbox

#BUSY TIMEOUT BOOTING MACOS VIRTUALBOX INSTALL#
#BUSY TIMEOUT BOOTING MACOS VIRTUALBOX FULL#
#BUSY TIMEOUT BOOTING MACOS VIRTUALBOX CODE#
#BUSY TIMEOUT BOOTING MACOS VIRTUALBOX ISO#
#BUSY TIMEOUT BOOTING MACOS VIRTUALBOX DOWNLOAD#

This will pass through all of the features that your CPU supports. 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 Ensure the args are all on a single line! 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Ī USB keyboard is added here because macOS doesn’t support QEMU’s default PS/2 keyboard. First, SSH into your Proxmox server so we can make some edits to the configuration files.Įdit /etc/pve/qemu-server/nf (e.g. In the Hardware page for the VM, add a second DVD drive at IDE0, set it to use your Monterey-full.img.ĭon’t try to start the VM just yet. In the Options page for the VM, ensure that “use tablet for pointer” is set to “Yes”.

Choose VMWare vmxnet3 for the network model.

Set the number of cores for the VM, use a power of two (e.g.

Set the size of the hard disk (64GB or greater, 32GB is too small).

On Proxmox 7 you must untick “pre-enroll keys”

Set graphics to “VMWare Compatible”, set BIOS to OVMF (UEFI), set Machine to Q35, tick QEMU Agent, tick Add EFI Disk and pick storage for it.

#BUSY TIMEOUT BOOTING MACOS VIRTUALBOX ISO#

Select the OpenCore ISO you uploaded and set OS type to “Other”.

Make a note of it.Įvery Mac uses the same OSK, so don’t be surprised that it doesn’t look like a random string! Create the VMįrom the Proxmox web UI, create a new virtual machine as shown below. It’ll print out the 64 character OSK for you. Gcc -o smc_read smc_read.c -framework IOKit In a command prompt, change into the same directory as that file and run: xcode-select -install # If you don't already have gcc

#BUSY TIMEOUT BOOTING MACOS VIRTUALBOX CODE#

Save the first block of C code from this page as smc_read.c. You can get around this by reading an authentication key out of your real Mac hardware (the OSK key).

MacOS checks that it is running on real Mac hardware, and refuses to boot on third-party hardware. iso file extension, this is actually a hard disk image. Prepare an OpenCore imageĭownload the file from the newest release in my repository (you need v13 or newer), double click it to unpack it, and upload it to Proxmox’s ISO store at /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. Upload this file to your Proxmox’s ISO store directory (typically /var/lib/vz/template/iso). This will build a Monterey-full.img file in the scripts/monterey directory for you. Now from the root of OSX-KVM, run: cd scripts/monterey

#BUSY TIMEOUT BOOTING MACOS VIRTUALBOX INSTALL#

Open up the Terminal and run this command to install the commandline tools: xcode-select -install

#BUSY TIMEOUT BOOTING MACOS VIRTUALBOX DOWNLOAD#

Just exit out of the install wizard when it says “to set up the installation of macOS 12 Beta, click Continue” and you should be left with “Install macOS 12 Beta” in your Applications folder.ĭownload my copy of the OSX-KVM repository using the download button, and unzip it: Since Monterey is still in closed Developer Beta, you need to opt-in to the Apple beta program and grab Monterey from System Update. Modern AMD CPUs also support SSE 4.2 and will work with this guide. Older CPUs will cause Illegal Instruction crashes when apps/extensions attempt to use these missing instructions. 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. Since Monterey is still in closed Developer Beta, you need to be an Apple Developer and have access to a Mac (or Mac VM) to download it.

#BUSY TIMEOUT BOOTING MACOS VIRTUALBOX FULL#

You can get the full sourcecode of my OpenCore release on my GitHub here. This tutorial for installing macOS Monterey Developer Beta has been adapted for Proxmox from Kholia’s OSX-KVM project and Leoyzen’s OpenCore configuration for KVM. With the public release of Monterey, this guide is now obsolete, please use my new installation guide instead Magic Trackpad 2 causes kernel heap corruption when passed to a Proxmox guest, GPFs.Installing macOS 12 “Monterey” Developer Beta on Proxmox 6.Recovering lost GPG public keys from your YubiKey.Installing macOS 12 “Monterey” on Proxmox 7.Expanding the disk of your Proxmox macOS VM.Driving a 4-pin computer PWM fan on the BTT Octopus using Klipper.Installing macOS 13 Ventura Developer Beta on Proxmox 7.2.