 Home |
Products |
Support |
Community |
News |
xen-users
[Xen-users] a lot of packet loss
| To: | xen-users@xxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | [Xen-users] a lot of packet loss |
| From: | Attila Szamos <szamosa@xxxxxxxxx> |
| Date: | Fri, 1 May 2009 23:15:15 +0200 |
| Delivery-date: | Fri, 01 May 2009 14:16:50 -0700 |
| Dkim-signature: | v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=+BNImqsOC26x3iellYYLMUl1zwDSh3eNIIl8dlgfD1o=; b=K78L1wgAWFYqy/ijeFxumcZWQVkxv+wTkOy7aSRJQLip3SgQaBnskDx/cD14nds+fZ oTbzrJTAS83rFQ/JpEVwG0FRGxykZ6DxQ6QizrTMc6MxHgfj87gIbBD2AMOPxDlVNqtl HT/8utaY2JBUq3iprHBfuzUK2gqXYWD3tTw0M= |
| Domainkey-signature: | a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=Ckr63YbrV2D3VCa1V1H1aSa2jdKBhsOx74zXgvEUM5bA/2dlxPnFODHl/+gG3vk7W/ 76VU6j/pGeGO5E9G33JuyRFLEth9wxHTmM4JZ/7yRr84Tv2/YZcGC61nqwl+seu2gDw+ aRobUfZYtj/qekLYWXnfv+YgT/Xm6rYVsIN8U= |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxxx |
| List-help: | <mailto:xen-users-request@lists.xensource.com?subject=help> |
| List-id: | Xen user discussion <xen-users.lists.xensource.com> |
| List-post: | <mailto:xen-users@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe> |
| Sender: | xen-users-bounces@xxxxxxxxxxxxxxxxxxx |
I've fix-ed the timesyncronization problem. But I don't know where to start with the network problem. If I ping the VM a lot of packet didn't get an echo reply. root@test6:~# ping perftest-vm2 PING test-vm2 (172.27.68.28) 56(84) bytes of data. 64 bytes from test-vm2 (172.27.68.28): icmp_seq=1 ttl=64 time=0.346 ms 64 bytes from test-vm2 (172.27.68.28): icmp_seq=2 ttl=64 time=0.048 ms 64 bytes from test-vm2 (172.27.68.28): icmp_seq=3 ttl=64 time=0.039 ms 64 bytes from test-vm2 (172.27.68.28): icmp_seq=4 ttl=64 time=0.041 ms 64 bytes from test-vm2 (172.27.68.28): icmp_seq=6 ttl=64 time=0.032 ms 64 bytes from test-vm2 (172.27.68.28): icmp_seq=7 ttl=64 time=0.044 ms 64 bytes from test-vm2 (172.27.68.28): icmp_seq=8 ttl=64 time=0.038 ms 64 bytes from test-vm2 (172.27.68.28): icmp_seq=43 ttl=64 time=8.05 ms 64 bytes from test-vm2 (172.27.68.28): icmp_seq=56 ttl=64 time=0.042 ms 64 bytes from test-vm2 (172.27.68.28): icmp_seq=57 ttl=64 time=0.036 ms 64 bytes from test-vm2 (172.27.68.28): icmp_seq=58 ttl=64 time=0.041 ms 64 bytes from test-vm2 (172.27.68.28): icmp_seq=59 ttl=64 time=0.038 ms 64 bytes from test-vm2 (172.27.68.28): icmp_seq=60 ttl=64 time=0.041 ms 64 bytes from test-vm2 (172.27.68.28): icmp_seq=61 ttl=64 time=0.038 ms 64 bytes from test-vm2 (172.27.68.28): icmp_seq=62 ttl=64 time=0.033 ms --- test-vm2 ping statistics --- 64 packets transmitted, 15 received, 76% packet loss, time 63064ms rtt min/avg/max/mdev = 0.032/0.594/8.056/1.995 ms I've tried to switch the networking to 'route' from 'bridge', but it didn't help. Any suggestions? _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-users] I/O request not ready: 0, ptr: 0, port: 0, data: 0, count: 0, size: 0 with VNC enabled, Fajar A. Nugraha |
|---|---|
| Next by Date: | [Xen-users] problems with xensource lists?, Fajar A. Nugraha |
| Previous by Thread: | [Xen-users] time is losing 2 hours in domU and problem with the network, Attila Szamos |
| Next by Thread: | Re: [Xen-users] a lot of packet loss, Bhasker C V |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
