Unstable since proxmox-kernel-6.17 update

[sharanah]

This is a new thread (as suggested), based on: https://forum.proxmox.com/threads/o...le-on-test-no-subscription.173920/post-819343

I've a proxmox cluster of 3 machines, including Ceph (19.2.3) without any subscriptions. The issue only occurs on this specific machine (pashka),

All machines are a from Dell, PowerEdge R340 (1U server). Only the CPU on pashka is different from the other machines. All machines are running 2-6 VMs, without any fancy features (i.e. passthru).

pashka:  Model name: Intel(R) Xeon(R) E-2126G CPU @ 3.30GHz
medovik: Model name: Intel(R) Xeon(R) E-2124 CPU @ 3.30GHz
oladyi:  Model name: Intel(R) Xeon(R) E-2124 CPU @ 3.30GHz

pashka:  Linux pashka 6.17.2-1-pve #1 SMP PREEMPT_DYNAMIC PMX 6.17.2-1 (2025-10-21T11:55Z) x86_64 GNU/Linux
medovik: Linux medovik 6.17.2-1-pve #1 SMP PREEMPT_DYNAMIC PMX 6.17.2-1 (2025-10-21T11:55Z) x86_64 GNU/Linux
oladyi:  Linux oladyi 6.17.2-1-pve #1 SMP PREEMPT_DYNAMIC PMX 6.17.2-1 (2025-10-21T11:55Z) x86_64 GNU/Linux

 

[Stoiko Ivanov]

All machines are a from Dell, PowerEdge R340 (1U server). Only the CPU on pashka is different from the other machines. All machines are running 2-6 VMs, without any fancy features (i.e. passthru).

please check the BIOS settings especially related to SR-IOV and I/OAT DMA - also try disabling intel_iommu via kernel commandline like @t.lamprecht suggested:

Post in thread 'Opt-in Linux 6.17 Kernel for Proxmox VE 9 available on test & no-subscription'

Yesterday at 09:14

The latest kernel update is very unstable on my machine(s) (see attached journalctl.log). The older kernel 6.14.11-4, and 6.14.8-2 don't have this issue.

View attachment 93239

Please open a new thread for this and post more details about your HW, e.g. the server vendor and model.

This might be related to your CPU not implementing VT-d correctly, and, e.g., the newer kernel exposing some feature that was previously not used or just not detected that it was wrong. If you do not rely on PCI pass-through you can try adding disabling the IOMMU, e.g by adding the intel_iommu=off as...

• t.lamprecht

• 

See the known-issues for PVE 9.1 for a bit more information:
https://pve.proxmox.com/wiki/Roadmap#9.1-known-issues

if this does not help - please post the journal with intel_iommu disabled - maybe we get kernel traces with a better pointer to the issue.

I hope this helps!