Leaderboard

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

beh allora ti assicuro che avrai un sacco di cose con cui divertirti 😁

Il secondo monitor già non compare più, e la scheda madre ha solo una uscita quindi ora funziona tutto

however seems weird that skipped because values are pretty the same if I see well

check if your mmio are changed..if not it is fine 😛

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

It shouldnt change if you not change bios parameters like CSM/UEFI or 4g on/off if you have in BIOS however check always your debug log, if you see some skip to 0 when before you have had them to 1 , it means value of that MMIO is changed and you have to recalculate its value

if you check @Ploddlesssdt.aml you will see if inside there are the same your location or in the worst case they are not identical you have to manage them according your ioreg I do not know if @Ploddlesis able to modify it for you..I am not able to do I >Know for sure @iGPUand @Gengik84 are able to do... try to ask them if they have some time to do this for you 🙂

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

11:312 00:001 OCABC: MMIO devirt 0xEF100000 (0x181 pages, 0x8000000000000001) skip 0 NO please..let decide how to start your system (bios setting , and card in slot on it) then put here a config which boots then we will try again 🙂 last chance for you if things will change again (for my help I mean) 🙂

check this and latest you have posted 0xEF1 is not here so what does it means? you have changed something in BIOS o in your pci slot position... and in this way it is not possible to help sorry ;(

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)

which config are you using? your debug posted is different from what we have done yesterday check well first you have to solve your black screen (randomly happen so I thing is not config.plist related) then you can optimize your ACPI could differ from mine or from other users also with the same your motherboard So, SSDT from others have to be tuned with your system usually you have to start with a clean system and save from it an IOREG then skilled people could help to produce correct SSDT for your system

also previous debug is weird compared from the job we did yesterday you do not have to mix different MMIO from different motherboard or user bios config from this result you have to start

@infodo not panic..you not OS I mean 🙂 in my latest config you have proper MMIO list calculated for you by me reading your log If you change bios parameter MMIO list could change (parameter like CSM/UEFI or 4G if you have) Have you tested with another cable? have you tested with a HDMI/DP adaptor if you do not have another Monitor to test? Monitor I see in your video seems pretty old.. in this latest your debug all MMIO are skipped to 0 not good for future full functionality of your system (Shutdown/Sleep wake and so on)

I think it is a cable or monitor problem..but from here I can't say more now you have a pretty basic configured system, you can try to run some benchmark aqs Cinebench 15 and cinebench23 also luxmark3.1 give a great stress test on gpu then..you can try to add stuff you need (wifi? ethernet kext for your Gigabyte and so on...

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

ah maybe I have understood.. I am waiting for your latest try

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?

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

config.plist.zip in this you have your Exact MMIO test they are pretty similar pay attention if you change on your BIOS, Uefi or CSM they could change so test always with the same bios settings post always open core txt debug log

It is weird in my opinion how it is possible our motherboard act in so different ways in my case vfio.conf it is not usefull at all maybe it is about Agesa difference in our mb? Or for what? i have tested also old agesa but for me vfio.conf it is not important at all. @iGPU about pci bridge maybe we could find a way to ask on proxmox forum how qemu pci bridge virtual device interact wth real pci bridge and if they interact how to Add on that file missing ones

@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

I would like suggest to all of you to try do run an ACPIDUMP in this way: download acpidump.efi and put in OC/tools (thanks @Gengik84for this) https://www.macos86.it/topic/1560-acpi-come-estrarle/?tab=comments#comment-40152 https://www.macos86.it/applications/core/interface/file/attachment.php?id=6306 Boot directly with your OSX disk (with opencore EFI and not via Linux) in my case my NVME Sabrent obviously you can access only to opencore shell try to reach your EFI folder (in my case FS1:/EFI/OC/Tools and then run: acpidump.efi boot in your system and mount your EFI backup this data then start proxmox and do the same inside proxmox/OSX/opencore you will see how VM interact with our original ACPI... Maybe some of you have the skills to understand better than me and use it to improve our VM 😉

@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...

@Driftwood I don't understand well..but you can ask to all people you desire..I am happy for this (Pavo or other who have experience and no preclusion in this proxmox way) Your ethernet problem is a mystery for me..I am not understanding well it..but I am sure that 8125 is not supported in OSX and maybe you need a new Mieze kext to have it fully working there. I think audio is OSX problem, but some workaround are out there (firewire audio as you say, or a well done usb audio with DAC capacity as @iGPU have. But, when I started this "journey" my goal was to have all working has my previous x299 hack 🙂 Internal Audio is no go..and I have to declare here my loss 🙂 🙂 I can only affirm that in OSX Sierra it is a driver problem and I can have a see (bad) internal audio only passing audio has single device and no as entire controller in this way: usb2: host=0c76:161f If I pass entire controller it is not working at all if I have a green speaker connected on backplate audio output. if I start without audio jack connected I have this but only one working perfect is LG (dp audio Nvidia driver related) USB Pnp Audio Device works bad the same in HS..work well in Catalina I have researched a lot on this because is the only thing I miss It is a coreaudiod related problem and also real Macs could have this problems (by the way, Realtek and usb Audio do not need of any AppleALC or voodooHDA kexts

