No, as said above, I wish I would have gotten this instead of the ASROCK Rack B450D4U-V1LQ5 .
Asking because you are talking about Intel CPU's
That's because most of my Experience on Proxmox VE has been on Intel Systems. Xeon E5 v1/v2 (soon v4), Xeon E3 v3/v5/v6.
On an AMD Ryzen based ASUS ROG STRIX B550-A GAMING I get this, where USB3, Ethernet and SATA (plus 2 other PCIe Slots where the Hailo 8L PCIe Accelerator are installed) are in the same IOMMU Group 13:
Code:
Group 0: [1022:1482] 00:01.0 Host bridge Starship/Matisse PCIe Dummy Host Bridge
Group 1: [1022:1483] [R] 00:01.2 PCI bridge Starship/Matisse GPP Bridge
Group 2: [1022:1482] 00:02.0 Host bridge Starship/Matisse PCIe Dummy Host Bridge
Group 3: [1022:1482] 00:03.0 Host bridge Starship/Matisse PCIe Dummy Host Bridge
Group 4: [1022:1483] [R] 00:03.1 PCI bridge Starship/Matisse GPP Bridge
Group 5: [1022:1482] 00:04.0 Host bridge Starship/Matisse PCIe Dummy Host Bridge
Group 6: [1022:1482] 00:05.0 Host bridge Starship/Matisse PCIe Dummy Host Bridge
Group 7: [1022:1482] 00:07.0 Host bridge Starship/Matisse PCIe Dummy Host Bridge
Group 8: [1022:1484] [R] 00:07.1 PCI bridge Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
Group 9: [1022:1482] 00:08.0 Host bridge Starship/Matisse PCIe Dummy Host Bridge
Group 10: [1022:1484] [R] 00:08.1 PCI bridge Starship/Matisse Internal PCIe GPP Bridge 0 to bus[E:B]
Group 11: [1022:790b] 00:14.0 SMBus FCH SMBus Controller
[1022:790e] 00:14.3 ISA bridge FCH LPC Bridge
Group 12: [1022:1440] 00:18.0 Host bridge Matisse/Vermeer Data Fabric: Device 18h; Function 0
[1022:1441] 00:18.1 Host bridge Matisse/Vermeer Data Fabric: Device 18h; Function 1
[1022:1442] 00:18.2 Host bridge Matisse/Vermeer Data Fabric: Device 18h; Function 2
[1022:1443] 00:18.3 Host bridge Matisse/Vermeer Data Fabric: Device 18h; Function 3
[1022:1444] 00:18.4 Host bridge Matisse/Vermeer Data Fabric: Device 18h; Function 4
[1022:1445] 00:18.5 Host bridge Matisse/Vermeer Data Fabric: Device 18h; Function 5
[1022:1446] 00:18.6 Host bridge Matisse/Vermeer Data Fabric: Device 18h; Function 6
[1022:1447] 00:18.7 Host bridge Matisse/Vermeer Data Fabric: Device 18h; Function 7
Group 13: [1022:43ee] [R] 01:00.0 USB controller 500 Series Chipset USB 3.1 XHCI Controller
USB: [05e3:0608] Bus 001 Device 003 Genesys Logic, Inc. Hub
USB: [0b05:1939] Bus 001 Device 002 ASUSTek Computer, Inc. AURA LED Controller
USB: [1d6b:0002] Bus 001 Device 001 Linux Foundation 2.0 root hub
USB: [1d6b:0003] Bus 002 Device 001 Linux Foundation 3.0 root hub
[1022:43eb] 01:00.1 SATA controller 500 Series Chipset SATA Controller
[1022:43e9] 01:00.2 PCI bridge 500 Series Chipset Switch Upstream Port
[1022:43ea] [R] 02:00.0 PCI bridge Device 43ea
[1022:43ea] 02:01.0 PCI bridge Device 43ea
[1022:43ea] 02:02.0 PCI bridge Device 43ea
[1022:43ea] 02:03.0 PCI bridge Device 43ea
[1022:43ea] 02:08.0 PCI bridge Device 43ea
[1022:43ea] 02:09.0 PCI bridge Device 43ea
[1e60:2864] [R] 05:00.0 Co-processor Hailo-8 AI Processor
[1e60:2864] [R] 06:00.0 Co-processor Hailo-8 AI Processor
[8086:15f3] [R] 08:00.0 Ethernet controller Ethernet Controller I225-V
Group 14: [1002:1478] [R] 09:00.0 PCI bridge Navi 10 XL Upstream Port of PCI Express Switch
Group 15: [1002:1479] [R] 0a:00.0 PCI bridge Navi 10 XL Downstream Port of PCI Express Switch
Group 16: [1002:73ff] [R] 0b:00.0 VGA compatible controller Navi 23 [Radeon RX 6600/6600 XT/6600M]
Group 17: [1002:ab28] 0b:00.1 Audio device Navi 21/23 HDMI/DP Audio Controller
Group 18: [1022:148a] [R] 0c:00.0 Non-Essential Instrumentation [1300] Starship/Matisse PCIe Dummy Function
Group 19: [1022:1485] [R] 0d:00.0 Non-Essential Instrumentation [1300] Starship/Matisse Reserved SPP
Group 20: [1022:1486] [R] 0d:00.1 Encryption controller Starship/Matisse Cryptographic Coprocessor PSPCPP
Group 21: [1022:149c] [R] 0d:00.3 USB controller Matisse USB 3.0 Host Controller
USB: [1d6b:0002] Bus 003 Device 001 Linux Foundation 2.0 root hub
USB: [1d6b:0003] Bus 004 Device 001 Linux Foundation 3.0 root hub
Note that I am NOT right now using
pcie_acs_override=downstream
(I tried for a while but it did NOT help in my Use Case).
It is also possible that this consumer Motherboard just happens to have a **** PCIe and IOMMU Groups Arrangement

