proxmox-kernel 6.8.4-X, Intel i40e module, and X710 cards -- no networking?

[jjasen]

Out of a fleet of ten servers with Intel X710 cards, I've had ten failures in networking lighting up when upgrading to the 6.8.4-3 kernel.

I tried logging into two and restarting the interfaces, including ifdown/ifup and service networking restart, but still no joy.

The only solution I found is to revert to the 6.5.13-5 kernel.

Anyone else see this?

 

[Deepcuts]

root@proxmox:~# uname -r
6.8.4-3-pve

No such issue with X710 and DAC

 

[jjasen]

A few hints, mining the 8.2 changelog, and comparing ip output between 6.5.x and 6.8.4, it seems my interfaces have collected a npX trailer.

OK, I can fix that one way or another.

 

[bubbleaegis]

hello jjasen, I also noticed that all the networking features do not work with kernel 6.8.4-2 and 6.8.4-3.
i don't think it is not a problem related to the x710 network card...
X722 card also does not work for me. I also have the X710 card

these are my network cards:

inxi -N
Network:
Device-1: Emulex OneConnect NIC driver: be2net
Device-2: Emulex OneConnect NIC driver: be2net
Device-3: Intel Ethernet X722 for 1GbE driver: i40e
Device-4: Intel Ethernet X722 for 1GbE driver: i40e
Device-5: IBM XClarity Controller type: USB driver: cdc_ether

 

[hvisage]

Out of a fleet of ten servers with Intel X710 cards, I've had ten failures in networking lighting up when upgrading to the 6.8.4-3 kernel.

I tried logging into two and restarting the interfaces, including ifdown/ifup and service networking restart, but still no joy.

The only solution I found is to revert to the 6.5.13-5 kernel.

Anyone else see this?

RTFM the 8.2 Release notes, and then use this https://github.com/D4M4EVER/Proxmox_Preserve_Network_Names from https://www.reddit.com/r/Proxmox/comments/1cd1quu/proxmox_ve_82_proxmox_backup_server_32_breaking/

 

[bubbleaegis]

RTFM the 8.2 Release notes, and then use this https://github.com/D4M4EVER/Proxmox_Preserve_Network_Names from https://www.reddit.com/r/Proxmox/comments/1cd1quu/proxmox_ve_82_proxmox_backup_server_32_breaking/

have you tried it? does it work? @jjasen. How come this change?

 

[bubbleaegis]

I solved it this way:

inxi -n

I took note of the new network interfaces nomenclature and then changed the references inside:

nano /etc/network/interfaces

Rebooted everything and now it seems to work.

 

[hvisage]

have you tried it? does it work? @jjasen. How come this change?

I have used it on just about all my PVE & PBS going to PVE 8.2 & PBS 3.2 as just about all of them had the Intel interfaces that have that virtual function causing the "change" that the System(&@#$(%&@#$%&(D implements

I have loads of )&#@$(%)&@#$)%(& words for SystemD, as the correct way for them, *should* have been to take a Solaris leave and make those "fixed" on first detection, but that would be common sense in a server world that old SysAdmins like me prefer. So the consequence is this change in the enumeration from the kernel side, and systemD not persisting it on first configuration.

 

[bubbleaegis]

I have used it on just about all my PVE & PBS going to PVE 8.2 & PBS 3.2 as just about all of them had the Intel interfaces that have that virtual function causing the "change" that the System(&@#$(%&@#$%&(D implements

I have loads of )&#@$(%)&@#$)%(& words for SystemD, as the correct way for them, *should* have been to take a Solaris leave and make those "fixed" on first detection, but that would be common sense in a server world that old SysAdmins like me prefer. So the consequence is this change in the enumeration from the kernel side, and systemD not persisting it on first configuration.

SystemD sometimes I feel like I live in a real living joke.

 

[jjasen]

have you tried it? does it work? @jjasen. How come this change?

From a glance, changes in the i40e kernel module to more expose virtual functions. Since my 710 and your 722 use that module, presto -- we get new device names.

I generally agree on systemd being a pain in the neck, with a variance of 2-3 ft (75-90 centimeters approximately, for non-US folks).

 

[bubbleaegis]

I would like to make a point. At this time I am upgrading all my PVE servers. I am observing that in servers where previously the original installation was PVE 7 and later upgraded to PVE 8 I have this problem with the latest kernel update. In the servers where I installed PVE 8 from the beginning I am not experiencing this problem that Intel interfaces are being renamed.