"ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable"

[Dunuin]

Hi,

Recently my syslogs get spammed with ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable. The worst it is on the PVE host itself (Running PVE 7.2 ontop of Debian 11) but I also see it in all my Debian VMs.
And have seen it in other peoples PVE syslogs too.

Someone knows how to fix it or what to look for to narrow it down?

 

[bbgeek17]

I suspect its related to the "tap" or other virtual interface that is created and brought up during VM startup or other other operations. If you look around syslog at the time of the message you should see something like:

May 24 11:49:39 pve7demo1 systemd-udevd[5326]: Using default interface naming scheme 'v247'.
May 24 11:49:39 pve7demo1 systemd-udevd[5326]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
May 24 11:49:39 pve7demo1 kernel: device tap100i0 entered promiscuous mode
May 24 11:49:39 pve7demo1 systemd-udevd[5329]: Using default interface naming scheme 'v247'.
May 24 11:49:39 pve7demo1 systemd-udevd[5329]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
May 24 11:49:39 pve7demo1 systemd-udevd[5329]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
May 24 11:49:39 pve7demo1 systemd-udevd[5326]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.

I believe the message is harmless if annoying.

---

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox

 

[Stoiko Ivanov]

Recently my syslogs get spammed with ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable

on a hunch - could it be that you only recently installed ethtool on that machine?