thenickdude / KVM-Opencore

OpenCore disk image for running macOS VMs on Proxmox/QEMU

Home Page:https://www.nicksherlock.com/2021/10/installing-macos-12-monterey-on-proxmox-7/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

install Monterey apple logo appears then reboot

zhonghuang opened this issue · comments

Hi @thenickdude, thank you for your work!
I'm installing Montereyon according to this guide:
Proxmox
proxmox 7.1 and OpenCore-v16.
hardware: X79+E5-2687w+32G
my configuration file:

agent: 1
args: -device isa-applesmc,osk="our..." -smbios type=2 -device usb-kbd,bus=ehci.0,port=2 -global nec-usb-xhci.msi=off -global ICH9-LPC.acpi-pci-hotplug-with-bridge-support=off -cpu host,kvm=on,vendor=GenuineIntel,+kvm_pv_unhalt,+kvm_pv_eoi,+hypervisor,+invtsc
balloon: 0
bios: ovmf
boot: order=ide2
cores: 8
cpu: Penryn
efidisk0: local-lvm:vm-100-disk-1,efitype=4m,size=4M
ide0: local:iso/Monterey-recovery.img,cache=unsafe,size=3143856K
ide2: local:iso/OpenCore-v16.iso,cache=unsafe,size=150M
machine: q35
memory: 16384
meta: creation-qemu=6.1.0,ctime=1654908856
name: macOS-Monterey
net0: virtio=2E:A4:36:DE:80:EE,bridge=vmbr0,firewall=1
numa: 1
ostype: other
scsihw: virtio-scsi-pci
smbios1: uuid=6fe10261-4b2b-49f6-9807-1b7d2ed3be68
sockets: 1
vga: vmware
virtio0: local-lvm:vm-100-disk-0,cache=unsafe,discard=on,size=50G
vmgenid: 6a27f371-bc0d-4d8e-9011-15c2190bc4a8

verbose:

Screen Shot 2022-06-11 at 10 43 28 AM

Screen Shot 2022-06-11 at 10 44 42 AM

Screen Shot 2022-06-11 at 10 45 42 AM

Screen Shot 2022-06-11 at 10 46 16 AM

Screen Shot 2022-06-11 at 10 46 39 AM

Screen Shot 2022-06-11 at 10 47 07 AM

Screen Shot 2022-06-11 at 10 47 34 AM

![Uploading Screen Shot 2022-06-11 at 10.48.01 AM.png…]()

Screen Shot 2022-06-11 at 10 48 48 AM

Thanks!

Your config looks good. Try cores: 4 instead, and let me know your full OSK too just in case (I'll edit it out of the message after reading it).

Also, on Proxmox run:

dmesg | grep -i -e tsc -e clocksource

Look for an error like “TSC found unstable after boot, most likely due to broken BIOS.

It's the broken BIOS. I'll try methods in issue #15.