Recent content by athurdent

Try this: https://forum.proxmox.com/threads/proxmox-ve-8-0-released.129320/page-6#post-567264 Solved it for me and I obviously did also not read the release notes thoroughly. Sorry for the noise.

Any idea why my network won't start after updating from 7.4? I can disable networking and bring it up manually fine root@epyc:~# ifconfig enp6s0f0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 ether 40:a6:b7:55:f9:54 txqueuelen 1000 (Ethernet) RX packets 14607 bytes...

Hi, I simply used this one: https://www.intel.com/content/www/us/en/download/18159/intel-network-adapter-linux-virtual-function-driver-for-intel-ethernet-controller-700-and-e810-series.html Compiled it as stated in the readme, and my 22.04 LTS systems were stable again immediately. No problems...

I still have one unpatched test VM I can reproduce the error with by simply running OOKLA‘s CLI speedtest. Tried with the 22.04 HWE kernel, no luck there. If you still want to look into what seems to be an Ubuntu problem, I can keep that VM without the Intel driver and run tests. Just let me...

Thank you very much for looking into this! Attached a few more crashes. Always refcount -1 it seems. I have now also upgraded the Intel card's firmware, which did not help. qemu upgrades would have been from Proxmox, so it seems there were none. Ubuntu upgrades correlate: Start-Date...

Also tried with kernel 5.19 now, same problems.

System is a M11SDV-8C-LN4F with an X710-DA2 (SR-IOV used). System has been working fine for over a year now. Also working fine is the base OS (Debian Bullseye), no kernel errors logged and no problems with heavy harddisk or network I/O, e.g. when backing up VMs to a NAS. An OPNsense VM is also...

Awesome, thank you very much!

Thanks, will try to figure out the kernel source then. As an alternate approach, would it be a problem to simply install the Intel drivers manually, or does PVE conflict with those? Any custom Intel driver mods in Proxmox kernels maybe?

Thanks! I was under the impression that this is a code generated when building the driver, to determine if there were changes in code between versions. Any idea how to correlate that output into a version listed e.g. here in table 2?

Thank you very much for looking into this, but that seems to only show the kernel version, too? # modinfo i40e filename: /lib/modules/5.15.60-2-pve/kernel/drivers/net/ethernet/intel/i40e/i40e.ko license: GPL v2 description: Intel(R) Ethernet Connection XL710 Network Driver...

I'd like to match the NVM firmware of a X710-DA2 to the driver used in PVE, but it seems the version string used is the Linux kernel version and not the Intel driver version. Where would I find the actual Intel i40e driver version used in PVE? # ethtool -i enp6s0f0 driver: i40e version...

Is there any way to get the actual Intel driver version Proxmox uses? For all of my cards I only get the Proxmox version... # ethtool -i enp2s0f0 driver: ixgbe version: 5.11.22-4-pve firmware-version: 0x800006da, 1.1824.0