hello @SpaceInvaderOne,

 

i followed your tutorial step by step, and the system runs good to the step who i shuld delet disk1 and disk2 an copy path from disk 3 to Disk1 then the BigSur doen't boot up Bootscreen failure 

 

the xml:

Spoiler

XML doen't boot up
<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
  <name>Macinabox BigSur</name>
  <uuid>XXXXXXXXX</uuid>
  <description>MacOS Big Sur</description>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 10" icon="BigSur.png" os="osx"/>
  </metadata>
  <memory unit='KiB'>XXXXXXXXX</memory>
  <currentMemory unit='KiB'>XXXXXXXXX</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>20</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='2'/>
    <vcpupin vcpu='1' cpuset='14'/>
    <vcpupin vcpu='2' cpuset='3'/>
    <vcpupin vcpu='3' cpuset='15'/>
    <vcpupin vcpu='4' cpuset='4'/>
    <vcpupin vcpu='5' cpuset='16'/>
    <vcpupin vcpu='6' cpuset='5'/>
    <vcpupin vcpu='7' cpuset='17'/>
    <vcpupin vcpu='8' cpuset='6'/>
    <vcpupin vcpu='9' cpuset='18'/>
    <vcpupin vcpu='10' cpuset='7'/>
    <vcpupin vcpu='11' cpuset='19'/>
    <vcpupin vcpu='12' cpuset='8'/>
    <vcpupin vcpu='13' cpuset='20'/>
    <vcpupin vcpu='14' cpuset='9'/>
    <vcpupin vcpu='15' cpuset='21'/>
    <vcpupin vcpu='16' cpuset='10'/>
    <vcpupin vcpu='17' cpuset='22'/>
    <vcpupin vcpu='18' cpuset='11'/>
    <vcpupin vcpu='19' cpuset='23'/>
  </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>/etc/libvirt/qemu/nvram/780d32bc-3927-43ec-89a6-4862f17c4cfd_VARS-pure-efi.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough' check='none' migratable='on'/>
  <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 BigSur/macos_disk.img'/>
      <target dev='hdc' bus='sata'/>
      <boot order='1'/>
      <address type='drive' controller='0' bus='0' target='0' unit='2'/>
    </disk>
    <controller type='scsi' index='0' model='virtio-scsi'>
      <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='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='0x18'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0' multifunction='on'/>
    </controller>
    <controller type='pci' index='2' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='2' port='0x19'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x1'/>
    </controller>
    <controller type='pci' index='3' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='3' port='0x1a'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x2'/>
    </controller>
    <controller type='pci' index='4' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='4' port='0x1b'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x3'/>
    </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:4b:86:a7'/>
      <source bridge='br0'/>
      <model type='e1000-82545em'/>
      <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>
    <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='0x03' slot='0x00' function='0x0'/>
    </memballoon>
  </devices>
  <seclabel type='dynamic' model='dac' relabel='yes'/>
  <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='************************'/>
    <qemu:arg value='-smbios'/>
    <qemu:arg value='type=2'/>
    <qemu:arg value='-cpu'/>
    <qemu:arg value='Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check'/>
  </qemu:commandline>
</domain>

the Path:Url's tho the img's:

Spoiler

disk1
/mnt/user/isos/BigSur-opencore.img

 

disk2
/mnt/user/isos/BigSur-install.img

 

disk3
/mnt/user/domains/Macinabox BigSur/macos_disk.img
 

after every change i run the script 1

 

only reset to disk settings get a startup result.

 

i Hope you can fix it.

 

best regrads from Vavaria Germany

JZDS

6 hours ago, JZDS said:

    <controller type='scsi' index='0' model='virtio-scsi'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/>
    </controller>

I think virtio-scsi controller is not supported by mac os, delete it, you are not using it.

 

6 hours ago, JZDS said:

  <vcpu placement='static'>20</vcpu>

This is a odd number of cores, apple may not like it.

Either use a proper number of cores (16/18/24), or follow the examples reported here (irregular topology, use 24 and disable 4 cores):

https://github.com/Leoyzen/KVM-Opencore

 

I assume you copied the efi folder to the mac os disk before deleting the opencore disk.

Edited October 16, 20214 yr by ghost82

3 hours ago, ghost82 said:

I assume you copied the efi folder to the mac os disk before deleting the opencore disk.

