Leaderboard

intendo le tue acpi originali, quelle della scheda madre che hai allegato prima e non quelle che usi 🙂

@JaidyI have messaged you.

welcome here @boolean 🙂 you have to lock in your bios your great cpu @32 cores 32 threads or 64 core without SMT (better for performance) this is an OSX limits

No, no particular lag You have to stress in your ideal pipeline job condition...f it is good for you 🙂 You have an ideal system with black screen it is not ideal (imho)

ok for each different one you have to convert it Fromm ex to decimal..and put in your config.plist mmio whithelist in this way

before you have to see newer one put #in front your mmiolist in config and check the new mmio list (all skipped to 0 should be (Yoda) 🙂

simply...have you connected the power on it?

Ioreg is a photography of all your system

to do additional steps..you have to post your IOREG as I said above..from there is possible to see many things to optimize your system 😉

No for latest question in your bios you should decide boot option Choose internal disk where you have your booting EFI and save disconnect uSB and see if system starts from your internal disk if starts, with my config (I mean) put here an IOREG to have one, save it, compress it and put here then some people with skill in ssdt creation could help you I do not use any SSDT but if you want to use it is your choice 🙂 About kext..there you can use all kext you need to have a proper WIFI or BT working..I do not use it so you have to ask to users using your same models you have only to add in kexts folder and then declare them in your config in Kernel/add but... before B A C K U P this EFI 😛 and... if you change BIOS settings you could have the need to modify your MMIO...so pay attention 🙂

I think you have mixed stuff in two different efi copy completely this refi on your HDD's EFI replace completely then boot always from your HD thanks

11:361 00:002 OCABC: MMIO devirt 0xE2100000 (0x81 pages, 0x8000000000000001) skip 1 11:364 00:003 OCABC: MMIO devirt 0xE3180000 (0x81 pages, 0x8000000000000001) skip 1 11:367 00:002 OCABC: MMIO devirt 0xEF100000 (0x181 pages, 0x8000000000000001) skip 1 11:370 00:003 OCABC: MMIO devirt 0xFA180000 (0x81 pages, 0x8000000000000001) skip 1 11:373 00:002 OCABC: MMIO devirt 0xFA300000 (0x100 pages, 0x8000000000000001) skip 1 11:376 00:002 OCABC: MMIO devirt 0xFEA00000 (0x100 pages, 0x8000000000000001) skip 1 11:379 00:002 OCABC: MMIO devirt 0xFEC00000 (0x1 pages, 0x8000000000000001) skip 1 11:382 00:003 OCABC: MMIO devirt 0xFEC10000 (0x1 pages, 0x8000000000000001) skip 1 11:385 00:002 OCABC: MMIO devirt 0xFED00000 (0x1 pages, 0x8000000000000001) skip 1 11:388 00:002 OCABC: MMIO devirt 0xFED40000 (0x5 pages, 0x8000000000000001) skip 1 11:391 00:002 OCABC: MMIO devirt 0xFED80000 (0x10 pages, 0x8000000000000001) skip 1 11:394 00:002 OCABC: MMIO devirt 0xFEDC2000 (0xE pages, 0x8000000000000001) skip 1 11:397 00:002 OCABC: MMIO devirt 0xFEDD4000 (0x2 pages, 0x8000000000000001) skip 1 11:400 00:002 OCABC: MMIO devirt 0xFEE00000 (0x100 pages, 0x8000000000000001) skip 1 11:403 00:003 OCABC: MMIO devirt 0xFF000000 (0x1000 pages, 0x8000000000000001) skip 1 11:406 00:003 OCABC: MMIO devirt 0x1040000000 (0x10400 pages, 0x8000000000000001) skip 0 11:409 00:002 OCABC: MMIO devirt 0x6EE0000000 (0x10400 pages, 0x8000000000000001) skip 0 11:412 00:002 OCABC: MMIO devirt 0x6F10000000 (0x10400 pages, 0x8000000000000001) skip 0 11:415 00:003 OCABC: MMIO devirt 0xCDB0000000 (0x10400 pages, 0x8000000000000001) skip 0 now these are like they should be Are you sure you have not touched anything in your bios settings? CSM is on or off? Before third MMIO was different and your system started check this and do not touch anything 😉

