I have tried following the guide several times but I always get the same error. Everyt

Hi team, I have the same issue with a Ryzen 5600G. <p dir="auto"

I again tried removing macinabox/users and wiping all data macinabox-data in:<br

Can't install Monterey,about spaceinvaderone/macinabox

Comments (34)

rutj87 commented on July 25, 2024 1

Hi team,

I have the same issue with a Ryzen 5600G.

I can get BigSur to install and run with no issues but when I try Monterey, I get boot loop issue at apple logo and can't evwen get in to Monterey installer.

Any help/assistance would be greatly appreciated. No issues following the steps for BigSur and previous versions but for some reason Monterey doesn't play nicely.

Thanks in adance.

from macinabox.

Core-i99 commented on July 25, 2024

Booting from basesystem is correct.

Can you share the vm xml and full specs of the machine?

from macinabox.

Cliff-R-K commented on July 25, 2024

The only way I can get it to boot is to leave the cores at default.
I am running unrid on a sytem with a Ryzen 5600G CPU (Waiting to get my 3900X back from RMA) and 64GB RAM

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' id='35' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
  <name>Macinabox Monterey</name>
  <uuid>159aa42b-0787-4399-b05f-a8b58b1169e0</uuid>
  <description>MacOS Monterey</description>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 10" icon="Monterey.png" os="osx"/>
  </metadata>
  <memory unit='KiB'>4194304</memory>
  <currentMemory unit='KiB'>4194304</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>2</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
    <vcpupin vcpu='1' cpuset='1'/>
  </cputune>
  <resource>
    <partition>/machine</partition>
  </resource>
  <os>
    <type arch='x86_64' machine='pc-q35-4.2'>hvm</type>
    <loader readonly='yes' type='pflash'>/mnt/user/system/custom_ovmf/Macinabox_CODE-pure-efi.fd</loader>
    <nvram>/mnt/user/system/custom_ovmf/Macinabox_VARS-pure-efi.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough' check='none' migratable='on'>
    <topology sockets='1' dies='1' cores='2' threads='1'/>
  </cpu>
  <clock offset='utc'>
    <timer name='rtc' tickpolicy='catchup'/>
    <timer name='pit' tickpolicy='delay'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/local/sbin/qemu</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/domains/Macinabox Monterey/Monterey-opencore.img' index='3'/>
      <backingStore/>
      <target dev='hdc' bus='sata'/>
      <boot order='1'/>
      <alias name='sata0-0-2'/>
      <address type='drive' controller='0' bus='0' target='0' unit='2'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/isos/Monterey-install.img' index='2'/>
      <backingStore/>
      <target dev='hdd' bus='sata'/>
      <alias name='sata0-0-3'/>
      <address type='drive' controller='0' bus='0' target='0' unit='3'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/domains/Macinabox Monterey/macos_disk.img' index='1'/>
      <backingStore/>
      <target dev='hde' bus='virtio'/>
      <alias name='virtio-disk4'/>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </disk>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <alias name='usb'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <alias name='usb'/>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci2'>
      <alias name='usb'/>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <alias name='usb'/>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </controller>
    <controller type='sata' index='0'>
      <alias name='ide'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pcie-root'>
      <alias name='pcie.0'/>
    </controller>
    <controller type='pci' index='1' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='1' port='0x10'/>
      <alias name='pci.1'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/>
    </controller>
    <controller type='pci' index='2' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='2' port='0x11'/>
      <alias name='pci.2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/>
    </controller>
    <controller type='pci' index='3' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='3' port='0x12'/>
      <alias name='pci.3'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/>
    </controller>
    <controller type='pci' index='4' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='4' port='0x13'/>
      <alias name='pci.4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <alias name='virtio-serial0'/>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:56:b8:12'/>
      <source bridge='br0'/>
      <target dev='vnet29'/>
      <model type='virtio'/>
      <alias name='net0'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>
    <serial type='pty'>
      <source path='/dev/pts/7'/>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
      <alias name='serial0'/>
    </serial>
    <console type='pty' tty='/dev/pts/7'>
      <source path='/dev/pts/7'/>
      <target type='serial' port='0'/>
      <alias name='serial0'/>
    </console>
    <channel type='unix'>
      <source mode='bind' path='/var/lib/libvirt/qemu/channel/target/domain-35-Macinabox Monterey/org.qemu.guest_agent.0'/>
      <target type='virtio' name='org.qemu.guest_agent.0' state='disconnected'/>
      <alias name='channel0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <alias name='input0'/>
      <address type='usb' bus='0' port='1'/>
    </input>
    <input type='mouse' bus='ps2'>
      <alias name='input1'/>
    </input>
    <input type='keyboard' bus='ps2'>
      <alias name='input2'/>
    </input>
    <graphics type='vnc' port='5901' autoport='yes' websocket='5701' listen='0.0.0.0' keymap='en-us'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <audio id='1' type='none'/>
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <alias name='video0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>
    <memballoon model='none'/>
  </devices>
  <seclabel type='dynamic' model='dac' relabel='yes'>
    <label>+0:+100</label>
    <imagelabel>+0:+100</imagelabel>
  </seclabel>
  <qemu:commandline>
    <qemu:arg value='-usb'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='usb-kbd,bus=usb-bus.0'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='isa-applesmc,osk=ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc'/>
    <qemu:arg value='-smbios'/>
    <qemu:arg value='type=2'/>
    <qemu:arg value='-cpu'/>
    <qemu:arg value='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,+rdrand,check'/>
  </qemu:commandline>
