Short answer: linux-image-2.6.32-5-xen-amd64_2.6.32-48squeeze4~ijc0_amd64.deb solves my problem (bonding packet loss). Tests: - 2 nodes with base install of squeeze - apt-get install xen-linux-system ifenslave-2.6 - each node has one single head and one dual head NIC: root@xen02:/# dmesg | grep eth [ 0.795296] e1000e 0000:05:00.0: eth0: (PCI Express:2.5GB/s:Width x1) 00:19:d1:a3:e9:0d [ 0.795299] e1000e 0000:05:00.0: eth0: Intel(R) PRO/1000 Network Connection [ 0.795368] e1000e 0000:05:00.0: eth0: MAC: 2, PHY: 2, PBA No: FFFFFF-0FF [ 0.869452] igb 0000:02:00.0: eth1: (PCIe:2.5Gb/s:Width x4) 00:1b:21:aa:07:10 [ 1.079555] igb 0000:02:00.1: eth2: (PCIe:2.5Gb/s:Width x4) 00:1b:21:aa:07:11 [ 1.079846] igb 0000:02:00.1: eth2: PBA No: G18758-001 02:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01) - the dual head NICs are configured as bond1 pointopoint: iface bond1 inet static bond-slaves eth1 eth2 bond-mode 0 bond-miimon 100 bond-primary eth1 eth2 address 10.10.10.12 netmask 255.255.255.0 network 10.10.10.255 pointopoint 10.10.10.10 Test1: node xen01 runs linux-image-2.6.32-5-xen-amd64_2.6.32-45_amd64 root@xen02:/home/helmutw# ping 10.10.10.10 [...] ^C --- 10.10.10.10 ping statistics --- 10 packets transmitted, 7 received, 30% packet loss, time 9022ms rtt min/avg/max/mdev = 0.026/0.027/0.029/0.003 ms Test2: both nodes run linux-image-2.6.32-5-xen-amd64_2.6.32-48squeeze3_amd64 packet loss: 100% Test3: node xen01 runs linux-image-2.6.32-5-xen-amd64_2.6.32-45_amd64 node xen02 runs linux-image-2.6.32-5-xen-amd64_2.6.32-48squeeze4~ijc0_amd64 packet loss: 0% Test4: both nodes run linux-image-2.6.32-5-xen-amd64_2.6.32-48squeeze4~ijc0_amd64 packet loss: 0% Obviously these tests say nothing about the other reported problems. Helmut Wollmersdorfer |