config.plist 2.zip same as above delete all open core txt debug and do two reboot 11:167 00:001 OCABC: MMIO devirt 0xE2100000 (0x81 pages, 0x8000000000000001) skip 0 11:168 00:001 OCABC: MMIO devirt 0xE3180000 (0x81 pages, 0x8000000000000001) skip 0 11:169 00:001 OCABC: MMIO devirt 0xEF100000 (0x181 pages, 0x8000000000000001) skip 0 11:171 00:001 OCABC: MMIO devirt 0xFA180000 (0x81 pages, 0x8000000000000001) skip 0 11:172 00:001 OCABC: MMIO devirt 0xFA300000 (0x100 pages, 0x8000000000000001) skip 0 11:173 00:001 OCABC: MMIO devirt 0xFEA00000 (0x100 pages, 0x8000000000000001) skip 0 11:174 00:001 OCABC: MMIO devirt 0xFEC00000 (0x1 pages, 0x8000000000000001) skip 0 11:175 00:001 OCABC: MMIO devirt 0xFEC10000 (0x1 pages, 0x8000000000000001) skip 0 11:177 00:001 OCABC: MMIO devirt 0xFED00000 (0x1 pages, 0x8000000000000001) skip 0 11:178 00:001 OCABC: MMIO devirt 0xFED40000 (0x5 pages, 0x8000000000000001) skip 0 11:179 00:001 OCABC: MMIO devirt 0xFED80000 (0x10 pages, 0x8000000000000001) skip 0 11:180 00:001 OCABC: MMIO devirt 0xFEDC2000 (0xE pages, 0x8000000000000001) skip 0 11:181 00:001 OCABC: MMIO devirt 0xFEDD4000 (0x2 pages, 0x8000000000000001) skip 0 11:182 00:001 OCABC: MMIO devirt 0xFEE00000 (0x100 pages, 0x8000000000000001) skip 0 11:183 00:001 OCABC: MMIO devirt 0xFF000000 (0x1000 pages, 0x8000000000000001) skip 0 11:184 00:001 OCABC: MMIO devirt 0x1040000000 (0x10400 pages, 0x8000000000000001) skip 0 11:186 00:001 OCABC: MMIO devirt 0x6EE0000000 (0x10400 pages, 0x8000000000000001) skip 0 11:187 00:001 OCABC: MMIO devirt 0x6F10000000 (0x10400 pages, 0x8000000000000001) skip 0 11:188 00:001 OCABC: MMIO devirt 0xCDB0000000 (0x10400 pages, 0x8000000000000001) skip 0 I have converted these above if you change slot position or bios option they could change and we will become crazy to solve your problem

config.plist.zip before booting with this one delete open core txt log (all) then boot two times with this and post config.plist and two opencore txt debug files Do not touch anything else please

see first skip 0 ? yesterday it was to 1 🙂 check latest result we have yesterday then, for shutdown and restart you should find proper combinations I think with 1 there it could works also for you

I would start with a more clean config.plist and you would try to solve your problem with your monitor then it is more simple to do the missing optimization (if possible 😛 ) I can't help on bluetooth configuration but you have to solve a problem and then try to solve others 🙂 so use MMIO list I have produced yesterday for you..and try to solve your monitor problem first. How? enabling or disabling whatevergreen kext clearing Nvram.. only you could test then search on bios wake on lan parameter if you have..and maybe also with this you could solve "others" problem (ask to gigabyte users here)

Verbose time is pretty fine login time no try to change hdmi or display port you are using also try to disable whatever green kext and if you have black screen without restarting change display port and see if some ports have signal

config.plist.zip I hope this solve your freeze 🙂