</domain>

from macinabox.

Core-i99 commented on July 25, 2024

The only way I can get it to boot is to leave the cores at default.

That's normal. Macos in a vm only supports core counts that are a factor of 2.

You can use multiple sockets if you want something like 6 cores.
How many cores do you want for the vm?

And don't edit the vm with unraid built-in vm tab. This will mess up the xml

from macinabox.

Cliff-R-K commented on July 25, 2024

Ok, I would like to use 4 cores. But my main problem is that I can't install. Or is that connected to the low amount of cores? Also the download of the image which I am guessing is happening during the running of userscripts is completed in like one second which I nalso guess is not normal?

from macinabox.

Core-i99 commented on July 25, 2024

Ok, I would like to use 4 cores. But my main problem is that I can't install. Or is that connected to the low amount of cores?

Yes it is.

from macinabox.

Cliff-R-K commented on July 25, 2024

Ok I tried editing the VM using xml-view and added some more cores but even after I click on update it does not save the new settings.
But I still don't understand if you think that the userscripts completing directly is not an problem. As I understand it should download a file that is ~650MB and it can't possible have done that in one second ?

from macinabox.

Core-i99 commented on July 25, 2024

Ok I tried editing the VM using xml-view and added some more cores but even after I click on update it does not save the new settings.
But I still don't understand if you think that the userscripts completing directly is not an problem. As I understand it should download a file that is ~650MB and it can't possible have done that in one second ?

The docker container downloads the macos installer, not the user script.

Edit the xml with virt manager.

from macinabox.

Cliff-R-K commented on July 25, 2024

I again tried removing macinabox/userscripts and wiping all data macinabox-data in:
/mnt/system/custom _ovmf
/mnt/user/macinabox
/mnt/domains/
/mnt/isos/

Redownloaded macinabox and waited for install to complete.
I the runned 1_macinabox_vmready_notify
then 1_macinabox_helper
Editing the Mac monterey vm changing cores to 4 and their corresponing hyperthreads and changed ram to 16GB
Edited 1_macinabox_helper added my vm name.
Runned the 1_macinabox_helper script again to make it fix the xml.

started the vm, selected the first base hd option. Apple logo and progressbar appears. After a couple of seconds the vm reboots back to the first screen again, and if I rerun I get the same result.

the log from the VM:

