Errors in ethX with Intel E1000

[Abel Paz]

Hi,

From last update we detected some problems with Intel E1000 network configuration. If we use it, errors appear on network info:

ifconfig eth
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.3.119  netmask 255.255.255.0  broadcast 192.168.3.255
        ether 00:50:56:00:01:07  txqueuelen 1000  (Ethernet)
        RX packets 5233235  bytes 1390147408 (1.2 GiB)
        RX errors 535  dropped 261  overruns 0  frame 535
        TX packets 2473740  bytes 2647585012 (2.4 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

(just a few hours running)

If you select VirtIO or Realtek cards insted, no errors apear. The problem is Realtek is 100Mb, and VirtIO is not the ideal NIC to use in this environments.

¿Is this any kind of bug introduced in last version? We had 4.2.6 kernel before updating the cluster.

proxmox-ve: 4.1-37 (running kernel: 4.2.8-1-pve)
pve-manager: 4.1-13 (running version: 4.1-13/cfb599fb)
pve-kernel-4.2.6-1-pve: 4.2.6-36
pve-kernel-4.2.8-1-pve: 4.2.8-37
pve-kernel-2.6.32-29-pve: 2.6.32-126
pve-kernel-4.2.2-1-pve: 4.2.2-16
pve-kernel-2.6.32-41-pve: 2.6.32-163
pve-kernel-4.2.3-2-pve: 4.2.3-22
lvm2: 2.02.116-pve2
corosync-pve: 2.3.5-2
libqb0: 1.0-1
pve-cluster: 4.0-32
qemu-server: 4.0-55
pve-firmware: 1.1-7
libpve-common-perl: 4.0-48
libpve-access-control: 4.0-11
libpve-storage-perl: 4.0-40
pve-libspice-server1: 0.12.5-2
vncterm: 1.2-1
pve-qemu-kvm: 2.5-5
pve-container: 1.0-44
pve-firewall: 2.0-17
pve-ha-manager: 1.0-21
ksm-control-daemon: 1.2-1
glusterfs-client: 3.5.2-2+deb8u1
lxc-pve: 1.1.5-7
lxcfs: 0.13-pve3
cgmanager: 0.39-pve1
criu: 1.6.0-1

Thanks in advance.

Best regards,
Abel.

 

[Richard]

Hi,

From last update we detected some problems with Intel E1000 network configuration. If we use it, errors appear on network info:

ifconfig eth
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.3.119  netmask 255.255.255.0  broadcast 192.168.3.255
        ether 00:50:56:00:01:07  txqueuelen 1000  (Ethernet)
        RX packets 5233235  bytes 1390147408 (1.2 GiB)
        RX errors 535  dropped 261  overruns 0  frame 535
        TX packets 2473740  bytes 2647585012 (2.4 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

(just a few hours running)

If you select VirtIO or Realtek cards insted, no errors apear. The problem is Realtek is 100Mb, and VirtIO is not the ideal NIC to use in this environments.

¿Is this any kind of bug introduced in last version? We had 4.2.6 kernel before updating the cluster.

proxmox-ve: 4.1-37 (running kernel: 4.2.8-1-pve)
pve-manager: 4.1-13 (running version: 4.1-13/cfb599fb)

I have the same version running already for a couple of weeks with an ubuntu guest and much traffic and did not encounter such a problem.

 

[Abel Paz]

Hi,
Just one machine and using Intel E1000 is not a similar case to us. We have over 10-15 guests per host in a cluster of 6 nodes, and independently on the host and the guest operating system, Intel E1000 is reporting errors in eth0 using this version.

The paravirtualized VirtIO NIC does not have this problem by now.

 

[Francois Legrand]

Same problem here. Migrating VM from proxmox 3 to 4. Most of the VM with E1000 shows errors !!!

 

[Abel Paz]

Same problem here. Migrating VM from proxmox 3 to 4. Most of the VM with E1000 shows errors !!!

We had to change all our interfaces to VirtIO. Old machines that doesn't support VirtIO still present this problem (even with latest Proxmox VE version existing)

 

[novascore.io]

I've also had this issue. I have a firewall setup with two interfaces. Funnily enough, only the internal interface was registering the errors, and only when other VMs were making requests through the firewall. If I turned all other VMs off and routed traffic from from other physical machines, still passing through the firewall, I'd have zero errors. Boot up local VMs, and errors on the local interface (LAN side NIC) started counting up.

I ended up "solving" the issue by changing the LAN side interface to Virtio, problem resolved. I left the WAN side interface as Intel.

Cheers
ns