yes because no pikera booting in there..I have thought you have Nvidia.. 48:200 00:054 OCABC: MMIO devirt 0xE2100000 (0x81 pages, 0x8000000000000001) skip 0 48:237 00:036 OCABC: MMIO devirt 0xE3180000 (0x81 pages, 0x8000000000000001) skip 0 48:273 00:036 OCABC: MMIO devirt 0xEA400000 (0x181 pages, 0x8000000000000001) skip 0 48:309 00:036 OCABC: MMIO devirt 0xFA180000 (0x81 pages, 0x8000000000000001) skip 0 48:345 00:036 OCABC: MMIO devirt 0xFA300000 (0x100 pages, 0x8000000000000001) skip 0 48:404 00:058 OCABC: MMIO devirt 0xFEA00000 (0x100 pages, 0x8000000000000001) skip 0 48:440 00:036 OCABC: MMIO devirt 0xFEC00000 (0x1 pages, 0x8000000000000001) skip 0 48:476 00:036 OCABC: MMIO devirt 0xFEC10000 (0x1 pages, 0x8000000000000001) skip 0 48:512 00:035 OCABC: MMIO devirt 0xFED00000 (0x1 pages, 0x8000000000000001) skip 0 48:548 00:036 OCABC: MMIO devirt 0xFED40000 (0x5 pages, 0x8000000000000001) skip 0 48:602 00:053 OCABC: MMIO devirt 0xFED80000 (0x10 pages, 0x8000000000000001) skip 0 48:638 00:036 OCABC: MMIO devirt 0xFEDC2000 (0xE pages, 0x8000000000000001) skip 0 48:674 00:036 OCABC: MMIO devirt 0xFEDD4000 (0x2 pages, 0x8000000000000001) skip 0 48:710 00:036 OCABC: MMIO devirt 0xFEE00000 (0x100 pages, 0x8000000000000001) skip 0 48:747 00:036 OCABC: MMIO devirt 0xFF000000 (0x1000 pages, 0x8000000000000001) skip 0 48:805 00:058 OCABC: MMIO devirt 0x1040000000 (0x10400 pages, 0x8000000000000001) skip 0 48:841 00:036 OCABC: MMIO devirt 0x6EE0000000 (0x10400 pages, 0x8000000000000001) skip 0 48:878 00:036 OCABC: MMIO devirt 0x6F10000000 (0x10400 pages, 0x8000000000000001) skip 0 48:914 00:036 OCABC: MMIO devirt 0xCDB0000000 (0x10400 pages, 0x8000000000000001) skip 0 these are your MMIO with bios you are using by now and they are different from @Ploddlesone posted in OP of other thread My questions are: 1) same BIOS 2)CSM on or off?

ok then add pikera boot arg to posted config above 😛

please do not modify anything otherwise I will be crazy to understand I will explain what I want to do I would like that your system uses your MMIO.. so we have to convert it for you and see if in txt they are skipped to 1

I mean if system is on try to change port where you connect your Monitor other DP, other HDMI I have disabled WEG kext and applealc

@Driftwood i would like to suggest you to read this thread https://forum.proxmox.com/threads/vm-w-pcie-passthrough-not-working-after-upgrading-to-6-0.56021/ Here is possible also to understand what that args you add in your vm does i think not necessary but reading that thread you can understand better how a working pcie root/ bridge are related to qemu config... about 47:00 controller..in my case 46:00... you should investigate better 😜

@iGPU this is mine, I use a script given on amd discord by @pshirshov user, he should be also here I think with maybe other nickname: IOMMU Group 49: 42:08.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57a4] 46:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485] 46:00.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] 46:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] IOMMU Group 50: 42:09.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57a4] 47:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) IOMMU Group 51: 42:0a.0 PCI bridge [0604]: Advanced Micro Devices, Inc. [AMD] Device [1022:57a4] 48:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) to copy examples you did 46:00.0 Non-Essential Instrumentation [1300]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485] Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse Reserved SPP [1022:1485] Kernel driver in use: vfio-pci 46:00.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] Subsystem: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:1486] Kernel driver in use: vfio-pci Kernel modules: xhci_pci 46:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] Subsystem: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:148c] Kernel driver in use: vfio-pci Kernel modules: xhci_pci 47:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] Kernel driver in use: vfio-pci Kernel modules: ahci 48:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] Kernel driver in use: vfio-pci Kernel modules: ahci and this is achieved only with: hostpci9: 46:00.1 hostpci10: 46:00.3 hostpci11: 47:00 hostpci12: 48:00 47:00, 48:00 are my sata controllers: Qemu hard disk here is my Catalina on disk file the others are my mechanical disks installed and passed thanks to 47:00, 48:00 controllers