-device virtio-blk-pci,bus=pci.3,addr=0x0,drive=libvirt-1-format,id=virtio-disk4,write-cache=on \
-netdev tap,fd=41,id=hostnet0,vhost=on,vhostfd=42 \
-device virtio-net-pci,netdev=hostnet0,id=net0,mac=52:54:00:b1:df:52,bus=pci.1,addr=0x0 \
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-chardev socket,id=charchannel0,fd=43,server=on,wait=off \
-device virtserialport,bus=virtio-serial0.0,nr=1,chardev=charchannel0,id=channel0,name=org.qemu.guest_agent.0 \
-device usb-tablet,id=input0,bus=usb.0,port=1 \
-audiodev id=audio1,driver=none \
-vnc 0.0.0.0:1,websocket=5701,audiodev=audio1 \
-k en-us \
-device qxl-vga,id=video0,ram_size=67108864,vram_size=67108864,vram64_size_mb=0,vgamem_mb=16,max_outputs=1,bus=pcie.0,addr=0x1 \
-device virtio-balloon-pci,id=balloon0,bus=pci.4,addr=0x0 \
-usb \
-device usb-kbd,bus=usb-bus.0 \
-device 'isa-applesmc,osk=ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc' \
-smbios type=2 \
-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,+rdrand,check \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
char device redirected to /dev/pts/9 (label charserial0)
2022-02-26T07:14:28.787573Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
2022-02-26T07:14:28.787602Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16]
2022-02-26T07:14:28.788862Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
2022-02-26T07:14:28.788871Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16]
2022-02-26T07:14:28.790049Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
2022-02-26T07:14:28.790060Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16]
2022-02-26T07:14:28.791042Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
2022-02-26T07:14:28.791052Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16]
2022-02-26T07:14:28.792053Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
2022-02-26T07:14:28.792062Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16]
2022-02-26T07:14:28.793064Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
2022-02-26T07:14:28.793072Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16]
2022-02-26T07:14:28.794221Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
2022-02-26T07:14:28.794230Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16]
2022-02-26T07:14:28.795527Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
2022-02-26T07:14:28.795536Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.80000001H:ECX.fma4 [bit 16]
qxl_send_events: spice-server bug: guest stopped, ignoring
2022-02-26T07:14:57.377089Z qemu-system-x86_64: terminating on signal 15 from pid 4983 (/usr/sbin/libvirtd)
2022-02-26 07:14:57.617+0000: shutting down, reason=shutdown

from macinabox.

Core-i99 commented on July 25, 2024

Share the config with those 4 cores.

from macinabox.

