I confirm a drastic change in behavior on the way VF passthrough is handled by 6.14.8-2-pve and 6.16.0-50-pve kernels when calling VF passthrough. I have made many tests changing kernel parameters but all comes down to the fact that everything...
So the issue seems to be related to the kernel parameter intremap=no_x2apic_optout which cannot be transposed to 6.14.8-2-pve and 6.16.0-50-pve without causing the passthrough to crash the NIC when calling the VF at start of VM. This kernel...
Unfortunately yes. The link points to latest kernel 6.16.0-50-pve. Exact same behavior than with 6.14.8-2-pve
Here is my cmdline :
root=ZFS=rpool/ROOT/pve-1 boot=zfs intel_iommu=on iommu=pt intremap=no_x2apic_optout pci_pt_e820_access=on quiet...
Ok Not sure if this is related but I am having a similar and serious issue since I updated to PMX 9.
I have drilled down the issue to the kernel version.
The issue is definitely present with kernels 6.14.8-2-pve and 6.16.0-50-pve behaving...
just fyi: we're currently looking into this, and believe we have identified a commit (+possible fix) that's responsible, i'll send a patch later if it turns out that it fixes the issue
I'm running Proxmox on 6 home PCs all with PCIE pass-through. This morning I just updated to the latest kernel and other proxmox updates that were released today. All systems were fine except for one older Pre-Ryzen based PC.
The pre-ryzen PC...
Yes exact same issue here once I updated to kernel 6.8.12-12. There definitely is some regression with this kernel version.
Several VM on multiple servers give error message when mounting vfio devices at VM start
kvm: -device...