@iGPU i think you and others are doing many tests how I did. Maybe you should try to follow some my previous finding. trx40 does not need stuff inside vfio.conf in can’t stated definitely because our system are a bit different but I am sure of this (95% that it is so) try to pass only 46:00 or only 46:00.1 and 46:00.3 you will see that 42.08.0 and 46:00.0 will be connected to vfio without declaring it in vm and this happens for many device you can pass. simple way to understand this is to connect a mouse and a keyboard to usb3 backplate internal ports then add in vm only hostpci0: your vga here hostpci1: 46:00.1 hostpci2: 46:00.3 hostpci3: your OS X nvme disk controllers ( in my case 02:00) to do in exact copy of a your starting vm named progressively i think your system starts and you can verify with lspci -nnk all stuff connected in automatic to vfio when I on my amd I will try to complete better...

hi @Rox67erto fix audio I use ..Catalina in my case but I think also in all trx40 motherboard you have to pass only two USB controllers in my case 46:00.1 and 46:00.3 passing this you have your realtek audio exposed in Catalina and it should work also for you If not , reboot Catalina without audio jack connection (green jack one (speaker output) and connect it after login (I think jack detection is not working well.. ah your right controller should be 47:00.1 and 47:00.3 with only this you can have all usb mapped (testing by now so take as it come and test also by yourself) I can also pass all controllers (and also you can with 3 problematic ones you have to use FLR patch) I discover that for us (trx40 owner I mean) we need to patch 148c ID to pass problematics controllers, I asked to Pavo to build for me a kernel patch for trx40 users adapting the original one for x570 you can find in vfio/reddit post and then He has upload also on his github. and these are all my controller passed I have eliminated old usb vm stuff you can find in /usr/share/qemu-server/pve-q35-4.0.cfg

😂😂😂 Catalina internal Realtek 2.0 audio problem....solved 🙂 I have reached my internal peace...no more talking for me about audio (but if you find a way to use internal audio Catalina stuff In high Sierra I will happy to try)

Below al controller I can pass in my MSI TRX40 Pro 10G: Marked in light yellow are controllers I can pass using FLR patches (id 148c) All the others mainboard controllers are passed well from first Proxmox release I have installed (6.1) my next goal is audio..ehm joking 🙂 is to understand if all other USB passed are useful or not.. now I will duplicate this vm and disable all usb except 46:00.1 and 46:00.3..my feeling is that all usb will be there again with other usb...

Ah I have mapped in ioreg all USB ports after passing all usb entire controllers interesting thing is that high Sierra does not see usb3 devices catalina instead yes i think also usb related problems are due to OS X versions

in my opinion is an OSX problem (windows VM Is perfect in this), maybe in connection with CPU tsc or frequency..because audio is there..but different problems Then it seems that some audio USB with DAC have no problem Researchingyou can see it is also a problem with usb audio in real Mac..

I disagree (in friendship) 🙂 ok a separated disk for any OSX..but then I boot from OC or clover to execute one of them and in my VM test I have also a Catalina OSX on a qemu file. I would like to understand better problems many of you have to pass your controllers From your lspci -nnk I see it is possible to pass all controllers in the same way I do (some of them using FLR patch). Other thing I am very interested is if for you it is mandatory to put stuff on vfio.conf or in blacklist.conf..because it shouldn't (on TRX40) And, if it is mandatory I see only a main difference from our rigs..GFX card by the way @Driftwoodpassing your Blackmagic card you did my day better 🙂 Thank you

@AllubzV and @all interested to solve audio problem try to pass all your main USB controller and boot with audio jack disconnected (in my case hostpci: 46:00)..audio instead should be 23:00.4 (and do not pass it) No need to patch FLR

@Driftwood your Realtek ethernet in osx should supported from this kext by Mieze:

Have you put kext for your intel? otherwise OS X do not see it or maybe I miss your problem completely😂

a discover...not useful but... Our internal USB Realtek USB 2.0 audio does no need any additional kext for "working"... it works (bad) with only OSX system kext

Gigabyte TRX40 Designare ASrock TRX40 Creator I would also use this USB port to have a proxmox disk connected and installed with all useful things (like VM and so on) this helps to pass more easily all other controllers

@Driftwood novnc problem is related to passed gpu and none in display VM config line if you access to your amd from another pc/device you have to change that none and block gpu bybass (maybe) in my experience any problem your rig can have (if it has been working well before) is caused from an user problem 😊 network problem could be tricky if you installed Proxmox with vmxnet3 in vm config and if you pass the same network controller you will have proble or to navigate or to access to webinterface because passed ethernet will take your ip (ip you used in installation step) and conseguentially it assign a different ip to your vmxnet3 device (assuming you are in dchp for both) @iGPU this should be last question about audio😂 do you know which driver is using your working audio device?

@iGPU in verbose maybe you can see where it hangs before login ?

Mmmmh maybe you have to revert to a not patched kernel? my booting time is very fast and all usb controller are on without problem I have opened a thread on proxmox forum for audio problem but it is hard to explain and I do not think is a proxmox problem because with same distro config a Windows vm is working perfectly usb part of your thunderbolt is working?

If you have windows installed you can use it in my case I use grub bootloader (proxmox) to boot and decide what I want use you have to find a solution for you better for you I mean 👍

00:14.0 SMBus [0c05]: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller [1022:790b] (rev 61) Subsystem: ASRock Incorporation FCH SMBus Controller [1849:ffff] Kernel driver in use: piix4_smbus Kernel modules: i2c_piix4, sp5100_tco 03:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 [Radeon VII] [1002:66af] (rev c1) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 [Radeon VII] [1002:081e] Kernel driver in use: vfio-pci Kernel modules: amdgpu 03:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 HDMI Audio [Radeon VII] [1002:ab20] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 HDMI Audio [Radeon VII] [1002:ab20] Kernel driver in use: vfio-pci Kernel modules: snd_hda_intel 05:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller [1022:148c] Subsystem: ASRock Incorporation Starship USB 3.0 Host Controller [1849:ffff] Kernel driver in use: xhci_hcd 23:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 [Radeon VII] [1002:66af] (rev c1) Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 [Radeon VII] [1002:081e] Kernel driver in use: vfio-pci Kernel modules: amdgpu 23:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 HDMI Audio [Radeon VII] [1002:ab20] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Vega 20 HDMI Audio [Radeon VII] [1002:ab20] Kernel driver in use: vfio-pci Kernel modules: snd_hda_intel 25:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller [1022:148c] Subsystem: ASRock Incorporation Starship USB 3.0 Host Controller [1849:ffff] Kernel driver in use: xhci_hcd 25:00.4 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller [1022:1487] Subsystem: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller [1022:d102] Kernel modules: snd_hda_intel 43:00.0 Non-Volatile memory controller [0108]: Phison Electronics Corporation Device [1987:5016] (rev 01) Subsystem: Phison Electronics Corporation Device [1987:5016] Kernel driver in use: nvme 44:00.0 USB controller [0c03]: ASMedia Technology Inc. Device [1b21:3242] Subsystem: ASMedia Technology Inc. Device [1b21:3242] Kernel driver in use: xhci_hcd 45:00.0 Ethernet controller [0200]: Aquantia Corp. AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] [1d6a:07b1] (rev 02) Subsystem: ASRock Incorporation AQC107 NBase-T/IEEE 802.3bz Ethernet Controller [AQtion] [1849:d107] Kernel driver in use: atlantic Kernel modules: atlantic 48:00.1 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] Subsystem: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:1486] Kernel driver in use: xhci_hcd 48:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:149c] Subsystem: Advanced Micro Devices, Inc. [AMD] Matisse USB 3.0 Host Controller [1022:148c] Kernel driver in use: xhci_hcd 49:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] Kernel driver in use: ahci Kernel modules: ahci 4a:00.0 SATA controller [0106]: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] (rev 51) Subsystem: Advanced Micro Devices, Inc. [AMD] FCH SATA Controller [AHCI mode] [1022:7901] Kernel driver in use: ahci Kernel modules: ahci 4b:00.0 Non-Volatile memory controller [0108]: Phison Electronics Corporation Device [1987:5016] (rev 01) Subsystem: Phison Electronics Corporation Device [1987:5016] Kernel driver in use: nvme @Driftwoodin my experience you can pass all of these listed above using previous FLR posted Kernel patch It is also possible to have some problem if you use sata or nvme disk (for proxmox installation)..I use ASMedia usb 3.2 type controller for Proxmox so I do not share with proxmox my sata or nvme controller when VM starts, and I pass entire sata/nvme controllers to boot in "vanilla" OSX/Windows VM I would like also to suggest to comment amdgpu,radeon and nouveau lines in blacklist.conf to have a more friendly AMD system (you can run command from this instead to use another pc/device to modify things) if you try..be prepared to solve possible problems 🙂