yes i did. but i think anything gone wron. if i change the series of the disks it doesn't bot up. if i swap back already is good. i have no idea whats gone wrong

Edited October 16, 20214 yr by JZDS

4 hours ago, ghost82 said:

I think virtio-scsi controller is not supported by mac os, delete it, you are not using it.

is fixed its a leftover of testing disk assignments

 

4 hours ago, ghost82 said:

This is a odd number of cores, apple may not like it.

Either use a proper number of cores (16/18/24), or follow the examples reported here (irregular topology, use 24 and disable 4 cores):

fixed used now 8core with 2 threads for 16core

 

is the logfile helpful to fix it?

 

Spoiler

-netdev tap,fd=33,id=hostnet0 \
-device e1000-82545em,netdev=hostnet0,id=net0,mac=52:54:00:0d:ca:78,bus=pci.1,addr=0x0 \
-chardev pty,id=charserial0 \
-device isa-serial,chardev=charserial0,id=serial0 \
-chardev socket,id=charchannel0,fd=35,server,nowait \
-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 \
-vnc 0.0.0.0:0,websocket=5700 \
-k de \
-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.3,addr=0x0 \
-usb \
-device usb-kbd,bus=usb-bus.0 \
-device '************************' \
-smbios type=2 \
-cpu Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check \
-sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny,resourcecontrol=deny \
-msg timestamp=on
2021-10-16 12:15:37.516+0000: Domain id=14 is tainted: high-privileges
2021-10-16 12:15:37.516+0000: Domain id=14 is tainted: custom-argv
2021-10-16 12:15:37.516+0000: Domain id=14 is tainted: host-cpu
char device redirected to /dev/pts/0 (label charserial0)
2021-10-16T12:15:37.554085Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
2021-10-16T12:15:37.554982Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
2021-10-16T12:15:37.555742Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
2021-10-16T12:15:37.556616Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
2021-10-16T12:15:37.557324Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
2021-10-16T12:15:37.558025Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
2021-10-16T12:15:37.558764Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
2021-10-16T12:15:37.559528Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
2021-10-16T12:15:37.560285Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
2021-10-16T12:15:37.561057Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
2021-10-16T12:15:37.561826Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
2021-10-16T12:15:37.562572Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
2021-10-16T12:15:37.563332Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
2021-10-16T12:15:37.564104Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
2021-10-16T12:15:37.564887Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
2021-10-16T12:15:37.565740Z qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.01H:ECX.pcid [bit 17]
2021-10-16T12:17:15.832584Z qemu-system-x86_64: terminating on signal 15 from pid 14029 (/usr/sbin/libvirtd)
2021-10-16 12:17:16.032+0000: shutting down, reason=destroyed

 

no, apart the last two lines indicating that the vm is receiving a shutdown command from libvirt for whatever reason...

When ever I try to install Big Sur, it hangs on the install screen saying 2 hours and 19 mins left. Anyone have ideas on how to fix it?

Hi all, I'm hanging on this screen after doing the install succesfully:

 

 

Steps completed:

• Boot into macOS Big Sur with VNC Remote
• install OpenCore Configurator
• Copy bootloader to main disk
• Check macOS serial number

I then shut down the VM and did these steps:

• Increase CPU cores (8)
• Increase RAM (8192MB)
• Remove install vDisks and use disk 3 for primary disk
• Helper script changes:
  • FirstInstall = no

I've found this resource but I'm unsure how to change these parameters:

 

https://dortania.github.io/OpenCore-Install-Guide/troubleshooting/extended/kernel-issues.html#stuck-on-eb-log-exitbs-start

 

Where do these parameters live? In the config.plist? I don't where to find the config.plist now that I can't login to macOS anymore.

 

XML:

Spoiler

