High TX-DROP with all CT

[meepmeep]

Hi

I'm using proxmox since few months, and I just notice a lot of "TX Drop" on all my CT :

Some details to help you understand my network configuration :
- veth100.0 = eth0 for CT100 (public ip) = vmrb0 = eth0,
- veth100.1 = eth1 for CT100 (private ip) = vmrb1 = private bridge not link to physical interface,
- veth102.0 = eth0 for CT102 (public ip) = vmrb0,
- veth102.1 = eth1 for CT102 (private ip) = vmrb0,
- veth103.0 = eth0 for CT103 (private ip]). Public ip is using venet0.
etc.

netstat -i
Kernel Interface table
Iface   MTU Met   RX-OK RX-ERR RX-DRP RX-OVR    TX-OK TX-ERR TX-DRP TX-OVR Flg
eth0       1500 0   [URL="tel:1282769848 0"]1282769848 0[/URL]      0 0 [URL="tel:1193938364 0"]1193938364 0[/URL]   0 0 BMRU
eth1       9000 0   26762838     0      0 0   44556339     0   0 0 BMRU
venet0     1500 0   501454698       0      0 0   493423389   0 90 0 BOPRU
veth100.0  1500 0   435748892       0      0 0 521975239   0 [URL="tel:145182255 0"]145182255 0[/URL] BMRU
veth100.1  1500 0   2254389       0      0 0 3252985     0 11 0 BMRU
veth102.0  1500 0   112088546       0      0 0 64394239     0 50181198 0 BMRU
veth102.1  1500 0     818222       0      0 0 [URL="tel:1153631"]1153631[/URL]     0 4 0 BMRU
veth103.0  1500 0   8810149       0      0 0   6673935     0 16 0 BMRU
vmbr0       1500 0   525721778       0      0 0 519952405   0 0 0 BMRU
vmbr1       1500 0   7376102     0      0 0   6547949     0 0 0 BMRU

As you can see, drop affects VETH and VENET interface.

pve-manager: 3.0-23 (pve-manager/3.0/957f0862)
running kernel: 2.6.32-20-pve
proxmox-ve-2.6.32: 3.0-107
pve-kernel-2.6.32-22-pve: 2.6.32-107
pve-kernel-2.6.32-20-pve: 2.6.32-100
pve-kernel-2.6.32-19-pve: 2.6.32-96
pve-kernel-2.6.32-18-pve: 2.6.32-88
lvm2: 2.02.95-pve3
clvm: 2.02.95-pve3
corosync-pve: 1.4.5-1
openais-pve: 1.1.4-3
libqb0: 0.11.1-2
redhat-cluster-pve: 3.2.0-2
resource-agents-pve: 3.9.2-4
fence-agents-pve: 4.0.0-1
pve-cluster: 3.0-4
qemu-server: 3.0-20
pve-firmware: 1.0-23
libpve-common-perl: 3.0-4
libpve-access-control: 3.0-4
libpve-storage-perl: 3.0-8
vncterm: 1.1-4
vzctl: 4.0-1pve3
vzprocps: 2.0.11-2
vzquota: 3.1-2
pve-qemu-kvm: 1.4-13
ksm-control-daemon: 1.1-1

Eth0 Network card model : 02:00.0 Ethernet controller: Intel Corporation 82574L Gigabit Network Connection

 

[meepmeep]

Little update, it looks like that tx-drop started in early July, which match with my migration to proxmox 3.0 (0 drop, collision before that date).

To be confirmed, it could come from Munin which wasn't logging this information on Debian 6 / proxmox 2.3...

 

[iconvergence]

Little update, it looks like that tx-drop started in early July, which match with my migration to proxmox 3.0 (0 drop, collision before that date).

To be confirmed, it could come from Munin which wasn't logging this information on Debian 6 / proxmox 2.3...

i have the same issue on 3 differents computers & hardware. All are in proxmox 3.

 

[meepmeep]

Update: i migrate all my network interfaces to VENET. No packet have been dropped since.
(the tx-drop is only increasing when the CT are starting and the network is not available immediately, after that, no more dropped packet).

This is still a strange behavior, i will submit on bugzilla

 

[iconvergence]

venet is ok too however need bridge for windows

do you have the bugzilla id ?