Description of problem: When ping guest from host (host->guest) && ping host from guest (guest->host), it always lost packets using rtl8139 nic on RHEL-Server-5.4 It's easy to reproduce set size of icmp as 65507 or 32767. Version-Release number of selected component (if applicable): [root@intel-q9400-4-1 ~]# rpm -qa |grep kvm kmod-kvm-83-105.el5_4.9 kvm-qemu-img-83-105.el5_4.9 etherboot-zroms-kvm-5.4.4-10.el5 kvm-tools-83-105.el5_4.9 kvm-debuginfo-83-105.el5_4.9 kvm-83-105.el5_4.9 How reproducible: 100% Steps to Reproduce: 1. Start a VM(RHEL-Server-5.4) using rtl8138 nic 2. Ping guest from host 3. Ping host from guest Actual results: Lost packets when ping guest from host Lost packets when ping host form guest No packet lost. Expected results: Success to ping guest from host Success to ping host form guest No packet lost. Additional info: command to start VM: (using switch) [root@intel-q9400-4-1 images]# qemu-kvm -name vm1 -monitor stdio -drive file=./RHEL-Server-5.4-64.qcow2,media=disk,if=ide,cache=off,boot=on -net nic,vlan=0,macaddr=00:11:22:33:8D:02,model=rtl8139 -net tap,vlan=0,ifname=AUTOTEST_332,script=/etc/qemu-ifup-switch,downscript=no -m 512 -usbdevice tablet -rtc-td-hack -no-hpet -cpu qemu64,+sse2 -no-kvm-pit-reinjection -smp 1 -vnc :22 [root@intel-q9400-4-1 ~]# brctl show all bridge name bridge id STP enabled interfaces switch 8000.0023ae8fce25 no eth0 AUTOTEST_332 virbr0 8000.3a281deffec5 yes ----------------------------------------------------------- command to start VM: (using virtbr0) [root@intel-q9400-4-1 images]# qemu-kvm -name vm1 -monitor stdio -drive file=./RHEL-Server-5.4-64.qcow2,media=disk,if=ide,cache=off,boot=on -net nic,vlan=0,macaddr=00:11:22:33:8D:02,model=rtl8139 -net tap,vlan=0,ifname=AUTOTEST_332,script=/etc/qemu-ifup-virbr0,downscript=no -m 512 -usbdevice tablet -rtc-td-hack -no-hpet -cpu qemu64,+sse2 -no-kvm-pit-reinjection -smp 1 -vnc :22 [root@intel-q9400-4-1 ~]# brctl show all bridge name bridge id STP enabled interfaces switch 8000.0023ae8fce25 no eth0 virbr0 8000.3a281deffec5 yes AUTOTEST_332 ----------------------------------------------------------- Host --> guest [root@intel-q9400-4-1 kvm_runtest_2]# ping -c 10 10.66.82.147 -s 65507 PING 10.66.82.147 (10.66.82.147) 65507(65535) bytes of data. 65515 bytes from 10.66.82.147: icmp_seq=1 ttl=64 time=86.9 ms 65515 bytes from 10.66.82.147: icmp_seq=2 ttl=64 time=1002 ms 65515 bytes from 10.66.82.147: icmp_seq=3 ttl=64 time=1002 ms 65515 bytes from 10.66.82.147: icmp_seq=4 ttl=64 time=1042 ms 65515 bytes from 10.66.82.147: icmp_seq=7 ttl=64 time=1002 ms 65515 bytes from 10.66.82.147: icmp_seq=8 ttl=64 time=1002 ms 65515 bytes from 10.66.82.147: icmp_seq=9 ttl=64 time=956 ms --- 10.66.82.147 ping statistics --- 10 packets transmitted, 7 received, 30% packet loss, time 8999ms rtt min/avg/max/mdev = 86.988/870.841/1042.910/320.850 ms, pipe 2 ---------------------- Guest --> host: [root@localhost network-scripts]# ping 10.66.82.249 -c 20 -s 32767 PING 10.66.82.249 (10.66.82.249) 32767(32795) bytes of data. 32775 bytes from 10.66.82.249: icmp_seq=1 ttl=64 time=625 ms 32775 bytes from 10.66.82.249: icmp_seq=2 ttl=64 time=109 ms 32775 bytes from 10.66.82.249: icmp_seq=3 ttl=64 time=63.4 ms 32775 bytes from 10.66.82.249: icmp_seq=4 ttl=64 time=363 ms 32775 bytes from 10.66.82.249: icmp_seq=5 ttl=64 time=735 ms 32775 bytes from 10.66.82.249: icmp_seq=6 ttl=64 time=1003 ms 32775 bytes from 10.66.82.249: icmp_seq=7 ttl=64 time=1724 ms 32775 bytes from 10.66.82.249: icmp_seq=8 ttl=64 time=1725 ms 32775 bytes from 10.66.82.249: icmp_seq=12 ttl=64 time=1002 ms 32775 bytes from 10.66.82.249: icmp_seq=13 ttl=64 time=1704 ms --- 10.66.82.249 ping statistics --- 20 packets transmitted, 10 received, 50% packet loss, time 19041ms rtt min/avg/max/mdev = 63.472/905.880/1725.028/611.979 ms, pipe 2
Created attachment 364874 [details] ping message of guest ping from guest to host
Created attachment 364875 [details] ping message of host ping from host to guest
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.
This request was erroneously denied for the current release of Red Hat Enterprise Linux. The error has been fixed and this request has been re-proposed for the current release.
Reassigning to mst.
Could not reproduce this bug with latest kvm/guest. kvm-83-219.el5 guest: 5.5.z