<?xml version='1.0' encoding='UTF-8'?>
<domain type='kvm' xmlns:qemu='http://libvirt.org/schemas/domain/qemu/1.0'>
  <name>Macinabox BigSur</name>
  <description>MacOS Big Sur</description>
  <metadata>
    <vmtemplate xmlns="unraid" name="Windows 10" icon="default.png" os="osx"/>
  </metadata>
  <memory unit='KiB'>8388608</memory>
  <currentMemory unit='KiB'>8388608</currentMemory>
  <memoryBacking>
    <nosharepages/>
  </memoryBacking>
  <vcpu placement='static'>8</vcpu>
  <cputune>
    <vcpupin vcpu='0' cpuset='0'/>
    <vcpupin vcpu='1' cpuset='1'/>
    <vcpupin vcpu='2' cpuset='2'/>
    <vcpupin vcpu='3' cpuset='3'/>
    <vcpupin vcpu='4' cpuset='4'/>
    <vcpupin vcpu='5' cpuset='5'/>
    <vcpupin vcpu='6' cpuset='6'/>
    <vcpupin vcpu='7' cpuset='7'/>
  </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/7c979414-6956-470a-85b7-59c3ab54dc2f_VARS-pure-efi.fd</nvram>
  </os>
  <features>
    <acpi/>
    <apic/>
  </features>
  <cpu mode='host-passthrough' check='none' migratable='on'/>
  <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 BigSur/macos_disk.img'/>
      <target dev='hdc' bus='sata'/>
      <boot order='1'/>
      <address type='drive' controller='0' bus='0' target='0' unit='2'/>
    </disk>
    <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='pci' index='5' model='pcie-root-port'>
      <model name='pcie-root-port'/>
      <target chassis='5' port='0x8'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x0'/>
    </controller>
    <controller type='virtio-serial' index='0'>
      <address type='pci' domain='0x0000' bus='0x02' slot='0x00' function='0x0'/>
    </controller>
    <controller type='sata' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x1f' function='0x2'/>
    </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:fa:7a:64'/>
      <source bridge='br0'/>
      <model type='e1000-82545em'/>
      <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'/>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x41' slot='0x00' function='0x0'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x41' slot='0x00' function='0x1'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/>
    </hostdev>
    <hostdev mode='subsystem' type='pci' managed='yes'>
      <driver name='vfio'/>
      <source>
        <address domain='0x0000' bus='0x42' slot='0x00' function='0x0'/>
      </source>
      <address type='pci' domain='0x0000' bus='0x05' slot='0x00' function='0x0'/>
    </hostdev>
    <memballoon model='none'/>
  </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='************************'/>
    <qemu:arg value='-smbios'/>
    <qemu:arg value='type=2'/>
    <qemu:arg value='-cpu'/>
    <qemu:arg value='Penryn,kvm=on,vendor=GenuineIntel,+invtsc,vmware-cpuid-freq=on,+pcid,+ssse3,+sse4.2,+popcnt,+avx,+aes,+xsave,+xsaveopt,check'/>
  </qemu:commandline>
</domain>

 

Any help much appreciated

Edited October 17, 20214 yr by IJke
Add XML file

12 minutes ago, IJke said:

install OpenCore Configurator

^^ is wrong, you messed the bootloader.

 

 

 

Edited October 17, 20214 yr by ghost82

1 minute ago, ghost82 said:

^^ is wrong, you messed the bootloader.

 

It's one of the steps in SpaceInvaders video, download OpenCore Configurator, mount the paritions, copy bootloader over to desktop, then to main disk. Why do you think that step is wrong?

Just now, IJke said:

Why do you think that step is wrong?

I added a link in my reply above, read my comment in that link and also next answers if you want to use the configurator.

SIO used opencore configurator but missed to emphasize that you need a very specific version of the configurator if you want to use it.

2 minutes ago, ghost82 said:

I added a link in my reply above, read my comment in that link and also next answers if you want to use the configurator.

SIO used opencore configurator but missed to emphasize that you need a very specific version of the configurator if you want to use it.

 

Awesome, read it. So if i understand correctly my current config.plist is the issue because I used the wrong version of opencore configurator? Steps to resolve would be to put back the install media as primary/secondary disks, copy over fresh config.plist and edit in textedit rather than opencore configurator?

5 minutes ago, IJke said:

It's one of the steps in SpaceInvaders video

If you don't want to start again from scratch you may follow these steps:

https://forums.unraid.net/topic/84601-support-spaceinvaderone-macinabox/?do=findComment&comment=1041416

7 minutes ago, IJke said:

So if i understand correctly my current config.plist is the issue because I used the wrong version of opencore configurator?

Correct

7 minutes ago, IJke said:

Steps to resolve would be to put back the install media as primary/secondary disks, copy over fresh config.plist and edit in textedit rather than opencore configurator?