Cliff-R-K commented on July 25, 2024

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
  <name>Macinabox Monterey</name>
  <uuid>e5751bac-c65f-419f-ae5f-79dc5b8764e3</uuid>
  <description>MacOS Monterey</description>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 10" icon="default.png" os="osx"/>
  </metadata>
  <memory unit='KiB'>17301504</memory>
  <currentMemory unit='KiB'>17301504</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>8</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='1'/>
    <vcpupin vcpu='1' cpuset='7'/>
    <vcpupin vcpu='2' cpuset='3'/>
    <vcpupin vcpu='3' cpuset='9'/>
    <vcpupin vcpu='4' cpuset='4'/>
    <vcpupin vcpu='5' cpuset='10'/>
    <vcpupin vcpu='6' cpuset='5'/>
    <vcpupin vcpu='7' cpuset='11'/>
  </cputune>
  <os>
    <type arch='x86_64' machine='pc-q35-4.2'>hvm</type>
    <loader readonly='yes' type='pflash'>/mnt/user/system/custom_ovmf/Macinabox_CODE-pure-efi.fd</loader>
    <nvram>/etc/libvirt/qemu/nvram/e5751bac-c65f-419f-ae5f-79dc5b8764e3_VARS-pure-efi.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough' check='none' migratable='on'>
    <topology sockets='1' dies='1' cores='4' threads='2'/>
    <cache mode='passthrough'/>
    <feature policy='require' name='topoext'/>
  </cpu>
  <clock offset='utc'>
    <timer name='rtc' tickpolicy='catchup'/>
    <timer name='pit' tickpolicy='delay'/>
    <timer name='hpet' present='no'/>
  </clock>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>restart</on_crash>
  <devices>
    <emulator>/usr/local/sbin/qemu</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/domains/Macinabox Monterey/Monterey-opencore.img'/>
      <target dev='hdc' bus='sata'/>
      <boot order='1'/>
      <address type='drive' controller='0' bus='0' target='0' unit='2'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/isos/Monterey-install.img'/>
      <target dev='hdd' bus='sata'/>
      <address type='drive' controller='0' bus='0' target='0' unit='3'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='writeback'/>
      <source file='/mnt/user/domains/Macinabox Monterey/macos_disk.img'/>
      <target dev='hde' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </disk>
    <controller type='sata' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pcie-root'/>
    <controller type='pci' index='1' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='1' port='0x10'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0' multifunction='on'/>
    </controller>
    <controller type='pci' index='2' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='2' port='0x11'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/>
    </controller>
    <controller type='pci' index='3' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='3' port='0x12'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/>
    </controller>
    <controller type='pci' index='4' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='4' port='0x13'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
    </controller>
    <controller type='usb' index='0' model='ich9-ehci1'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x7'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci1'>
      <master startport='0'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0' multifunction='on'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci2'>
      <master startport='2'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x1'/>
    </controller>
    <controller type='usb' index='0' model='ich9-uhci3'>
      <master startport='4'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:b1:df:52'/>
      <source bridge='br0'/>
      <model type='virtio'/>
      <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/>
    </interface>
    <serial type='pty'>
      <target type='isa-serial' port='0'>
        <model name='isa-serial'/>
      </target>
    </serial>
    <console type='pty'>
      <target type='serial' port='0'/>
    </console>
    <channel type='unix'>
      <target type='virtio' name='org.qemu.guest_agent.0'/>
      <address type='virtio-serial' controller='0' bus='0' port='1'/>
    </channel>
    <input type='tablet' bus='usb'>
      <address type='usb' bus='0' port='1'/>
    </input>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes' websocket='-1' listen='0.0.0.0' keymap='en-us'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <audio id='1' type='none'/>
    <video>
      <model type='qxl' ram='65536' vram='65536' vgamem='16384' heads='1' primary='yes'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
    </memballoon>
  </devices>
  <qemu:commandline>
    <qemu:arg value='-usb'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='usb-kbd,bus=usb-bus.0'/>
    <qemu:arg value='-device'/>
    <qemu:arg value='isa-applesmc,osk=ourhardworkbythesewordsguardedpleasedontsteal(c)AppleComputerInc'/>
    <qemu:arg value='-smbios'/>
    <qemu:arg value='type=2'/>
    <qemu:arg value='-cpu'/>
    <qemu:arg value='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,+rdrand,check'/>
  </qemu:commandline>
</domain>

from macinabox.

Core-i99 commented on July 25, 2024

  <cpu mode='host-passthrough' check='none' migratable='on'>
    <topology sockets='1' dies='1' cores='4' threads='2'/>
    <cache mode='passthrough'/>
    <feature policy='require' name='topoext'/>
  </cpu>

try this instead;

<cpu mode='host-passthrough' check='none'>
   <topology sockets='1' cores='8' threads='1'/>
</cpu>

I'm currently unsure why it doesn't boot. 8 cores should work fine.

You might also want to enable verbose mode in OpenCore. To give a bit more logging.

from macinabox.

Cliff-R-K commented on July 25, 2024

Ok, will try. Just to clarify, it does boot and the installation starts when I click on the "base-hd icon" but aborts after a few seconds

from macinabox.

Cliff-R-K commented on July 25, 2024

Ok, I just tried editing the xml with the new options. Same result. VM starts and when I click the first icon apple logo/progressbar appears then after a few seconds reboots back to the same screen. Is it because I have a Ryzen CPU ? or should it work anyways ?

from macinabox.

Core-i99 commented on July 25, 2024