again..audio obsession for me 🙂 (in High Sierra 😉 ) https://www.usb-audio.com/support/

@Driftwood i cant see here how @Pavosolved your problem i think you are the user he said to help on amd discord channel with realtek and audio problem. i would like to have this kind of discussion in public because maybe it is usefull also for others. Just my 2 cents in this subject😁 i do not well understand your ethernet problem, in my case also aquantia card take by default an ipv6 address and i can modify it in installation step configuration according my router configuration..but maybe yours problem is different. Instead solution of scrambling iommu group is pretty simple. our trx40 motherboard had a bunch of bridges with pcie, nvme and so on some slots are shared and changing card position or eliminating / adding a nvme disk could have many of the effects you describe above as personal consideration : best trx40 mb is Gigabyte designare. It has best layout i have ever seen for its slots and a full features including a big thunderbolt value maybe fullfill all nvme slot in it could cause some problems in a proxmox/osx environment but it is the only motherboard i would like to have different of mine Trx40 asrock creator is also fine, in my case not so good because i have 8 sata disk in my rig and it seems it miss 2 sata ports.

again..on audio problem 🙂 installed Catalina 10.15.5 beta 4 USB audio is perfect ALC internal audio is not present at all if I connect my speakers on green output jack if I do not connect and reboot I see Realtek USB 2.0 audio device inbound, but connecting some speakers has no effects In High Sierra no results at all I would like to specify that I can obtain these passing all stuff I can (all usb, audio and so on) in Catalina Same configg in high Sierra no audio to see audio in high Sierra I have to pass as USB device from web interface but audio is problematic... So Catalina has better usb audio /port drivers than highSierra not tested so much in 10.15.4 release..but there I have had similar HS problem ah, as side note in HS I can't see usb 3 device (if I connect also a simple usb pen (3.0) instead usb 2.0 device are well recognised I attach my Catalina 10.15.4 ioreg where I have mapped all my USB ports testing usb2/3 devices for usb audio and internal audio (when this works 😉 ) no need of any additional kext (no AppleAlc, no voodooHDA) fabio’s iMac Pro ioreg cata.ioreg.zip

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..

source

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

for your problem (main problem) have you checked in updated bios if some new voice is there about IOMMU I mean? If you do not have done any error it is the only answer to explore because @99% it is an user errors (some time I miss myself things and I break my head to understand.. FYI I have reverted all mid Debian files to original ones, because for me passing them with FLR patch is not useful to latest my goal on this system ( internal audio 🙂) others task are reached and all controllers are passed well I hope I can find a solution for audio, but I am convinced it is an OSX problem and if you search also many original Mac are affected from this usb audio bug A solution seems to use an Audio with DAC capability or also @iGPUexternal audio I have not tested personally so if people could share experiences in this subject I will more than happy 🙂

searching on the net also real Mac have some problems (not solved for all) USB audio problem this is a partial log when audio starts to fail

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

@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?

@lvtzi would use a smaller drive for proxmox but it is a your choice as advice starts more simple you can and then when you know what are you doing you can go deeper

Hi @lvtz USB controller is integrated on my motherboard and in the main guide I show where I connect my "proxmox" disk. in 1) and 2) question you mix some different subject.. to install Proxmox you have to create an USB Pen (CD/DVD or what you desire) to install it Then you can choose a disk to install Proxmox (proxmox = linux) I have chosen an external USB disk..why? in this way I have all others controller (sata, NVME, and so on to pass to my VM) Best solution is to have your guest OS system in a separate drive from Proxmox disk ie if you have now a working OSX on your system you can use it with only a proper EFI to boot with it.. if you instead install OSX on a file, you can have it on your Proxmox disk..in my opinion it is better to use Proxmox disk only for few things and leave all other OSX separated from it so you need: 1) an USB/CD/DVD for iso installation file 2) boot from this one and from here you have to configure Proxmox (5 minute of your time) 3) in there you choose disk fr proxmox installation (in my case an external disk on back USB) 4) then you can create following the instructions your VM if you have an existing OSX on a separate disk you can try to "pass" that disk..I did for my NVME High Sierra Be prepared to solve different problems..but when you succeed in this task you will be happy 😉

@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

@Driftwood if better results are obtained with a VM file disk..they are not accurate (sorry for this 🙂 ) if instead they are achieved with a passed drive or entire controller...are very good almost impossible but very good @iGPUyou can use multiple gpu (not in crossfire or SLI), software like davinci resolve and other have a great benefit with dual gpu system

