Proxmox screen with "start boot option" message when I start a VM

[bugs]

Hello,

I have a Promox working fine with zfs on a iMac. I have a few VM but when I want to install osx-proxmox (https://github.com/luchina-gabriel/OSX-PROXMOX) I can install os x but when I start the vm I get the proxmox screen with 75% of the progress bar and the message "start boot option" below. But it fails to go further.

Something like this



Could you help me ?

Kind regards.

 

[noel.]

I would recommend using Nick Sherlock's blog [1] for setting up a Hackintosh VM. His tutorials are excellent and tell you step-by-step what to do and why.

---

[1]: https://www.nicksherlock.com/2022/10/installing-macos-13-ventura-on-proxmox/

 

[bugs]

Hello Noel,

Thank you for your feedback. I know the nicksherlock website (excellent indeed) and I allready checked his recommanded script to avoid the bootloop but without success. This is why I asked the question here.

Kind regards.

 

[bugs]

I still got this screen.

Any help ?

 

[noel.]

How long have you let it sit on the boot screen?

Is your system up-to-date? please update with apt dist-upgrade and post the output of pveversion -v. (We also released PVE 8 today, please update, here is the wiki on how to do that).

Otherwise: after starting the machine, check the journal files to see if it gives anything interesting: journalctl -r

Also, maybe try with a different .iso or version of MacOS, just to see if you can get them to boot

 

[Porencephaly13]

Did you ever figure this out? I'm having the same problem

 

[LnxBil]

I'm having the same problem

Are you on AMD?

 

[Porencephaly13]

Are you on AMD?

Yes

 

[LnxBil]

Yes

I thought so. Those errors are common, afaik. Please see some hackintosh-forum for amd related problems. MacOS will best be used on an Intel CPU, more precicely an intel CPU that has actual MacOS support. Getting things working with AMD will work sometimes, but often it's a hell of mountain to climb. Best advise is to switch to (near-)identical hardware to a real mac and enjoy the easy setup. I tried it multiple times and it just works.

 

[Porencephaly13]

I thought so. Those errors are common, afaik. Please see some hackintosh-forum for amd related problems. MacOS will best be used on an Intel CPU, more precicely an intel CPU that has actual MacOS support. Getting things working with AMD will work sometimes, but often it's a hell of mountain to climb. Best advise is to switch to (near-)identical hardware to a real mac and enjoy the easy setup. I tried it multiple times and it just works.

Sorry I got confused. I do have an intel CPU. Specifically, I have 2 Intel Xeon E5-2670

 

[wfeii1980]

I'm having the same problem，Does anyone know the reason? CPU??

PVE Version: 8.1.4
My CPU: Intel(R) Pentium(R) Silver N6005 @ 2.00GHz

# Hackintosh VM - Big Sur
agent: 1
args: -device isa-applesmc,osk="ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc" -smbios type=2 -device usb-kbd,bus=ehci.0,port=2 -device usb-mouse,bus=ehci.0,port=3 -cpu host,kvm=on,vendor=GenuineIntel,+kvm_pv_unhalt,+kvm_pv_eoi,+hypervisor,+invtsc -global ICH9-LPC.acpi-pci-hotplug-with-bridge-support=off
autostart: 0
balloon: 0
bios: ovmf
boot: order=ide0;virtio0
cores: 4
efidisk0: local-lvm:vm-102-disk-0,size=4M
ide0: local:iso/opencore-osx-proxmox-vm.iso,cache=unsafe,size=80M
ide2: local:iso/recovery-bigsur.iso,cache=unsafe,size=800M
machine: q35
memory: 8192
meta: creation-qemu=8.1.2,ctime=1706330489
name: HACK-BIG-SUR
net0: vmxnet3=BC:24:11:49:B6:BB,bridge=vmbr0
numa: 0
onboot: 0
ostype: other
scsihw: virtio-scsi-pci
smbios1: uuid=...
sockets: 1
tablet: 1
vga: vmware
virtio0: local-lvm:vm-102-disk-1,cache=none,discard=on,size=100G
vmgenid: ...

# journalctl -r
Jan 27 13:55:22 pve login[3924]: ROOT LOGIN  on '/dev/pts/0'
Jan 27 13:55:22 pve systemd[1]: Started session-11.scope - Session 11 of User root.
Jan 27 13:55:22 pve systemd-logind[604]: New session 11 of user root.
Jan 27 13:55:22 pve login[3919]: pam_unix(login:session): session opened for user root(uid=0)>
Jan 27 13:55:22 pve pvedaemon[1031]: <root@pam> successful auth for user 'root@pam'
Jan 27 13:55:22 pve pvedaemon[1030]: <root@pam> starting task UPID:pve:00000F4C:0001C2A4:65B4>
Jan 27 13:55:22 pve pvedaemon[3916]: starting termproxy UPID:pve:00000F4C:0001C2A4:65B49ACA:v>
Jan 27 13:55:22 pve pvedaemon[1032]: <root@pam> end task UPID:pve:00000F47:0001BFCC:65B49AC2:>
Jan 27 13:55:14 pve pvedaemon[1032]: <root@pam> starting task UPID:pve:00000F47:0001BFCC:65B4>
Jan 27 13:55:14 pve pvedaemon[3911]: starting vnc proxy UPID:pve:00000F47:0001BFCC:65B49AC2:v>
Jan 27 13:55:14 pve pvedaemon[1030]: <root@pam> end task UPID:pve:00000F18:0001BF50:65B49AC1:>
Jan 27 13:55:14 pve kernel: vmbr0: port 2(tap102i0) entered forwarding state
Jan 27 13:55:14 pve kernel: vmbr0: port 2(tap102i0) entered blocking state
Jan 27 13:55:14 pve kernel: tap102i0: entered allmulticast mode
Jan 27 13:55:14 pve kernel: vmbr0: port 2(tap102i0) entered disabled state
Jan 27 13:55:14 pve kernel: vmbr0: port 2(tap102i0) entered blocking state
Jan 27 13:55:14 pve kernel: tap102i0: entered promiscuous mode
Jan 27 13:55:13 pve systemd[1]: Started 102.scope.
Jan 27 13:55:13 pve pvedaemon[3864]: start VM 102: UPID:pve:00000F18:0001BF50:65B49AC1:qmstar>
Jan 27 13:55:13 pve pvedaemon[1030]: <root@pam> starting task UPID:pve:00000F18:0001BF50:65B4>
Jan 27 13:55:12 pve pvedaemon[1031]: <root@pam> end task UPID:pve:00000E00:000196AD:65B49A59:>
Jan 27 13:55:12 pve systemd-logind[604]: Removed session 8.
Jan 27 13:55:12 pve systemd-logind[604]: Session 8 logged out. Waiting for processes to exit.
Jan 27 13:55:12 pve systemd[1]: session-8.scope: Deactivated successfully.