.
Im use PVE ISO installers on different systems(HP Servers from Gen 9 with Intel CPU's, Supermicro Epyc board, Gigabyte AMD Ryzen and Epyc's boards, Intel NUC's, Dell and HP mini desktop PC's...) and never have any issue... But if remember correctly Im start using PVE with version 6.X and never try/use older versions...
Not sure I was on older Versions either.
Anyways, that's like Proxmox VE Developers saying they rigorously test their Images & Updates and it's very Rare People have Issues. Maybe 0.1% or so of People have Issues according to them.
So what ? That's like saying that Airplanes are the safest Transportation Method (well, maybe not in the US anymore right now). Does it really matter when YOU are on the Plane that is falling

?
Ever since I had to do that workaround because their stupid Installer couldn't cope with 16MB of VRAM or whatever the Issue was, I first installed Debian and the Proxmox VE on top of it and never looked back.
I don't know what you do wrong on your system
Sure, it's me doing something wrong on my System

. I'm 100% the ONLY ONE with Issues. If you looked at Proxmox VE Forums you'd see that there are a lot (in absolute Terms, NOT in Percentage) of People affected by some of their Kernel Updates.Systems that once Rock Solid start to reboot at random.
It kinda pisses me off that People start Questioning what I'm doing wrong and why I'm going through all these "Hacks" when the System just works. Well, if the System would just work plug & play, *maybe*, just *maybe*, then I wouldn't lose so much Effort and Time for nothing. It's NOT like I'm having fun ! Sure, I learned many Things, but I wish I didn't need to invest so much Time

.
but for me work on MC12 board with Ryzen 5600 CPU... I dont remember what I need enable in BIOS to get it work... But probably everything about IOMMU and ACS need to be enabled...
Not sure I have an Option in BIOS for that. On the ***** ASROCK RACK B450D4U-V1LQ5 the BIOS almost has no Options at all, like even enabling ECC on Ryzen 5700X required a "Hack" / BIOS Mod ...
I don't get any kernel errors or crashes...
Usually if it works it works, and if it doesn't work, from my Experience, you find out within a few Seconds of GRUB Menu ... I also have Systems that are up since a long Time (and only Rebooted to update Kernel etc).
I can and I'm passtrough ONLY SATA Controller to VM(TrueNAS Core):
View attachment 43725
As you can see I have SATA, USB, I210 devices seperated in own IOMMU groups and can passtrouh them seperate to VM's ...
That's NOT the case on the ASUS (Consumer) System I tested it on. I have two other AMD Ryzen Systems on Consumer Motherboards, I didn't try those.
Plus these ASROCK Rack B450D4U-V1LQ5 but I don't recall anything about ACS in the BIOS.
EDIT 1: actually checking the disassembled BIOS, the ASROCK Rack B450D4U-V1LQ5 has an ACS Setting in the BIOS (which requires an AER Setting to be enabled). I think it's however hidden, so again some "Hack" / BIOS Mode is probably required.