Search results for query: e1000e

Sorry for the delay.... here is the second bout of error messages - looks the same to me: Oct 15 05:39:44 proxmox kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang: TDH <ee> TDT...

I have exactly the same issue. It's probably not related to E1000e known issue. pfSense VM start freezing during backup with PBS. Stop and start of the VM is required to recover. qm config <ID>: agent: 0 boot: order=ide2;scsi0 cores: 1 cpu: x86-64-v2-AES ide2: none,media=cdrom memory: 1024...

Hi! Um welches Netzwerkinterface handelt es sich? Wenn der Intel e1000e-Treiber verwendet wird, hilft womöglich die Information in [0]? Wenn die Fehlermeldungen direkt auf den Terminal tty0 gehen, könntest du einen anderen Terminal verwenden. Normalerweise wird stdout nicht als stdin...

I'm happy to report that switching every VM to use an e1000e nic has resolved 100% of the problems. I no longer experience hardware hangs, or iperf3 failures on extended runs. Admittedly my data points are still rather limited (only two 10 hour runs succeeded with the e1000e nics on the...

...iterations/installs and narrowed the process to above. Adding virtIO nic (just add, no config and doesn't matter if it it VirtIO, E1000, E1000E, RTL8139...) fails whole network on this VM only. Other VMs that are on this bridge(vmbr0) work perfectly fine! Also, I have 2 other nics (pci slot)...

...iterations/installs and narrowed the process to above. Adding virtIO nic (just add, no config and doesn't matter if it it VirtIO, E1000, E1000E, RTL8139...) fails whole network on this VM only. Other VMs that are on this bridge(vmbr0) work perfectly fine! Also, I have 2 other nics (pci slot)...

After switching the network hardware for the VM to e1000e, it can complete an extended iperf3 session Here's what I had to do for the windows VM: Going to fire up another test of the windows VM to the same iperf3 server to ensure stability. It seems I always had the most issues using the...

...cannot pass an extended iperf3 test yet with the virtio nic. It always fails right towards the end with the message: I'll try again with an e1000e nic specified. The UBUNTU vm never experiences a problem, and neither does the proxmox host. The problem could be something else, but I have...

does your server has an intel e1000e nic ? If so have you tried to disable offloading ?

...in the logs every 2 seconds until I rebooted the machine. # journalctl -b -1 -kg "hardware unit hang|e1000" Oct 13 07:03:13 proxmox kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang: TDH <7b> TDT...

...the proxmox server, a different server in the network) iperf3: error - select failed: Bad file descriptor So far this has solved the issue for the most part. I'll keep trying to see if VirtIO can pass a 10+ hour iperf3 test. I might be sticking to e1000e nic assignments in proxmox, we'll see.

Might running an iperf3 on PVE itself concurrently with VM(s) be a good test? This would cover the client VMs running network traffic concurrently with for instance running backups of clients on the host. Also, running iperf3 in both directions? (I ran into this also quite suddenly earlier this...

Just to update you guys. Ubuntu VM with an e1000e nic successfully ran IPerf3 for 10 hours at gigabit speeds with 0 retransmissions and no crashing. Windows 10 VM with a VirtIO nic has been running IPerf3 for 8 hours at gigabit speeds. No stats until it's done. After this VM finishes up...

...similar, and I'm going to test it again. I'm now testing: auto lo iface lo inet loopback iface eno1 inet manual # Disable offloads for e1000e driver issues # post-up /sbin/ethtool -K eno1 tso off gso off gro off post-up ethtool -K eno1 tso off auto vmbr0 iface vmbr0 inet...

That is a very good question, and my testing so far indicates the wisdom that led me to consider this is backwards. Assigning the VM to use an e1000e nic made all the problems go away for me. I'll do further testing later. But using the VirtIO option seems to me to be what was causing the...

...(6) I219-V (rev 30) Subsystem: Intel Corporation Ethernet Connection (6) I219-V I assume, therefore, that I am going to join the club of e1000e driver hangs, which doesn't fill me with joy (the NIC has been 100% stable running bare metal for the last 6 years). My question: can I avoid...

...what to think of this. This occurs almost instantly when running a windows VM & IPERF3 with a VirtIO "NIC" Oct 07 22:41:41 proxmox kernel: e1000e 0000:00:1f.6 eno1: Detected Hardware Unit Hang: TDH <e3> TDT...

Danke für den Log-Auszug. Die Meldung probe with driver e1000e failed with error -2 bestätigt, dass der Treiber im neuen Kernel die Netzwerkkarte nicht initialisieren kann, weil sie sich vermutlich in einem undefinierten Zustand befindet. Das ist ein klassisches Symptom bei solchen...

Hallo @Malz1902, dein Problem deutet stark auf das bekannte Problem mit dem Intel e1000e Treiber hin, wie von @jim_os bereits mehrfach erwähnt. Die Lösung, welche auch für @Josch und @marinko9999 funktioniert hat, ist das Deaktivieren von Offloading-Funktionen der Netzwerkkarte. Du kannst das...

Also das kam dabei raus, ... root@m90n-i7:~# journalctl -b -1 | grep e1000e Oct 02 20:31:34 m90n-i7 kernel: e1000e: Intel(R) PRO/1000 Network Driver Oct 02 20:31:34 m90n-i7 kernel: e1000e: Copyright(c) 1999 - 2015 Intel Corporation. Oct 02 20:31:34 m90n-i7 kernel: e1000e 0000:00:1f.6: Interrupt...