Ok, I just tried editing the xml with the new options. Same result. VM starts and when I click the first icon apple logo/progressbar appears then after a few seconds reboots back to the same screen. Is it because I have a Ryzen CPU ? or should it work anyways ?

Cpu is emulated to Penryn.

Try with 2 cores again and see if about this mac says core 2 duo. Just to confirm Penryn emulation works.

If it doesn't then you'll need host passtrough.

from macinabox.

Cliff-R-K commented on July 25, 2024

Ok, tried with two cores, and it did not make any difference. But what do you mean by "about this mac" ? I havent seen anything like that anywhere.

from macinabox.

Core-i99 commented on July 25, 2024

You have said before that leaving the default cores works.

But the default is 2 cores!

And now it doesn't work wirh 2 cores. What nonsense is this???

from macinabox.

Cliff-R-K commented on July 25, 2024

At first I did not understand that editing the vm template screws up the xml and the vm would not boot after that. I then realized that you where supposed to add the vm-name to the 1_macinabox_helper -script so that it fixes the vm template.
Now no matter what I do the vm boots and I get the three options where I can select "macOS base"

But it always just display apple logo and progressbar for a few seconds and then reboots back to the first menu with the three options again. Changing cores/RAM does not make any changes here as it always reboots after a few seconds.

from macinabox.

Core-i99 commented on July 25, 2024

Do not do any edits with the unraid gui. only use virt manager. the macinabox will not fix certain things the unraid gui editor removes.

from macinabox.

indecline commented on July 25, 2024

Had the same issue. Fixed it as below...

Update the cores on the VM through unRAID gui.
Put the VM name into the macinabox helper script under user scripts
Run the user script to fix the VM XML.

from macinabox.

jclendineng commented on July 25, 2024

Same issue here with Monterey and Ryzen

from macinabox.

rutj87 commented on July 25, 2024

Glad I’m not the only one @jclendineng

Anybody got an suggestions to help solve issues for @jclendineng and I with Monterey and Ryzen??

from macinabox.

levelel commented on July 25, 2024

I am with Asus B560 + i5 10400, following the above, using 8-vCPUs, 8G RAM, and having the same issue. So I guess it's not limited to AMD CPUs.

from macinabox.

xrh0905 commented on July 25, 2024

Same issue here.
Monterey boot loop, and stuck with 0%.
Asus motherboard with Ryzen.

from macinabox.

ex1tium commented on July 25, 2024

Same problem with Monterey. I can boot fine and start install. It will load 20% of progress bar and reboot. Doesn't matter what combination of cores or RAM I give it, 2, 4, 8.

I'm currently installing Big Sur which seems to work. It's about 50% done. 18 minutes remaining. I did exactly the same procedures for both OS versions with default config after running user scripts.

Gigabyte z370 Aorus Gaming 7, i7-8700K. Unraid 6.11.5.

//edit Tried upgrading from Big Sur to Ventura and it fails in the same spot when trying to resume upgrade process after booting. Loads a bit then VM reboots.

from macinabox.

benjaminfphillips commented on July 25, 2024

Just an update on this -- I had installed Ventura on my unraid install when my server was running on X99 hardware (5820k intel CPU and MSI X99a SLI plus mobo).

I found a backup on the disk on my array and it boots in fine.. so I do have a working Monterey install. Clearly I was able to install Monterey in the past and it seems like the switch to Ryzen (AMD) has for whatever reason stopped the installer from booting correctly but doesn't stop Monterey boot itself, which is kinda bizzare.

Also, I can boot into "recovery" which works fine.. so it really feels like the fault is with the installer, not opencore or anything else.

Hope this helps.

Edit: Just to confirm, I was able to run through the Monterey Install again by adding a second vdisk and using the recovery boot option to reinstall.

Edit 2: Tried to upgrade to Ventura but get the same issue as Monterey installer. Could be opencore related as I think the OC release we're using is fairly old by now?

from macinabox.

rutj87 commented on July 25, 2024

Just an update on this -- I had installed Ventura on my unraid install when my server was running on X99 hardware (5820k intel CPU and MSI X99a SLI plus mobo).

