I'm seeing a ghost "eth0" interface spamming my console logs on proxmox latest. Not sure if this issue is caused by a BIOS firmware update I carried out on this new device (Minisforum MS-01)... hopefully someone can help? eth0 doesn't exist on my system as you can see below. I'm not sure what I am missing.
dmesg "eth0" complaints
Let's look for "eth0"... it's not there.
root@MS1:~# ip link show eth0
Device "eth0" does not exist.
root@MS1:~# brctl show
bridge name bridge id STP enabled interfaces
INFRA 8000.de39214504a9 no ln_INFRA
P2P 8000.ba2458602957 no ln_P2P
UNTRUST 8000.327a5aa7a72d no ln_UNTRUST
fwbr111i0 8000.a6b9c2a3f77b no fwln111i0
veth111i0
fwbr117i0 8000.7a512c37ef9f no fwln117i0
veth117i0
vmbr0 8000.5847ca7759b2 no enp2s0f0np0
fwpr111p0
fwpr117p0
tap101i0
tap103i0
tap104i0
tap105i0
tap119i0
veth110i0
veth114i0
veth118i0
veth125i0
veth126i0
vmbr0v20 8000.5847ca7759b2 no enp2s0f0np0.20
pr_UNTRUST
vmbr0v30 8000.5847ca7759b2 no enp2s0f0np0.30
pr_P2P
vmbr0v70 8000.5847ca7759b2 no enp2s0f0np0.70
pr_INFRA
root@MS1:~#
[/CODE]
Kernel and driver view
/etc/network/interfaces
Software running on the box
The firmware on the NICs is up to date.
Any idea where this eth0 ghost is coming from and why my dmesg is being spammed by it if the interface "eth0" is nowhere on the system it seems? The hardware is https://store.minisforum.com/products/minisforum-ms-01 and they gave me a BIOS update to install, once I installed that BIOS update I noticed system instability and this ghost interface. I have already flashed back an older bios but the instability and log entries are still there.
Not sure what else to debug for this ghost interface.
dmesg "eth0" complaints
Code:
[ 4268.589196] eth0: entered promiscuous mode
[ 4270.532391] eth0: left promiscuous mode
[ 4330.733460] eth0: entered promiscuous mode
[ 4332.667188] eth0: left promiscuous mode
[ 4392.825174] eth0: entered promiscuous mode
[ 4394.770565] eth0: left promiscuous mode
[ 4454.941523] eth0: entered promiscuous mode
[ 4456.876004] eth0: left promiscuous mode
[ 4517.049452] eth0: entered promiscuous mode
[ 4518.983500] eth0: left promiscuous mode
[ 4579.869428] eth0: entered promiscuous mode
[ 4581.805875] eth0: left promiscuous mode
[ 4641.954756] eth0: entered promiscuous mode
[ 4643.912156] eth0: left promiscuous mode
[ 4704.074369] eth0: entered promiscuous mode
[ 4706.020271] eth0: left promiscuous mode
[ 4766.186591] eth0: entered promiscuous mode
[ 4768.121299] eth0: left promiscuous mode
[ 4828.274429] eth0: entered promiscuous mode
[ 4830.225876] eth0: left promiscuous modeLet's look for "eth0"... it's not there.
root@MS1:~# ip link show eth0
Device "eth0" does not exist.
root@MS1:~# brctl show
bridge name bridge id STP enabled interfaces
INFRA 8000.de39214504a9 no ln_INFRA
P2P 8000.ba2458602957 no ln_P2P
UNTRUST 8000.327a5aa7a72d no ln_UNTRUST
fwbr111i0 8000.a6b9c2a3f77b no fwln111i0
veth111i0
fwbr117i0 8000.7a512c37ef9f no fwln117i0
veth117i0
vmbr0 8000.5847ca7759b2 no enp2s0f0np0
fwpr111p0
fwpr117p0
tap101i0
tap103i0
tap104i0
tap105i0
tap119i0
veth110i0
veth114i0
veth118i0
veth125i0
veth126i0
vmbr0v20 8000.5847ca7759b2 no enp2s0f0np0.20
pr_UNTRUST
vmbr0v30 8000.5847ca7759b2 no enp2s0f0np0.30
pr_P2P
vmbr0v70 8000.5847ca7759b2 no enp2s0f0np0.70
pr_INFRA
root@MS1:~#
[/CODE]
Kernel and driver view
Code:
02:00.0 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 02)
Subsystem: Intel Corporation Ethernet Converged Network Adapter X710
Flags: bus master, fast devsel, latency 0, IRQ 16, IOMMU group 13
Memory at 611d000000 (64-bit, prefetchable) [size=8M]
Memory at 611e008000 (64-bit, prefetchable) [size=32K]
Expansion ROM at 6c780000 [disabled] [size=512K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [70] MSI-X: Enable+ Count=129 Masked-
Capabilities: [a0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number X
Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
Capabilities: [1a0] Transaction Processing Hints
Capabilities: [1b0] Access Control Services
Capabilities: [1d0] Secondary PCI Express
Kernel driver in use: i40e
Kernel modules: i40e
02:00.1 Ethernet controller: Intel Corporation Ethernet Controller X710 for 10GbE SFP+ (rev 02)
Subsystem: Intel Corporation Ethernet Converged Network Adapter X710
Flags: bus master, fast devsel, latency 0, IRQ 16, IOMMU group 14
Memory at 611c800000 (64-bit, prefetchable) [size=8M]
Memory at 611e000000 (64-bit, prefetchable) [size=32K]
Expansion ROM at 6c700000 [disabled] [size=512K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [70] MSI-X: Enable+ Count=129 Masked-
Capabilities: [a0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number X
Capabilities: [150] Alternative Routing-ID Interpretation (ARI)
Capabilities: [160] Single Root I/O Virtualization (SR-IOV)
Capabilities: [1a0] Transaction Processing Hints
Capabilities: [1b0] Access Control Services
Kernel driver in use: i40e
Kernel modules: i40e
57:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 04)
Subsystem: Intel Corporation Ethernet Controller I226-V
Flags: fast devsel, IRQ 16, IOMMU group 15
Memory at 6c300000 (32-bit, non-prefetchable) [size=1M]
Memory at 6c400000 (32-bit, non-prefetchable) [size=16K]
Expansion ROM at 6c200000 [disabled] [size=1M]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [70] MSI-X: Enable- Count=5 Masked-
Capabilities: [a0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number X
Capabilities: [1c0] Latency Tolerance Reporting
Capabilities: [1f0] Precision Time Measurement
Capabilities: [1e0] L1 PM Substates
Kernel driver in use: igc
Kernel modules: igc
58:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-LM (rev 04)
Subsystem: Intel Corporation Ethernet Controller I226-LM
Flags: bus master, fast devsel, latency 0, IRQ 19, IOMMU group 16
Memory at 6c500000 (32-bit, non-prefetchable) [size=1M]
Memory at 6c600000 (32-bit, non-prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable- Count=1/1 Maskable+ 64bit+
Capabilities: [70] MSI-X: Enable+ Count=5 Masked-
Capabilities: [a0] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number X
Capabilities: [1c0] Latency Tolerance Reporting
Capabilities: [1f0] Precision Time Measurement
Capabilities: [1e0] L1 PM Substates
Kernel driver in use: igc
Kernel modules: igc/etc/network/interfaces
Code:
root@MS1:~# cat /etc/network/interfaces
# network interface settings; autogenerated
# Please do NOT modify this file directly, unless you know what
# you're doing.
#
# If you want to manage parts of the network configuration manually,
# please utilize the 'source' or 'source-directory' directives to do
# so.
# PVE will preserve these directives, but will NOT read its network
# configuration from sourced files, so do not attempt to move any of
# the PVE managed interfaces into external files!
auto lo
iface lo inet loopback
iface enp2s0f0np0 inet manual
mtu 9000
iface enp87s0 inet manual
mtu 9000
auto enp88s0
iface enp88s0 inet manual
mtu 9000
iface enp2s0f1np1 inet manual
mtu 9000
auto vmbr0
iface vmbr0 inet static
address 192.168.10.11/24
gateway 192.168.10.1
bridge-ports enp2s0f0np0
bridge-stp off
bridge-fd 0
bridge-vlan-aware yes
bridge-vids 2-1094
mtu 9000
offload-rx-vlan-filter off
source /etc/network/interfaces.d/*Software running on the box
Code:
root@MS1:~# pveversion -v
proxmox-ve: 8.2.0 (running kernel: 6.8.8-1-pve)
pve-manager: 8.2.4 (running version: 8.2.4/faa83925c9641325)
proxmox-kernel-helper: 8.1.0
proxmox-kernel-6.8: 6.8.8-1
proxmox-kernel-6.8.8-1-pve-signed: 6.8.8-1
proxmox-kernel-6.8.4-2-pve-signed: 6.8.4-2
ceph-fuse: 17.2.7-pve3
corosync: 3.1.7-pve3
criu: 3.17.1-2
glusterfs-client: 10.3-5
ifupdown2: 3.2.0-1+pmx9
intel-microcode: 3.20240531.1+nmu1
ksm-control-daemon: 1.5-1
libjs-extjs: 7.0.0-4
libknet1: 1.28-pve1
libproxmox-acme-perl: 1.5.1
libproxmox-backup-qemu0: 1.4.1
libproxmox-rs-perl: 0.3.3
libpve-access-control: 8.1.4
libpve-apiclient-perl: 3.3.2
libpve-cluster-api-perl: 8.0.7
libpve-cluster-perl: 8.0.7
libpve-common-perl: 8.2.2
libpve-guest-common-perl: 5.1.4
libpve-http-server-perl: 5.1.0
libpve-network-perl: 0.9.8
libpve-rs-perl: 0.8.9
libpve-storage-perl: 8.2.3
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.4.0-3
proxmox-backup-client: 3.2.7-1
proxmox-backup-file-restore: 3.2.7-1
proxmox-firewall: 0.5.0
proxmox-kernel-helper: 8.1.0
proxmox-mail-forward: 0.2.3
proxmox-mini-journalreader: 1.4.0
proxmox-offline-mirror-helper: 0.6.6
proxmox-widget-toolkit: 4.2.3
pve-cluster: 8.0.7
pve-container: 5.1.12
pve-docs: 8.2.3
pve-edk2-firmware: 4.2023.08-4
pve-esxi-import-tools: 0.7.1
pve-firewall: 5.0.7
pve-firmware: 3.13-1
pve-ha-manager: 4.0.5
pve-i18n: 3.2.2
pve-qemu-kvm: 9.0.2-2
pve-xtermjs: 5.3.0-3
qemu-server: 8.2.4
smartmontools: 7.3-pve1
spiceterm: 3.3.0
swtpm: 0.8.0+pve1
vncterm: 1.8.0
zfsutils-linux: 2.2.4-pve1The firmware on the NICs is up to date.
Code:
root@MS1:~# ethtool enp2s0f0np0
Settings for enp2s0f0np0:
Supported ports: [ FIBRE ]
Supported link modes: 10000baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: No
Supported FEC modes: Not reported
Advertised link modes: 10000baseT/Full
Advertised pause frame use: No
Advertised auto-negotiation: No
Advertised FEC modes: Not reported
Speed: 10000Mb/s
Duplex: Full
Auto-negotiation: off
Port: Direct Attach Copper
PHYAD: 0
Transceiver: internal
Supports Wake-on: g
Wake-on: g
Current message level: 0x00000007 (7)
drv probe link
Link detected: yes
root@MS1:~# ethtool -i enp2s0f0np0
driver: i40e
version: 6.8.8-1-pve
firmware-version: 9.50 0x8000f12c 0.0.0
expansion-rom-version:
bus-info: 0000:02:00.0
supports-statistics: yes
supports-test: yes
supports-eeprom-access: yes
supports-register-dump: yes
supports-priv-flags: yes
root@MS1:~#Any idea where this eth0 ghost is coming from and why my dmesg is being spammed by it if the interface "eth0" is nowhere on the system it seems? The hardware is https://store.minisforum.com/products/minisforum-ms-01 and they gave me a BIOS update to install, once I installed that BIOS update I noticed system instability and this ghost interface. I have already flashed back an older bios but the instability and log entries are still there.
Not sure what else to debug for this ghost interface.
Last edited: