e1000e eno1: Detected Hardware Unit Hang:

[Dragsting]

Same errors here.
I see that proxmox has had problems with Intel NIC for many years.
What card should I buy for this to work properly?
Or maybe that's just the way proxmox is?

 

[spirit]

Same errors here.
I see that proxmox has had problems with Intel NIC for many years.
What card should I buy for this to work properly?
Or maybe that's just the way proxmox is?

I219-V,I218-V chipet drivers are shitty, not only on proxmox, same on xcp-ng for example
https://xcp-ng.org/docs/networking.html#intel-i218-i219-slow-speed

personnaly I'm using mellanox connect-x in production without any problem.

 

[tosick]

ethtool -K eth0 tx off rx off

Disabling TCP checksum offloading worked for me

Great! It helped! Thanks a lot!

 

[ZipsServer]

Also wanted to give a big thank you for

ethtool -K eth0 tx off rx off

Disabling TCP checksum offloading worked for me

This seems to have solved the hardware hangups and DRASTICALLY improved the network latency for the webapps I am running.

 

[jsabater]

Great! It helped! Thanks a lot!

I presume that you executed the command in the PVE node, not inside the VM, correct? Moreover, what other guests did you have in the node? I have a mix of VMs and LXCs and this behaviour only happens where I have VMs. Would that be your case, too?

 

[4u2fast]

Facing same issues after recent updates on 3 computes and different HW ! seems like something changed after update... system was stable for years before!

 

[fabian]

see https://bugzilla.proxmox.com/show_bug.cgi?id=6273 - seems like there might have been a regression there

 

[jsabater]

Hi, Fabian. Thanks for the link to the bug tracker. I have contributed to it. I hope it can be solved soon.

 

[leiwang15]

I am also having this problem, disable offloading is one way to solve it. Another solution is to modify your VM's network card model to Intel E1000E instead of VirtIO.
I was also able to reliably reproduce the problem with iperf3 client running inside the VM. (The following command might hang your host)
iperf3 -c <IPERF_SERVER> -M 100 -t 50

 

[jsabater]

I am also having this problem, disable offloading is one way to solve it. Another solution is to modify your VM's network card model to Intel E1000E instead of VirtIO.
I was also able to reliably reproduce the problem with iperf3 client running inside the VM. (The following command might hang your host)
iperf3 -c <IPERF_SERVER> -M 100 -t 50

Thanks a lot for your report, @leiwang15 . Much appreciated.

Incidentally, I found this thread on these forums regarding E1000E vs VirtIO on Proxmox.

 

[crypt0rr]

Fixed this issue on my Proxmox host (currently v8.3.5). Posted here: https://gist.github.com/crypt0rr/60aaabd4a5c29a256b4f276122765237

 

[jellyfish_jessie3]

similar thread (link to my reply which might be useful to folks here): https://forum.proxmox.com/threads/e1000-driver-hang.58284/post-760975

 

[2GOOD]

I am also having this problem, disable offloading is one way to solve it. Another solution is to modify your VM's network card model to Intel E1000E instead of VirtIO.
I was also able to reliably reproduce the problem with iperf3 client running inside the VM. (The following command might hang your host)
iperf3 -c <IPERF_SERVER> -M 100 -t 50

I've changed the VM's NICs to e1000e on 6.8.12-9-pve I219-LM. I'll post the results later.
Also keeping track of this bug report https://bugzilla.proxmox.com/show_bug.cgi?id=6273

Edit:

iperf3 -c <IPERF_SERVER> -M 100 -t 50

from within the VM also from the host - without an issue so far, offloads with default settings [on]

Edit 2:
hang again - using e1000e in the VMs is not fixing the problem!

 

[jsabater]

hang again - using e1000e in the VMs is not fixing the problem!

Thanks for reporting this. Good to know!