@Driftwood I asked before post if you want your vm config your lspci -nnk output your modules file your kvm.conf file..and all thing could be useful motherboards are different and you have a radeon which could be more problematic...but solutions could be similar for others controller.. Stay for now with Imacpro1.1 @AllubzV I think did an example to explain that more GPU are possible also in real Mac (and obviously in our hackintosh)

@AllubzV yes i think so for internal device..also i have bought a cheaper USB audio device and it has the same problem For your problem try to see if you have your KVM.conf file (MSR related) in my case that was the problem

Hi 1) yes you can use it* 1b) no no clean installation is required 2) if you want to use an exist OSX instalaltion yes, if you use a disk in a virtual file no 3) success dipend from your skill and patience. It is not simple but many users with your same rig (a vanilla Patches supported system) are trying proxmox having less problem with compatibility for app (0 problem) and better gpu performances It is Tricky but it could work 🙂 * you have to pass your disk controller or single disk (SATA, NVME..) To have a detailed answer you have to read all the post here and also in main guide.. you can also check @Pavo GitHub , there you will find a system more similar to yours

@iGPU I monitor my temps with my motherboard led code display in bios there is an option to monitor temps trulyspinach app does not work one kext seems to output a missing cpu Id in verbose

I did..in my case yes..no improvement but it is latest available so could have some benefit I cannot see by now I f you are unsure stay with old version