Not the install media, but the opencore vdisk (downloaded fresh) and boot from it.

You should be able to see the mac os disk and boot it; once booted mount both the efi (that of the mac os disk and that of the fresh opencore bootloader), replace the config.plist inside /EFI/OC folder (copied from the fresh opencore bootloader).

My advice is to use textedit if you want to edit the config.plist.

 

Others suggested using opencore configurator v. 2.19.1.0 but I don't think it's the correct version, since it was released in december 2020 and the opencore image I pulled to macinabox is v. 0.7.0, released in june 2021.

I prefer textedit, so I can blame only myself if I mess the configuration.

Edited October 17, 20214 yr by ghost82

15 hours ago, elin1923 said:

Anyone have ideas on how to fix it?

Depending on the method you chose the container has to download about 11 GB or few hundreds of MB, then it has to initialize the installation.

No need to fix anything, just wait.

27 minutes ago, IJke said:

and edit in textedit

btw there's no need to edit anything in the default config.plist, it should be able to boot correctly.

You will need to edit it if you customize the hardware, for example if you start to passthrough devices and you need patches/injections to make it to work.

2 hours ago, ghost82 said:

btw there's no need to edit anything in the default config.plist, it should be able to boot correctly.

You will need to edit it if you customize the hardware, for example if you start to passthrough devices and you need patches/injections to make it to work.

 

Thank you, should I still mount the drives and copy over bootloader with OpenCore Configurator?

4 hours ago, IJke said:

 

Thank you, should I still mount the drives and copy over bootloader with OpenCore Configurator?

you can use opencore configurator to mount efi partitions with no issues, just don't open the config.plist with the configurator.

Edited October 17, 20214 yr by ghost82

should a macinabox Big Sur have a similar performance like a physical Mac? I own both (vm and MacBook Pro) and there are lightyears between both, although the VM is sitting on NVME SSD, has 8GB mem and 8 cores (Ryzen 9 CPU).

 

I am not using any GPU.

 

Any advice?

6 minutes ago, doesntaffect said:

 

I am not using any GPU.

that is the issue, mac os without video metal acceleration is just crap to use as a everyday machine.

Got it. I want remote into the vm only, not sitting in front of the unraid host. Would a GPU also improve the VNC performance?

If so, which cheap (no gaming) GPU to pick? Ideally a passive one like Geforce GT1030 or similar.

10 minutes ago, doesntaffect said:

Would a GPU also improve the VNC performance?

If so, which cheap (no gaming) GPU to pick? Ideally a passive one like Geforce GT1030 or similar.

Yes, of course, mac os needs a physical gpu to have video acceleration to which you can attach a dummy plug to emulate an attached monitor if you only access mac os remotely.

As far as gpu choice amd should be better, even if they suffer the so called gpu reset bug, but patch in the kernel exists to overcome this issue (gnif vendor reset patch, implemented as an addon for unraid).

I would avoid nvidia, for compatibility, I have a kepler gtx titan black, but it will no more supported in monterey and a patch will be required.

The 1030 you mention, for example, is compatibile only up to high sierra with the nvdia drivers, no support in mojave/catalina/big sur/monterey.

You should read the "dortania gpu guide": from there you can see gpu comparibility.

looks like all reasonable (max. TDP) AMD GPUs are sold out or priced like a decent car , Haven't followed that area to close but the mining / supply shortage seem to have still an impact on the marked,

11 minutes ago, doesntaffect said:

priced like a decent car

100% agree, some older amd gpus are still good, not as the 5k or 6k series but if you don't want to sell a part of your body for a gpu...

 

Help spaceinvaderone you are my only hope...

Hi, first, thank you for make vms easier to make in unraid I really appreciate your efforts.

Since im a little dumb, probably this is already answered but Im not been able to find someone with the same problem im experiencing:

I did follow your step by step guide by the letter installing bigsur. Everything goes fine until I delete the extra disks, seems something is missing in my install because I keep geting this (tried this many times) 

 (no gui) and then I get an err that doesnt recover

 

seems that im missing something at the UEFI copy thing, but im unable to figure it out.

 

Can you help me?

Thanks!

5 hours ago, CBMX said:

Can you help me?

I don't say to read the whole thread, but at least the last few pages?

This issue and the solution were posted at least a couple of time very recently.

Edited October 19, 20214 yr by ghost82