ok solved 🙂 root@pve:~# pveversion -v proxmox-ve: 6.2-1 (running kernel: 5.4.34-1-pve) pve-manager: 6.2-4 (running version: 6.2-4/9824574a) pve-kernel-5.4: 6.2-1 pve-kernel-helper: 6.2-1 pve-kernel-5.4.34-1-pve: 5.4.34-2 ceph-fuse: 12.2.11+dfsg1-2.1+b1 corosync: 3.0.3-pve1 criu: 3.11-3 glusterfs-client: 5.5-3 ifupdown: 0.8.35+pve1 ksm-control-daemon: 1.3-1 libjs-extjs: 6.0.1-10 libknet1: 1.15-pve1 libproxmox-acme-perl: 1.0.3 libpve-access-control: 6.1-1 libpve-apiclient-perl: 3.0-3 libpve-common-perl: 6.1-2 libpve-guest-common-perl: 3.0-10 libpve-http-server-perl: 3.0-5 libpve-storage-perl: 6.1-7 libqb0: 1.0.5-1 libspice-server1: 0.14.2-4~pve6+1 lvm2: 2.03.02-pve4 lxc-pve: 4.0.2-1 lxcfs: 4.0.3-pve2 novnc-pve: 1.1.0-1 proxmox-mini-journalreader: 1.1-1 proxmox-widget-toolkit: 2.2-1 pve-cluster: 6.1-8 pve-container: 3.1-5 pve-docs: 6.2-4 pve-edk2-firmware: 2.20200229-1 pve-firewall: 4.1-2 pve-firmware: 3.1-1 pve-ha-manager: 3.0-9 pve-i18n: 2.1-2 pve-qemu-kvm: 5.0.0-2 pve-xtermjs: 4.3.0-1 qemu-server: 6.2-2 smartmontools: 7.1-pve2 spiceterm: 3.1-1 vncterm: 1.6-1 zfsutils-linux: 0.8.3-pve1 root@pve:~# it was simple..a file....kvm.conf 🙂 🙂 🙂 no improvement for our common problem for now I would like also to remark: useful file for my rig to modify after a clean Proxmox VE 6.2 iso: etc/modules vfio vfio_iommu_type1 vfio_pci vfio_virqfd etc/modprobe.d/kvm.conf options kvm ignore_msrs=1 /etc/default/grub.cfg quiet iommu=pt amd_iommu=on then I have used my previous VM.conf file recreating in it only EFI disk

Ok, it is a not new kernel problem related..Probably new QEMU has some conflict with our bootloaders... for now stay away from this or try with a solid backup

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.

@AllubzV take a look and compare with yours (I would like also others TRX40 users put their similar datas to compare) 04:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller [1022:148c] Subsystem: Micro-Star International Co., Ltd. [MSI] Starship USB 3.0 Host Controller [1462:7c60] 23:00.3 USB controller [0c03]: Advanced Micro Devices, Inc. [AMD] Starship USB 3.0 Host Controller [1022:148c] Subsystem: Micro-Star International Co., Ltd. [MSI] Starship USB 3.0 Host Controller [1462:7c60] Kernel driver in use: xhci_hcd 23:00.4 Audio device [0403]: Advanced Micro Devices, Inc. [AMD] Starship/Matisse HD Audio Controller [1022:1487] Subsystem: Micro-Star International Co., Ltd. [MSI] Starship/Matisse HD Audio Controller [1462:cb60] 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 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 And focalise also on Subsystem data (check also your BIOS AGESA, TRX40 ones are not updated to the last patch). Now, as you have seen FLR patch is not perfectly calibrated for TRX40 users and if you follow below link I have inserted on Proxmox forum, Stefan_R (a proxmox forum staff guy) says we have to do some others step because "we are experiment on the joy to use bleeding edge new hardware" 🙂 FLR patch was done some months ago and follow leveltech1 comment in some cases is possible to insert via kernel command (in my case it not was working) @pavo compiled that patch in a kernel (which is not the one suggested by Fabian) and it is available on his GitHub In my case is not working and for some x570 users is working partially So our goal should be how to compile new Kernel you can find in Proxmox git and then to understand if it possible to insert on a kernel line command FLR patch Proxmox Stefan_R advice level1techs FLR patch discussion Proxmox git for latest Kernel As last information I would like to share, I can pass also 23:00.4 as you can see in my above box (it uses vfio-pci kernel )but audio is problematic I can have a working internal audio via matisse audio controller or with a simple usb audio adapter bought to test this problem. Audio works..but it is not perfect (I loose it, some time is scratchy an so on) some time is perfect but usually if I change audio source from ie a video to a mp3 file ..I loose it For this I said before no ready for a professional use Nvidia Dp/hdmi is perfect. My idea is a negative idea in this subject (I hope to be very wrong on this). problem for me is due Audio osx system driver and how it is interact with trx40 CPU. In Proxmox Windows 10 64 bit VM, same linux configuration, internal audio (USB 2.0 Realtek) is perfect As last last ( 🙂 ) information I would like to advice to test audio problem (it is valid also for other problem you can have) to test with a minimal set of passed controllers.. I pass for this task only NVME controllers where I have my OSX disk and then I pass mouse/keyboard as single USB ports. To have proxmox distro installed on an USB disk could be useful to pass fine all your Sata or NVME controllers to OSX (I use back type C port of my motherboard) and doing this I loose possibility to pass my ASMedia USB controller to OSX, but both ports on it are working (simple USB port passthrough)

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!