do not update for now now also my minimal Vm hangs on ++++++++ end seed both with clover 5107 and opencore 0.58 try to revert to old kernel by now i hope it is enough to start again my VM 😂 upgrading deleted my lvm.conf file so this was the reason for the hang on ++++++++ phase (MSR related)

@AllubzV this could be the command (boot parameter) for me to test...adding where? they say boot argument.. I have tested in grub.cfg with no success for now pcie_no_flr=1022:148c,1462:cb60

to all: Maybe it is not well shown in the guide but you have to remember a thing: Clover/OpenCore iso image we upload on Proxmox appropriate folder if associated in our VM config it become a normal bootable EFI as we have in a "real" hackintosh So, if you modify it you automatically modify uploaded iso file in proxmox. ie my clover.iso I have in proxmox now inside has Opencore 0.59 boot loader.. So pay attention on this. In my experience is better to have uploaded a clean and simple working iso you can use only for repair bad things gone wrong, also in my case I have a commented line in VM with opencore/clover working iso that I never modify Usually I boot from EFI in my NVME drive, when things go bad (for osx I mean) I uncomment that line and from OVMF Proxmox bios I choose that iso to boot fine.

hi @Rocket88thank you for your message above for to do list 1) is a common research because OSX misses Qemu Agent so if you shutdown OSX linux will be on I think you can avoid something you used..maybe in your blacklist.conf file to pass "hangs after Ramdisk message" (it could mean you have blacklisted your GPU driver so you need to run VM from another pc/device Only you can verify this When you have time post here benchmark for your system, It could be useful for other users thank you again for posting your experience!