I found a backup on the disk on my array and it boots in fine.. so I do have a working Monterey install. Clearly I was able to install Monterey in the past and it seems like the switch to Ryzen (AMD) has for whatever reason stopped the installer from booting correctly but doesn't stop Monterey boot itself, which is kinda bizzare.

Also, I can boot into "recovery" which works fine.. so it really feels like the fault is with the installer, not opencore or anything else.

Hope this helps.

Edit: Just to confirm, I was able to run through the Monterey Install again by adding a second vdisk and using the recovery boot option to reinstall.

Edit 2: Tried to upgrade to Ventura but get the same issue as Monterey installer. Could be opencore related as I think the OC release we're using is fairly old by now?

Interesting discovery about the back up, may borrow a mates machine (had intel CPU) to install and take an image and bring across. Keep us posted if you find any other solutions.

from macinabox.

benjaminfphillips commented on July 25, 2024

Just an update on this -- I had installed Ventura on my unraid install when my server was running on X99 hardware (5820k intel CPU and MSI X99a SLI plus mobo).
I found a backup on the disk on my array and it boots in fine.. so I do have a working Monterey install. Clearly I was able to install Monterey in the past and it seems like the switch to Ryzen (AMD) has for whatever reason stopped the installer from booting correctly but doesn't stop Monterey boot itself, which is kinda bizzare.
Also, I can boot into "recovery" which works fine.. so it really feels like the fault is with the installer, not opencore or anything else.
Hope this helps.
Edit: Just to confirm, I was able to run through the Monterey Install again by adding a second vdisk and using the recovery boot option to reinstall.
Edit 2: Tried to upgrade to Ventura but get the same issue as Monterey installer. Could be opencore related as I think the OC release we're using is fairly old by now?

Interesting discovery about the back up, may borrow a mates machine (had intel CPU) to install and take an image and bring across. Keep us posted if you find any other solutions.

Yeah, for sure. Right now, it is unlikely that i'll be looking for any other options, other than maybe trying to get Ventura to work.

All you'd really need (seemingly) would be a working install of Monterey and choose to boot "Recovery" instead of base system and that'll get you through the installer.

Good luck :)

from macinabox.

rutj87 commented on July 25, 2024

Missed the part about the recovery boot option! Are you able to provide a bit more detail about this as I’m not familiar with recovery boot?

…

On Mon, 13 Feb 2023 at 7:45 am, CitizenFour ***@***.***> wrote: Just an update on this -- I had installed Ventura on my unraid install when my server was running on X99 hardware (5820k intel CPU and MSI X99a SLI plus mobo). I found a backup on the disk on my array and it boots in fine.. so I do have a working Monterey install. Clearly I was able to install Monterey in the past and it seems like the switch to Ryzen (AMD) has for whatever reason stopped the installer from booting correctly but doesn't stop Monterey boot itself, which is kinda bizzare. Also, I can boot into "recovery" which works fine.. so it really feels like the fault is with the installer, not opencore or anything else. Hope this helps. Edit: Just to confirm, I was able to run through the Monterey Install again by adding a second vdisk and using the recovery boot option to reinstall. Edit 2: Tried to upgrade to Ventura but get the same issue as Monterey installer. Could be opencore related as I think the OC release we're using is fairly old by now? Interesting discovery about the back up, may borrow a mates machine (had intel CPU) to install and take an image and bring across. Keep us posted if you find any other solutions. Yeah, for sure. Right now, it is unlikely that i'll be looking for any other options, other than maybe trying to get Ventura to work. All you'd really need (seemingly) would be a working install of Monterey and choose to boot "Recovery" instead of base system and that'll get you through the installer. Good luck :) — Reply to this email directly, view it on GitHub <#66 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARVUAIVTAA3R3KWZPJBSBWDWXFDUXANCNFSM5PGLWRFA> . You are receiving this because you commented.Message ID: ***@***.***>

from macinabox.

benjaminfphillips commented on July 25, 2024

