Test result for 7.0.14-22~bnxt-test1 on Intel (HPE DL360 Gen11, BCM57412, NIC firmware 237.1.141.0):
No Fatal firmware reset event, no TX timeouts and no DMAR faults since boot. On -20 the first crash came 20–25 s after driver init, on every...
Can you try test kernel found here https://forum.proxmox.com/threads/proxmox-ve-9-2-21-bcm57412-bnxt_en-network-failure-after-upgrade-to-kernel-7-0-14-20-pve.186749/post-871933 so far it seems to fix the issue
Over 2 hours in to running today's 7.0.14-22~bnxt-test1, so issues at all so far. I've even done a 5 minute iperf3 in both directions over the bnxt_en adapters, and no issues what so ever.
I would test installing it, maybe quicker than waiting for a reply. It would also be useful to know if 7.0.14-19 works ok for you, to narrow the problem down
Intel Xeon Gold 6248R CPU in a HPE DL360 Gen10
Indeed 7.0.14-22 didn't help, issue happened just after 10 minutes boot time. Still having 7.0.14-19 working fine
I have 6 servers with a BCM57504 (237.1.148.0) which is a quad sfp28 card, firmware is from the latest HPE SSP for the HPE DL360 G10
I upgraded 3 of the servers to `7.0.14-19-pve` on 27th September 2026, and no seen any network issues.
Today I...
See `Can I mix x86-64 and arm64 nodes in one cluster?` in the Q&A section, I assume to get around the different arch problem, you could use Affinity Rules to let VMs only HA between same architecture.
This is awesome news! Just manually installed it on Pi5, and working great, sadly not sure a 8GB Pi is quite enough memory, but was a nice POC.
For those interested: https://fingerlessgloves.me/2026/08/05/installing-proxmox-on-raspberry-pi/