[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-users] Slow networking problem in dom0
for tcpdump , i do it like this :
tcpdump -i ethX -w ethX.dump
type Ctrl+C when you think you have enough.
it will create a file ethX.dump with all the packets.
then get it on your desktop and open up with wireshark, see if there
is a lot of black lines (wireshark automaticly underlines the
packets in error in black)
If not, try to look if the flows are like they should be ( not too
much icmp, or other things, i don't know )
by the way i don't understand well what is xen-pub, it doesn't seem
like a nic , a xen device, nor a bridge :/
can you descripbe your network ?
For me it seems :
you have 2 nic : eth0 and eth1 wich is not used.
Then i supposed virbr0 was the bridge used between xen devices and
eth0
i see you have one Domu running ( vif4.0 )
and then the 3 other , but by there names, i wich say they are
definitly bridges, but you shouldn't have that traffic on xen-pub if
this is the case.
Can you post the output of brctl show ?
Thanks.
Le 14/05/2011 18:54, Joel Witherspoon a écrit :
So,
You're running IPv6 and IPv4 on the same interface? Can you do
without IPv6?
On Sat, May 14, 2011 at 9:49 AM, Emil
Christopher Melar <typeof@xxxxxxxxx>
wrote:
On Sat, May 14, 2011 at 6:14 PM, Erwan RENIER
< erwan.renier@xxxxxxxxxxx>
wrote:
> Did you try tcpdump allready to examine it with
wireshark, to see i there
> are problems with the flows ( like retransmitted
paquets ) , i had this
> problem on virtualbox that maid the network very slow.
over time (hours) it drops to 500-600 k/sec. My setup is
stated in the
first post.
tcpdump didn't work:
> Another option is to not bridge but route the network,
at least to see if it
> works.
> Also did you check your stats on the interfaces and on
the bridge for errors
> ?
tcpdump doesn't say anything unusual when it comes to ICMP at
least.
Any suggestions to what to test on?
I did sudo tcpdump -nnvvi xen-pub icmp[0] = 8 or icmp[0] =
30.
I am clueless on what to test :-)
I can't change the network configuration as I am only on
remote right
now. I just want to know if there's anything inherently wrong
with my
kernel and / or bridge configuration.
> can you post the result of : ifconfig -a on the host.
> Is there any relevant logs ( dmesg ).
> Thanks.
eth0 Link encap:Ethernet HWaddr 00:1b:21:8d:b1:27
inet6 addr: fe80::21b:21ff:fe8d:b127/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:69748631 errors:0 dropped:22 overruns:0
frame:0
TX packets:20460331 errors:0 dropped:0 overruns:0
carrier:0
collisions:0 txqueuelen:1000
RX bytes:87875949926 (87.8 GB) TX bytes:21764017480
(21.7 GB)
eth1 Link encap:Ethernet HWaddr bc:ae:c5:de:97:0d
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:18
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:9862 errors:0 dropped:0 overruns:0 frame:0
TX packets:9862 errors:0 dropped:0 overruns:0
carrier:0
collisions:0 txqueuelen:0
RX bytes:705262
(705.2 KB) TX bytes:705262
(705.2 KB)
sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
vif4.0 Link encap:Ethernet HWaddr fe:ff:ff:ff:ff:ff
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500
Metric:1
RX packets:59827 errors:0 dropped:0 overruns:0
frame:0
TX packets:700342 errors:0 dropped:6 overruns:0
carrier:0
collisions:0 txqueuelen:32
RX bytes:11462334 (11.4 MB) TX bytes:618194259
(618.1 MB)
virbr0 Link encap:Ethernet HWaddr aa:5e:2e:b3:28:32
inet addr:192.168.122.1 Bcast:192.168.122.255
Mask:255.255.255.0
inet6 addr: fe80::a85e:2eff:feb3:2832/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:26 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:1628 (1.6 KB)
xen-dmz Link encap:Ethernet HWaddr 5a:d4:56:b2:a8:17
inet6 addr: fe80::58d4:56ff:feb2:a817/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:468 (468.0 B)
xen-intern Link encap:Ethernet HWaddr 02:99:ff:50:7b:22
inet6 addr: fe80::99:ffff:fe50:7b22/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:468 (468.0 B)
xen-pub Link encap:Ethernet HWaddr 00:1b:21:8d:b1:27
inet addr:192.168.0.3 Bcast:192.168.0.255
Mask:255.255.255.0
inet6 addr: fe80::21b:21ff:fe8d:b127/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:68302724 errors:0 dropped:0 overruns:0
frame:0
TX packets:18407729 errors:0 dropped:0 overruns:0
carrier:0
collisions:0 txqueuelen:0
RX bytes:86617595475 (86.6 GB) TX bytes:22462523015
(22.4 GB)
Thanks!
--
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