Missed the part about the recovery boot option! Are you able to provide a bit more detail about this as I’m not familiar with recovery boot?
…
On Mon, 13 Feb 2023 at 7:45 am, CitizenFour @.> wrote: Just an update on this -- I had installed Ventura on my unraid install when my server was running on X99 hardware (5820k intel CPU and MSI X99a SLI plus mobo). I found a backup on the disk on my array and it boots in fine.. so I do have a working Monterey install. Clearly I was able to install Monterey in the past and it seems like the switch to Ryzen (AMD) has for whatever reason stopped the installer from booting correctly but doesn't stop Monterey boot itself, which is kinda bizzare. Also, I can boot into "recovery" which works fine.. so it really feels like the fault is with the installer, not opencore or anything else. Hope this helps. Edit: Just to confirm, I was able to run through the Monterey Install again by adding a second vdisk and using the recovery boot option to reinstall. Edit 2: Tried to upgrade to Ventura but get the same issue as Monterey installer. Could be opencore related as I think the OC release we're using is fairly old by now? Interesting discovery about the back up, may borrow a mates machine (had intel CPU) to install and take an image and bring across. Keep us posted if you find any other solutions. Yeah, for sure. Right now, it is unlikely that i'll be looking for any other options, other than maybe trying to get Ventura to work. All you'd really need (seemingly) would be a working install of Monterey and choose to boot "Recovery" instead of base system and that'll get you through the installer. Good luck :) — Reply to this email directly, view it on GitHub <#66 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARVUAIVTAA3R3KWZPJBSBWDWXFDUXANCNFSM5PGLWRFA . You are receiving this because you commented.Message ID: @.>

Once you have an install completed it creates a recovery option in the bootloader. You can load that to reinstall MacOS rather than the usual way of loading the base system. That's why you need the image of another person's Monterey install.. just so you have access to the recovery option.

from macinabox.

rutj87 commented on July 25, 2024

Thanks @benjaminfphillips. Following now 👍 and have BigSur up and runing and added a seperate Vdisk.

One remaining question about how you were able to get it to work.... Did you use the recovery option to run the Monterey installer or use the old image you had from previous config? If the first, how did you get it to give option of Monterey Install in Recovery rather than BigSur?

from macinabox.

wiggleforlife commented on July 25, 2024

@rutj87 Did you ever figure out Monterey? I'd like to upgrade my existing Big Sur install for BlueBubbles' new FaceTime feature, but I'd like a success story first. My server runs on a Ryzen 5, so would I have to make a VM on my Intel laptop to get the Monterey recovery OS?

from macinabox.

rutj87 commented on July 25, 2024

No I gave up and bough at Mac Mini 🤣🤣 I’d invested many many many hours and got nowhere. Interestingly, I tried to install it on a mates unraid VM which was running on intel and had the same problem! Have you tried it yet on your Ryzen yet? Would still like to get it working as hate my tech getting the better of me!

…

On Sat, 9 Dec 2023 at 7:29 pm, Cian O ***@***.***> wrote: @rutj87 <https://github.com/rutj87> Did you ever figure out Monterey? I'd like to upgrade my existing Big Sur install for BlueBubbles' new FaceTime feature, but I'd like a success story first. My server runs on a Ryzen 5, so would I have to make a VM on my Intel laptop to get the Monterey recovery OS? — Reply to this email directly, view it on GitHub <#66 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARVUAIQU3WIBDICSEUC4UX3YIQOPNAVCNFSM5PGLWRFKU5DIOJSWCZC7NNSXTN2JONZXKZKDN5WW2ZLOOQ5TCOBUHAZTENJXGQ3Q> . You are receiving this because you were mentioned.Message ID: ***@***.***>

from macinabox.

josley88 commented on July 25, 2024

Any updates on this? I also have this issue on my Ryzen unraid server. I can install Big Sur, but when it's time to upgrade to Monterey or if I try to install Monterey from the start, it restarts the VM.

from macinabox.

Can't install Monterey about macinabox HOT 34 OPEN

Comments (34)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent