paulmorabi

Members
  • Posts

    103
  • Joined

  • Last visited

Everything posted by paulmorabi

  1. OK, that makes sense! So, if I want to keep the current EFI, I can change the above and then 1. How do I disable the additional logging (when ready)? 2. How can I remove the option to clear NVRAM or Boot OSX (also once ready)?
  2. I've made great progress. I created a new VM and modified only a few areas - added a usb keyboard, adjusted the network card model and commented out the topology line. Current XML is as follows: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>OSX Catalina</name> <uuid>de64714c-4863-ade9-48f9-6689fd040f1c</uuid> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="osx.png" os="linux"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>4</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='1'/> <vcpupin vcpu='2' cpuset='2'/> <vcpupin vcpu='3' cpuset='4'/> </cputune> <os> <type arch='x86_64' machine='pc-q35-5.0'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF_CODE-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/de64714c-4863-ade9-48f9-6689fd040f1c_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='custom' match='exact' check='none'> <model fallback='forbid'>qemu64</model> <!--<topology sockets='1' dies='1' cores='4' 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/OSX Catalina/vdisk1.img'/> <target dev='hdc' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback' io='threads'/> <source file='/mnt/user/domains/OSX Catalina/BaseSystem.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='qcow2' cache='writeback'/> <source file='/mnt/user/domains/OSX Catalina/OpenCoreEFI.qcow2'/> <target dev='hde' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='4'/> </disk> <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> <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='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </controller> <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-to-pci-bridge'> <model name='pcie-pci-bridge'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <interface type='bridge'> <mac address='52:54:00:b7:9c:1e'/> <source bridge='br0'/> <model type='e1000-82545em'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' 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'/> <input type='keyboard' bus='usb'> <alias name='input2'/> <address type='usb' bus='0' port='3'/> </input> <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='0x04' slot='0x00' function='0x0'/> </memballoon> </devices> <qemu:commandline> <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> I created my own EFI from Leoyzen's GitHub and it did the same Tiano Core bootloop. I used the OpenCoreEFI attached to an earlier thread here with the option to clear NVRAM and also boot OSX. The installer and whole install procedure was in Chinese for some reason and I had to wait until after install to change to English. I'm curious as to the differences between the EFI from GitHub and the debug one. Are there any specific additions that could have fixed the boot loop? (if its CPU based, I'm running a Ryzen 3600XT). I'll next attempt the pass through of my RX570. Thanks for all of your help so far.
  3. OK I will do this. Which XML should I begin with? Created from within Unraid or the one from Leoyzen's GitHub?
  4. It's possible I changed it as I've changed so many things to try and get this working. Anyhow, I changed to what you recommended and it's giving the same bootloop Tiancore logo
  5. OK so using the OpenCore from Leoyzen. I disabled first WhateverGreen and Lilu. This led to a bootloop at the Tiancore logo. I then disabled all of the other kernel modules and it's doing the same thing. Re-enabling them, and at the point where it should boot the UEFI the screen flashes and changes size between big and small and occasionally displays a graphical glitch.
  6. Here EDIT: I've tried changing various aspects of the config such as graphics, adding the smbios and Apple key flags etc. and the error is always the same. If it helps, I'm using the latest beta Unraid. EDIT 2: I tried the latest qcow2 images from kholia/OSX-KVM repository. The standard one OpenCore.qcow2 gives the same kernel panic. The passthrough image hangs at the Apple logo. I keep reading about people loading kexts etc. but from what I've seen within this thread, it should be possible to use these images to get up and running with USB, GPU pass-through etc. I'm really stumped!
  7. Removing that line moves me forward a little. I get a Kernel panic now. I tried changing CPU cores to 2 and it gave the same panic.
  8. Hi, I've set up my Unraid and am trying to get OpenCore sorted and my VM booted. Firstly, my libvirt config is her: <?xml version='1.0' encoding='UTF-8'?> <domain type='kvm'> <name>OSX Catalina</name> <uuid>fe4fb58e-51df-092b-3abf-9214097e89fc</uuid> <metadata> <vmtemplate xmlns="unraid" name="Linux" icon="default.png" os="linux"/> </metadata> <memory unit='KiB'>8388608</memory> <currentMemory unit='KiB'>8388608</currentMemory> <memoryBacking> <nosharepages/> </memoryBacking> <vcpu placement='static'>3</vcpu> <cputune> <vcpupin vcpu='0' cpuset='0'/> <vcpupin vcpu='1' cpuset='2'/> <vcpupin vcpu='2' cpuset='4'/> </cputune> #<os> # <type arch='x86_64' machine='pc-q35-5.0'>hvm</type> # <loader readonly='yes' type='pflash'>/usr/share/qemu/osx/OVMF_CODE.fd</loader> # <nvram>/etc/libvirt/qemu/nvram/OSX_OVMF_VARS.fd</nvram> #</os> <os> <type arch='x86_64' machine='pc-q35-5.0'>hvm</type> <loader readonly='yes' type='pflash'>/usr/share/qemu/ovmf-x64/OVMF-pure-efi.fd</loader> <nvram>/etc/libvirt/qemu/nvram/fe4fb58e-51df-092b-3abf-9214097e89fc_VARS-pure-efi.fd</nvram> </os> <features> <acpi/> <apic/> </features> <cpu mode='host-passthrough' check='none'> <topology sockets='1' dies='1' cores='3' threads='1'/> <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/OSX Catalina/vdisk1.img'/> <target dev='hdc' bus='sata'/> <address type='drive' controller='0' bus='0' target='0' unit='2'/> </disk> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='writeback' io='threads'/> <source file='/mnt/user/domains/OSX Catalina/Catalina-installer.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='qcow2' cache='writeback'/> <source file='/mnt/user/domains/OSX Catalina/OpenCoreEFI.qcow2'/> <target dev='hde' bus='sata'/> <boot order='1'/> <address type='drive' controller='0' bus='0' target='0' unit='4'/> </disk> <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> <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-to-pci-bridge'> <model name='pcie-pci-bridge'/> <address type='pci' domain='0x0000' bus='0x01' slot='0x00' function='0x0'/> </controller> <controller type='pci' index='3' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='3' port='0x11'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x1'/> </controller> <controller type='pci' index='4' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='4' port='0x12'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x2'/> </controller> <controller type='pci' index='5' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='5' port='0x13'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x3'/> </controller> <controller type='pci' index='6' model='pcie-root-port'> <model name='pcie-root-port'/> <target chassis='6' port='0x14'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x4'/> </controller> <controller type='virtio-serial' index='0'> <address type='pci' domain='0x0000' bus='0x03' slot='0x00' function='0x0'/> </controller> <interface type='bridge'> <mac address='52:54:00:6e:40:06'/> <source bridge='br0'/> <model type='virtio-net'/> <address type='pci' domain='0x0000' bus='0x02' slot='0x01' 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='0x05' slot='0x00' function='0x0'/> </memballoon> </devices> <qemu:commandline> <qemu:arg value='-cpu'/> <qemu:arg value='Penryn,vendor=GenuineIntel,+hypervisor,+invtsc,kvm=on,+fma,+avx,+avx2,+aes,+ssse3,+sse4_2,+popcnt,+sse4a,+bmi1,+bmi2'/> </qemu:commandline> </domain> When I generate a OpenCore qcow2 image myself using the instructions provided, the system boots but the VNC connection flickers between a small and big screen endlessly. If I quit and reconnect then it shows only a blank screen. I notice someone had a similiar issue and a debug image was provided. If I use this, I can boot OSX but get the following error: From a search around, this can be because of missing drivers or kexts? Any help with this would be really appreciated. I had OSX running well under Proxmox but am completely new to Unraid. Thanks!
  9. thanks for the reply. Do you mean even a USB flash drive to begin with?
  10. Hi, I'm a complete beginner with Unraid but have experience with other similar tools. I've just received my new PC, connected everything and booted into Unraid. All good so far. Currently, I haven't added any disks except for a 1TB SSD that I was planning to use for VM's. I'm planning to shuck some drives once they go on special and in the meantime was going to use Unraid as a VM host only. This is where the problem is. Do I need to put the SSD into the array or is there some other way I can set it up for VM image stoage only? Any help would be very appreciated. Thanks!
  11. I'll do some searching for nested virtualization in AMD. Thanks. Re: EFI, I'll start with the GitHub link and wait for OpenCore to get updated when Big Sur is officially released. I noticed minor glitches in my Proxmox based Big Sur OSX VM after upgrading between the betas so better to stay stable than on the cutting edge!
  12. @ghost82 thanks for the details. Regarding the iso, I did as per this how to and used dmg2img (which technically made a disk image rather than iso). Then added that as a disk to the VM and booted from it. Noted on the CPU arguments. I'll stick with Penryn and pass through the recommended flags. Not too fussed about nested virtualization so I'll leave it for now. About the EFI disk change whn upgrading to Big Sur. I did this successfully when upgrading the VM from the above install. After first reboot of the upgrade, at the point opencore bootloader appeared, I shut down the VM and swapped the EFI disks to use the latest OpenCore with Big Sur support. Everything worked from there. Originally, I considered to move this install from Proxmox but I suspect a clean install is more straightforward. And yes, will definitely be using OpenCore. BTW when you said the two EFI are compatible, which did you mean? The one in the Github link on the first page? If so, you should be able to upgrade to Big Sur without any EFI change?
  13. Hi everyone, I'm about to build my first Unraid box and am looking into getting an OSX VM up and running. I've successfully completed this with Proxmox in the past and although the overall process seems similar, not being familiar with UnRaid, I am unsure of a few things. I would really appreciate any help as I am trying to get everything planned so I can get it all up and running fast. General steps would be to obtain the OSX Catalina image and convert to iso (I'll start with this and move to Big Sur when stable) install image. This would be as per the instructions on the OSX KVM site. Using the EFI disk from the GitHub link in the first post, set up a VM, pass through the graphics card (RX570). At this stage, configure the CPU and the flags to pass to the VM. I'm not 100% sure here how or what to do: Previously, I used Penryn but in those case, OSX won't be able to identify the supported flags so I need to pass them though? If so, is it just the ones in the list on the first page? Does Unraid support nested virtualization so I can run docker inside OSX? Or, can I pass through the host CPU which would be an AMD 3600XT? I saw SpaceInvader1's advanced video mention you can pass host first and then put Penryn at the bottom of the XML? After setup, start the VM, install OSX onto disk. When complete, unmount the iso and hopefully it boots OSX. At this point, I can look to forward some USB ports so I can connect a bluetooth adaptor and other peripherals (mouse etc.). Has anyone had any experience passing a Bluetooth adaptor and using it for pairing with a Bluetooth speaker? Finally, when Big Sur is ready, the general upgrade process would be to do the update through the OS and swap for a new EFI disk. Any help would be very appreciated! Thanks,
  14. Hi, Is there a way to install the latest beta directly rather than installing the stable and then changing the release channel/track to beta? The reason I ask is that my motherboard will have the RealTek 2.5G LAN interface that is only supported in the latest beta. If I install 6.8 then I am not sure how to upgrade without network connectivity. Thanks
  15. @ghost82 Thank you so much for the reply. I understand fully.
  16. Thanks. Yes, I saw the above though it's running Clover rather than Opencore (which is generally considered better) and also not Big Sur (at least yet).
  17. Hi, I'm building a new HTPC/NAS and have been considering to give Unraid a try on it as I've heard many great things. Previously, I've used Open Media Vault, QNAP systems and also Proxmox based hypervisor for hosting VM's (OSX, Linux, Windows). Hardware wise, it will be Ryzen based system with either a GT730 (Kepler) or RX560 graphics card as I understand both of these will work in OSX up to Big Sur. They're also both relatively small and low temperature/power so good for a compact case (Fractal Design Node 804). I've been reading through the forums and it looks like people are generally having issues with OSX on Unraid. Has anyone gotten Big Sur running? Actually, I am a little confused as to the many issues as there is a OpenCore OSX/KVM github project and in the case of Proxmox, a slightly modified OpenCore also available (https://github.com/thenickdude/KVM-Opencore). If there is something specific that makes this more difficult then let me know. Finally, are there any general notes or feedback on adding SATA3 cards? I've read to avoid Marvell chipsets. Are there any other recommended reasonably priced 4/6 port cards that work with UnRaid? Any thoughts would be very appreciated.