Hi there,
After updating to PVE version 8 (currently installed version is 8.4.1 with 6.14 kernel), I occasionally have the error that my system is not reachable from one second to the other.
After rebooting, everything seems to work, but the containers start very slow (while it usually takes about 2 minutes to start all of them, it now takes about 10 minutes).
After some investigation (and with the help of a jetkvm), I was able to finally capture some error logs:
So it seems, that the network adapter fails.
In my HP ProDesk 400 G5 bought in October of 2020 I have this network adapter (according to this doc):
LAN: Realtek RTL8111HSH-CG GbE
I then found this thread on the forum:
Looks like I'm not the only one having this issue after updating to pve 8.
I checked drivers used for this network card and indeed this is the output:
The issue now is, that after applying the fix mentioned in this thread, the device is not reachable at all trough the network.
After removing it again and rebooting, I can reach the device again.
In the comments of the linked medium article someone has the same issue, but no answer for it.
Can you guys help me to fix this issue? With PVE 7, the networking was rock solid, without any of these issues. Thanks!
For reference, these are the current version installed on my system:
After updating to PVE version 8 (currently installed version is 8.4.1 with 6.14 kernel), I occasionally have the error that my system is not reachable from one second to the other.
After rebooting, everything seems to work, but the containers start very slow (while it usually takes about 2 minutes to start all of them, it now takes about 10 minutes).
After some investigation (and with the help of a jetkvm), I was able to finally capture some error logs:
Code:
NETDEV WATCHDOG: enp1s0 (r8169): transmit queue 0 timed out
So it seems, that the network adapter fails.
In my HP ProDesk 400 G5 bought in October of 2020 I have this network adapter (according to this doc):
LAN: Realtek RTL8111HSH-CG GbE
I then found this thread on the forum:
Hi,
If after an upgrade from 7 to 8, or a fresh install of your interface seem to die randomly (minutes to hours), and only indication you see in your syslog is:
possibly you've got a Realtek network interface that seem to be affected by this bug.
Backdrop:
At least for me it seem that something has changed in 6.2.16-12-pve from previous versions and driver r8169 seem to be flaky. Before upgrade, I've never even bothered to check which driver those were using - because everything was rock solid. However I've spent two days...
If after an upgrade from 7 to 8, or a fresh install of your interface seem to die randomly (minutes to hours), and only indication you see in your syslog is:
Code:
NETDEV WATCHDOG: enp1s0 (r8169): transmit queue 0 timed out
Backdrop:
At least for me it seem that something has changed in 6.2.16-12-pve from previous versions and driver r8169 seem to be flaky. Before upgrade, I've never even bothered to check which driver those were using - because everything was rock solid. However I've spent two days...
- tomtom13
- Replies: 8
- Forum: Proxmox VE: Installation and configuration
Looks like I'm not the only one having this issue after updating to pve 8.
I checked drivers used for this network card and indeed this is the output:
Code:
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
Subsystem: Hewlett-Packard Company RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet Controller [103c:859c]
Kernel driver in use: r8169
Kernel modules: r8169
The issue now is, that after applying the fix mentioned in this thread, the device is not reachable at all trough the network.
After removing it again and rebooting, I can reach the device again.
In the comments of the linked medium article someone has the same issue, but no answer for it.
Can you guys help me to fix this issue? With PVE 7, the networking was rock solid, without any of these issues. Thanks!
For reference, these are the current version installed on my system:
Code:
proxmox-ve: 8.4.0 (running kernel: 6.14.5-1-bpo12-pve)
pve-manager: 8.4.1 (running version: 8.4.1/2a5fa54a8503f96d)
proxmox-kernel-helper: 8.1.1
proxmox-kernel-6.14.5-1-bpo12-pve-signed: 6.14.5-1~bpo12+1
proxmox-kernel-6.14: 6.14.5-1~bpo12+1
proxmox-kernel-6.14.0-2-pve-signed: 6.14.0-2
proxmox-kernel-6.11.11-2-pve-signed: 6.11.11-2
proxmox-kernel-6.11: 6.11.11-2
proxmox-kernel-6.8.12-11-pve-signed: 6.8.12-11
proxmox-kernel-6.8: 6.8.12-11
ceph-fuse: 17.2.8-pve2
corosync: 3.1.9-pve1
criu: 3.17.1-2+deb12u1
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx11
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-5
libknet1: 1.30-pve2
libproxmox-acme-perl: 1.6.0
libproxmox-backup-qemu0: 1.5.1
libproxmox-rs-perl: 0.3.5
libpve-access-control: 8.2.2
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.1.0
libpve-cluster-perl: 8.1.0
libpve-common-perl: 8.3.1
libpve-guest-common-perl: 5.2.2
libpve-http-server-perl: 5.2.2
libpve-network-perl: 0.11.2
libpve-rs-perl: 0.9.4
libpve-storage-perl: 8.3.6
libspice-server1: 0.15.1-1
lvm2: 2.03.16-2
lxc-pve: 6.0.0-1
lxcfs: 6.0.0-pve2
novnc-pve: 1.6.0-2
proxmox-backup-client: 3.4.1-1
proxmox-backup-file-restore: 3.4.1-1
proxmox-firewall: 0.7.1
proxmox-kernel-helper: 8.1.1
proxmox-mail-forward: 0.3.2
proxmox-mini-journalreader: 1.4.0
proxmox-widget-toolkit: 4.3.11
pve-cluster: 8.1.0
pve-container: 5.2.6
pve-docs: 8.4.0
pve-edk2-firmware: 4.2025.02-3
pve-esxi-import-tools: 0.7.4
pve-firewall: 5.1.1
pve-firmware: 3.15-4
pve-ha-manager: 4.0.7
pve-i18n: 3.4.4
pve-qemu-kvm: 9.2.0-5
pve-xtermjs: 5.5.0-2
qemu-server: 8.3.12
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.7-pve2
Last edited: