thr3ads.net - Xen users - [Xen-users] Slow networking problem in dom0 [Apr 2011]

If this information is useful, please help other people find it:
Share via:

Emil Christopher Melar

2011-Apr-29 10:16 UTC

[Xen-users] Slow networking problem in dom0

Hi! I have a sandy bridge H67 machine running Intel  i7 2600k.
I installed  build-linux-2.6-pvops_x86_64 (commit
75cc13f5aa29b4f3227d269ca165dfa8937c94fe).
It is running fine on my Ubuntu 10.10 Maverick, besides one thing: The
ethernet goes from 50 MB/sec to 500 k/sec over time!

Now my ethernet is dead slow and I have to restart the eth0 resulting
in breaking the domU networks.
The NIC I use is an intel e1000, so it should be pretty stable. The
slowdown is both domU <--> dom0, and dom0 <--> external network.

I am getting really desperate since this is sort of in production. :)
Thanks for any help!

Some info:
Kernel Linux 2.6.32.27 x86_64 PVOPS

$ ethtool -i eth0

driver: e1000
version: 7.3.21-k5-NAPI
firmware-version: N/A
bus-info: 0000:08:00.0

Settings for eth0:
        Supported ports: [ TP ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Full
        Advertised pause frame use: No
        Advertised auto-negotiation: Yes
        Speed: 1000Mb/s
        Duplex: Full
        Port: Twisted Pair
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        MDI-X: Unknown
        Supports Wake-on: umbg
        Wake-on: g
        Current message level: 0x00000007 (7)
        Link detected: yes

Offload parameters for eth0:
rx-checksumming: on
tx-checksumming: on
scatter-gather: on
tcp-segmentation-offload: on
udp-fragmentation-offload: off
generic-segmentation-offload: on
generic-receive-offload: off
large-receive-offload: off
ntuple-filters: off
receive-hashing: off

/etc/network/interfaces:


# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

auto xen-pub
iface xen-pub inet static
      address 192.168.0.3
      netmask 255.255.255.0
      broadcast 192.168.0.255
      gateway 192.168.0.1
      bridge_ports eth0
      bridge_maxwait 1
      bridge_stp no
auto xen-dmz
iface xen-dmz inet manual
      pre-up  brctl addbr xen-dmz ; ifconfig xen-dmz up
      post-down ifconfig xen-dmz down ; brctl delbr xen-dmz
auto xen-intern
iface xen-intern inet manual
      pre-up  brctl addbr xen-intern ; ifconfig xen-intern up
      post-down ifconfig xen-intern down ; brctl delbr xen-intern
-- 
Emil Christopher Solli Melar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Mike Wright

2011-Apr-29 15:12 UTC

head link

Re: [Xen-users] Slow networking problem in dom0

On 04/29/2011 06:16 AM, Emil Christopher Melar wrote:> Hi! I have a sandy bridge H67 machine running Intel  i7 2600k.
> I installed  build-linux-2.6-pvops_x86_64 (commit
> 75cc13f5aa29b4f3227d269ca165dfa8937c94fe).
> It is running fine on my Ubuntu 10.10 Maverick, besides one thing: The
> ethernet goes from 50 MB/sec to 500 k/sec over time!
>
> Now my ethernet is dead slow and I have to restart the eth0 resulting
> in breaking the domU networks.
> The NIC I use is an intel e1000, so it should be pretty stable. The
> slowdown is both domU<-->  dom0, and dom0<-->  external
network.
>
> I am getting really desperate since this is sort of in production. :)
> Thanks for any help!
>
> Some info:
> Kernel Linux 2.6.32.27 x86_64 PVOPS
>
> $ ethtool -i eth0
>
> driver: e1000
> version: 7.3.21-k5-NAPI
> firmware-version: N/A
> bus-info: 0000:08:00.0
>
> Settings for eth0:
>          Supported ports: [ TP ]
>          Supported link modes:   10baseT/Half 10baseT/Full
>                                  100baseT/Half 100baseT/Full
>                                  1000baseT/Full
>          Supports auto-negotiation: Yes
>          Advertised link modes:  10baseT/Half 10baseT/Full
>                                  100baseT/Half 100baseT/Full
>                                  1000baseT/Full
>          Advertised pause frame use: No
>          Advertised auto-negotiation: Yes
>          Speed: 1000Mb/s
>          Duplex: Full
>          Port: Twisted Pair
>          PHYAD: 0
>          Transceiver: internal
>          Auto-negotiation: on
>          MDI-X: Unknown
>          Supports Wake-on: umbg
>          Wake-on: g
>          Current message level: 0x00000007 (7)
>          Link detected: yes
>
> Offload parameters for eth0:
> rx-checksumming: on
> tx-checksumming: on
This may be the problem.  Try "ethtool -K eth0 tx off"
> scatter-gather: on
> tcp-segmentation-offload: on
> udp-fragmentation-offload: off
> generic-segmentation-offload: on
> generic-receive-offload: off
> large-receive-offload: off
> ntuple-filters: off
> receive-hashing: off
>
> /etc/network/interfaces:
>
>
> # This file describes the network interfaces available on your system
> # and how to activate them. For more information, see interfaces(5).
>
> # The loopback network interface
> auto lo
> iface lo inet loopback
>
> auto xen-pub
> iface xen-pub inet static
>        address 192.168.0.3
>        netmask 255.255.255.0
>        broadcast 192.168.0.255
>        gateway 192.168.0.1
>        bridge_ports eth0
>        bridge_maxwait 1
>        bridge_stp no
> auto xen-dmz
> iface xen-dmz inet manual
>        pre-up  brctl addbr xen-dmz ; ifconfig xen-dmz up
>        post-down ifconfig xen-dmz down ; brctl delbr xen-dmz
> auto xen-intern
> iface xen-intern inet manual
>        pre-up  brctl addbr xen-intern ; ifconfig xen-intern up
>        post-down ifconfig xen-intern down ; brctl delbr xen-intern

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Emil Christopher Melar

2011-Apr-29 16:33 UTC

head link

Re: [Xen-users] Slow networking problem in dom0

On Fri, Apr 29, 2011 at 5:12 PM, Mike Wright <mike.wright@mailinator.com>
wrote:
>
> This may be the problem.  Try "ethtool -K eth0 tx off"
>
Thanks for the suggestion, but it made no difference. I tested domU
<---> dom0 and that was lightning fast actually. But I would expect
that from a virtual bridge.
dom0 <--> internet seems to also go faster. I get 500-600 kb/s  on
LAN, but 1.5MB/s on internet from dom0, which is my max.
Isn''t my bridge setup pretty standard? Seems like LAN speed is the
problem.
-- 
Emil Christopher Solli Melar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Emil Christopher Melar

2011-May-05 13:47 UTC

head link

Re: [Xen-users] Slow networking problem in dom0

I am getting pretty desperate now. LAN speed is still slow!

Any help or hit would be greatly appreciated!
> On Fri, Apr 29, 2011 at 5:12 PM, Mike Wright
<mike.wright@mailinator.com> wrote:
>
>>
>> This may be the problem.  Try "ethtool -K eth0 tx off"
>>
>
> Thanks for the suggestion, but it made no difference. I tested domU
> <---> dom0 and that was lightning fast actually. But I would expect
> that from a virtual bridge.
> dom0 <--> internet seems to also go faster. I get 500-600 kb/s  on
> LAN, but 1.5MB/s on internet from dom0, which is my max.
> Isn''t my bridge setup pretty standard? Seems like LAN speed is the
problem.
> --
> Emil Christopher Solli Melar
>


-- 
Emil Christopher Solli Melar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Emil Christopher Melar

2011-May-14 14:34 UTC

head link

Re: [Xen-users] Slow networking problem in dom0

I still have the same problem with slow LAN speed, and I may have to
see myself forced to drop Xen altogether, which is kind of sad.
Any hint would be greatly appreciated!

On Fri, Apr 29, 2011 at 6:33 PM, Emil Christopher Melar
<typeof@gmail.com> wrote:> On Fri, Apr 29, 2011 at 5:12 PM, Mike Wright
<mike.wright@mailinator.com> wrote:
>
>>
>> This may be the problem.  Try "ethtool -K eth0 tx off"
>>
>
> Thanks for the suggestion, but it made no difference. I tested domU
> <---> dom0 and that was lightning fast actually. But I would expect
> that from a virtual bridge.
> dom0 <--> internet seems to also go faster. I get 500-600 kb/s  on
> LAN, but 1.5MB/s on internet from dom0, which is my max.
> Isn''t my bridge setup pretty standard? Seems like LAN speed is the
problem.
> --
> Emil Christopher Solli Melar
>
-- 
Emil Christopher Solli Melar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Erwan RENIER

2011-May-14 15:48 UTC

head link

Re: [Xen-users] Slow networking problem in dom0

And from domU to internet ?

Le 14/05/2011 16:34, Emil Christopher Melar a écrit :> I still have the same problem with slow LAN speed, and I may have to
> see myself forced to drop Xen altogether, which is kind of sad.
> Any hint would be greatly appreciated!
>
> On Fri, Apr 29, 2011 at 6:33 PM, Emil Christopher Melar
> <typeof@gmail.com>  wrote:
>> On Fri, Apr 29, 2011 at 5:12 PM, Mike
Wright<mike.wright@mailinator.com>  wrote:
>>
>>> This may be the problem.  Try "ethtool -K eth0 tx off"
>>>
>> Thanks for the suggestion, but it made no difference. I tested domU
>> <--->  dom0 and that was lightning fast actually. But I would
expect
>> that from a virtual bridge.
>> dom0<-->  internet seems to also go faster. I get 500-600 kb/s 
on
>> LAN, but 1.5MB/s on internet from dom0, which is my max.
>> Isn''t my bridge setup pretty standard? Seems like LAN speed is
the problem.
>> --
>> Emil Christopher Solli Melar
>>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Emil Christopher Melar

2011-May-14 16:03 UTC

head link

Re: [Xen-users] Slow networking problem in dom0

On Sat, May 14, 2011 at 5:48 PM, Erwan RENIER <erwan.renier@laposte.net>
wrote:> And from domU to internet ?
Thanks for the response! :-)

domU to internet also has the same speed as LAN (600k/sec tops). It
climbs up to that speed slower and slower on a big download. Whereas
on dom0 <--> internet it gets to 2 MB/sec.
> Le 14/05/2011 16:34, Emil Christopher Melar a écrit :
>>
>> I still have the same problem with slow LAN speed, and I may have to
>> see myself forced to drop Xen altogether, which is kind of sad.
>> Any hint would be greatly appreciated!
>>
>> On Fri, Apr 29, 2011 at 6:33 PM, Emil Christopher Melar
>> <typeof@gmail.com>  wrote:
>>>
>>> On Fri, Apr 29, 2011 at 5:12 PM, Mike
Wright<mike.wright@mailinator.com>
>>>  wrote:
>>>
>>>> This may be the problem.  Try "ethtool -K eth0 tx
off"
>>>>
>>> Thanks for the suggestion, but it made no difference. I tested domU
>>> <--->  dom0 and that was lightning fast actually. But I would
expect
>>> that from a virtual bridge.
>>> dom0<-->  internet seems to also go faster. I get 500-600
kb/s  on
>>> LAN, but 1.5MB/s on internet from dom0, which is my max.
>>> Isn''t my bridge setup pretty standard? Seems like LAN
speed is the
>>> problem.
>>> --
>>> Emil Christopher Solli Melar
>>>
>


-- 
Emil Christopher Solli Melar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Erwan RENIER

2011-May-14 16:14 UTC

head link

Re: [Xen-users] Slow networking problem in dom0

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.
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 ?
can you post the result of : ifconfig -a on the host.
Is there any relevant logs ( dmesg ).
Thanks.

Le 14/05/2011 18:03, Emil Christopher Melar a écrit :> On Sat, May 14, 2011 at 5:48 PM, Erwan
RENIER<erwan.renier@laposte.net>  wrote:
>> And from domU to internet ?
> Thanks for the response! :-)
>
> domU to internet also has the same speed as LAN (600k/sec tops). It
> climbs up to that speed slower and slower on a big download. Whereas
> on dom0<-->  internet it gets to 2 MB/sec.
>
>> Le 14/05/2011 16:34, Emil Christopher Melar a écrit :
>>> I still have the same problem with slow LAN speed, and I may have
to
>>> see myself forced to drop Xen altogether, which is kind of sad.
>>> Any hint would be greatly appreciated!
>>>
>>> On Fri, Apr 29, 2011 at 6:33 PM, Emil Christopher Melar
>>> <typeof@gmail.com>    wrote:
>>>> On Fri, Apr 29, 2011 at 5:12 PM, Mike
Wright<mike.wright@mailinator.com>
>>>>   wrote:
>>>>
>>>>> This may be the problem.  Try "ethtool -K eth0 tx
off"
>>>>>
>>>> Thanks for the suggestion, but it made no difference. I tested
domU
>>>> <--->    dom0 and that was lightning fast actually. But I
would expect
>>>> that from a virtual bridge.
>>>> dom0<-->    internet seems to also go faster. I get
500-600 kb/s  on
>>>> LAN, but 1.5MB/s on internet from dom0, which is my max.
>>>> Isn''t my bridge setup pretty standard? Seems like LAN
speed is the
>>>> problem.
>>>> --
>>>> Emil Christopher Solli Melar
>>>>
>
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Emil Christopher Melar

2011-May-14 16:49 UTC

head link

Re: [Xen-users] Slow networking problem in dom0

On Sat, May 14, 2011 at 6:14 PM, Erwan RENIER <erwan.renier@laposte.net>
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.
My bridge setup is pretty standard. Speed is OK right after boot. But
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!
-- 
Emil Christopher Solli Melar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Joel Witherspoon

2011-May-14 16:50 UTC

head link

Re: [Xen-users] Slow networking problem in dom0

Erwan has the right idea. Check with tcpdump and Wireshark first. Check *Large
Send Offload* as well. Turn it off if it''s enabled.

*Joel C. Witherspoon*

(626) 502 - 7201

joel.witherspoon@gmail.com
My profiles: [image: LinkedIn]
<http://www.linkedin.com/in/jcwitherspoon> [image:
Twitter] <http://www.twitter.com/joelwitherspoon>
[image: Twitter] <http://twitter.com/joelwitherspoon>Latest tweet: For the
Nintendo and Twitter lovers out there: The Fail Blooper.
http://www.cubeecraft.com/blog/fail-blooper/
Follow @joelwitherspoon <http://twitter.com/joelwitherspoon>
<http://twitter.com/?status=@joelwitherspoon%20&in_reply_to_status_id=68414509013942270&in_reply_to=joelwitherspoon>
Reply<http://twitter.com/?status=@joelwitherspoon%20&in_reply_to_status_id=68414509013942270&in_reply_to=joelwitherspoon>
<http://twitter.com/?status=RT%20%40joelwitherspoon%3A%20For%20the%20Nintendo%20and%20Twitter%20lovers%20out%20there%3A%20The%20Fail%20Blooper.%20http%3A%2F%2Fwww.cubeecraft.com%2Fblog%2Ffail-blooper%2F>
Retweet<http://twitter.com/?status=RT%20%40joelwitherspoon%3A%20For%20the%20Nintendo%20and%20Twitter%20lovers%20out%20there%3A%20The%20Fail%20Blooper.%20http%3A%2F%2Fwww.cubeecraft.com%2Fblog%2Ffail-blooper%2F>
   13:37
May-11<http://twitter.com/joelwitherspoon/statuses/68414509013942270>
  Get this email app!
<http://www.wisestamp.com/apps/twitter?utm_source=extension&utm_medium=email&utm_term=twitter&utm_campaign=apps>

Signature powered by
<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>
WiseStamp<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>

On Sat, May 14, 2011 at 9:14 AM, Erwan RENIER
<erwan.renier@laposte.net>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.
> 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 ?
> can you post the result of : ifconfig -a on the host.
> Is there any relevant logs ( dmesg ).
> Thanks.
>
> Le 14/05/2011 18:03, Emil Christopher Melar a écrit :
>
>  On Sat, May 14, 2011 at 5:48 PM, Erwan
RENIER<erwan.renier@laposte.net>
>>  wrote:
>>
>>> And from domU to internet ?
>>>
>> Thanks for the response! :-)
>>
>> domU to internet also has the same speed as LAN (600k/sec tops). It
>> climbs up to that speed slower and slower on a big download. Whereas
>> on dom0<-->  internet it gets to 2 MB/sec.
>>
>>  Le 14/05/2011 16:34, Emil Christopher Melar a écrit :
>>>
>>>> I still have the same problem with slow LAN speed, and I may
have to
>>>> see myself forced to drop Xen altogether, which is kind of sad.
>>>> Any hint would be greatly appreciated!
>>>>
>>>> On Fri, Apr 29, 2011 at 6:33 PM, Emil Christopher Melar
>>>> <typeof@gmail.com>    wrote:
>>>>
>>>>> On Fri, Apr 29, 2011 at 5:12 PM, Mike Wright<
>>>>> mike.wright@mailinator.com>
>>>>>  wrote:
>>>>>
>>>>>  This may be the problem.  Try "ethtool -K eth0 tx
off"
>>>>>>
>>>>>>  Thanks for the suggestion, but it made no difference.
I tested domU
>>>>> <--->    dom0 and that was lightning fast actually.
But I would expect
>>>>> that from a virtual bridge.
>>>>> dom0<-->    internet seems to also go faster. I get
500-600 kb/s  on
>>>>> LAN, but 1.5MB/s on internet from dom0, which is my max.
>>>>> Isn''t my bridge setup pretty standard? Seems like
LAN speed is the
>>>>> problem.
>>>>> --
>>>>> Emil Christopher Solli Melar
>>>>>
>>>>>
>>
>>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Joel Witherspoon

2011-May-14 16:54 UTC

head link

Re: [Xen-users] Slow networking problem in dom0

So,
You''re running IPv6 and IPv4 on the same interface? Can you do without
IPv6?

*Joel C. Witherspoon*

(626) 502 - 7201

joel.witherspoon@gmail.com
My profiles: [image: LinkedIn]
<http://www.linkedin.com/in/jcwitherspoon> [image:
Twitter] <http://www.twitter.com/joelwitherspoon>
[image: Twitter] <http://twitter.com/joelwitherspoon>Latest tweet: For the
Nintendo and Twitter lovers out there: The Fail Blooper.
http://www.cubeecraft.com/blog/fail-blooper/
Follow @joelwitherspoon <http://twitter.com/joelwitherspoon>
<http://twitter.com/?status=@joelwitherspoon%20&in_reply_to_status_id=68414509013942270&in_reply_to=joelwitherspoon>
Reply<http://twitter.com/?status=@joelwitherspoon%20&in_reply_to_status_id=68414509013942270&in_reply_to=joelwitherspoon>
<http://twitter.com/?status=RT%20%40joelwitherspoon%3A%20For%20the%20Nintendo%20and%20Twitter%20lovers%20out%20there%3A%20The%20Fail%20Blooper.%20http%3A%2F%2Fwww.cubeecraft.com%2Fblog%2Ffail-blooper%2F>
Retweet<http://twitter.com/?status=RT%20%40joelwitherspoon%3A%20For%20the%20Nintendo%20and%20Twitter%20lovers%20out%20there%3A%20The%20Fail%20Blooper.%20http%3A%2F%2Fwww.cubeecraft.com%2Fblog%2Ffail-blooper%2F>
   13:37
May-11<http://twitter.com/joelwitherspoon/statuses/68414509013942270>
  Get this email app!
<http://www.wisestamp.com/apps/twitter?utm_source=extension&utm_medium=email&utm_term=twitter&utm_campaign=apps>

Signature powered by
<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>
WiseStamp<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>



On Sat, May 14, 2011 at 9:49 AM, Emil Christopher Melar
<typeof@gmail.com>wrote:
> On Sat, May 14, 2011 at 6:14 PM, Erwan RENIER
<erwan.renier@laposte.net>
> 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.
>
> My bridge setup is pretty standard. Speed is OK right after boot. But
> 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!
> --
> Emil Christopher Solli Melar
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Emil Christopher Melar

2011-May-14 17:03 UTC

head link

Re: [Xen-users] Slow networking problem in dom0

Yes. I noticed the same thing. I can do without IPV6. Maybe there''s
bridge
problem around this!
Do you know by any chance if I can disable IPv6 without booting in Ubuntu
10.10?

Thanks!

On Sat, May 14, 2011 at 6:54 PM, Joel Witherspoon <
joel.witherspoon@gmail.com> wrote:
> So,
> You''re running IPv6 and IPv4 on the same interface? Can you do
without
> IPv6?
>
>
> *Joel C. Witherspoon*
>
> (626) 502 - 7201
>
> joel.witherspoon@gmail.com
> My profiles: [image: LinkedIn]
<http://www.linkedin.com/in/jcwitherspoon> [image:
> Twitter] <http://www.twitter.com/joelwitherspoon>
>  [image: Twitter] <http://twitter.com/joelwitherspoon> Latest tweet:
For
> the Nintendo and Twitter lovers out there: The Fail Blooper.
> http://www.cubeecraft.com/blog/fail-blooper/
> Follow @joelwitherspoon <http://twitter.com/joelwitherspoon>
>
<http://twitter.com/?status=@joelwitherspoon%20&in_reply_to_status_id=68414509013942270&in_reply_to=joelwitherspoon>
>
Reply<http://twitter.com/?status=@joelwitherspoon%20&in_reply_to_status_id=68414509013942270&in_reply_to=joelwitherspoon>
>
<http://twitter.com/?status=RT%20%40joelwitherspoon%3A%20For%20the%20Nintendo%20and%20Twitter%20lovers%20out%20there%3A%20The%20Fail%20Blooper.%20http%3A%2F%2Fwww.cubeecraft.com%2Fblog%2Ffail-blooper%2F>
>
Retweet<http://twitter.com/?status=RT%20%40joelwitherspoon%3A%20For%20the%20Nintendo%20and%20Twitter%20lovers%20out%20there%3A%20The%20Fail%20Blooper.%20http%3A%2F%2Fwww.cubeecraft.com%2Fblog%2Ffail-blooper%2F>
>    13:37
May-11<http://twitter.com/joelwitherspoon/statuses/68414509013942270>
>   Get this email app!
<http://www.wisestamp.com/apps/twitter?utm_source=extension&utm_medium=email&utm_term=twitter&utm_campaign=apps>
>
> Signature powered by
>
<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>
>
WiseStamp<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>
>
>
>
> On Sat, May 14, 2011 at 9:49 AM, Emil Christopher Melar
<typeof@gmail.com>wrote:
>
>> On Sat, May 14, 2011 at 6:14 PM, Erwan RENIER
<erwan.renier@laposte.net>
>> 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.
>>
>> My bridge setup is pretty standard. Speed is OK right after boot. But
>> 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!
>> --
>> Emil Christopher Solli Melar
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
>>
>
>

-- 
Emil Christopher Solli Melar


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Joel Witherspoon

2011-May-14 17:16 UTC

head link

Re: [Xen-users] Slow networking problem in dom0

I''m not sure what you mean by "without booting".

*Joel C. Witherspoon*

(626) 502 - 7201

joel.witherspoon@gmail.com
My profiles: [image: LinkedIn]
<http://www.linkedin.com/in/jcwitherspoon> [image:
Twitter] <http://www.twitter.com/joelwitherspoon>
[image: Twitter] <http://twitter.com/joelwitherspoon>Latest tweet: For the
Nintendo and Twitter lovers out there: The Fail Blooper.
http://www.cubeecraft.com/blog/fail-blooper/
Follow @joelwitherspoon <http://twitter.com/joelwitherspoon>
<http://twitter.com/?status=@joelwitherspoon%20&in_reply_to_status_id=68414509013942270&in_reply_to=joelwitherspoon>
Reply<http://twitter.com/?status=@joelwitherspoon%20&in_reply_to_status_id=68414509013942270&in_reply_to=joelwitherspoon>
<http://twitter.com/?status=RT%20%40joelwitherspoon%3A%20For%20the%20Nintendo%20and%20Twitter%20lovers%20out%20there%3A%20The%20Fail%20Blooper.%20http%3A%2F%2Fwww.cubeecraft.com%2Fblog%2Ffail-blooper%2F>
Retweet<http://twitter.com/?status=RT%20%40joelwitherspoon%3A%20For%20the%20Nintendo%20and%20Twitter%20lovers%20out%20there%3A%20The%20Fail%20Blooper.%20http%3A%2F%2Fwww.cubeecraft.com%2Fblog%2Ffail-blooper%2F>
   13:37
May-11<http://twitter.com/joelwitherspoon/statuses/68414509013942270>
  Get this email app!
<http://www.wisestamp.com/apps/twitter?utm_source=extension&utm_medium=email&utm_term=twitter&utm_campaign=apps>

Signature powered by
<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>
WiseStamp<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>



On Sat, May 14, 2011 at 10:03 AM, Emil Christopher Melar
<typeof@gmail.com>wrote:
> Yes. I noticed the same thing. I can do without IPV6. Maybe
there''s bridge
> problem around this!
> Do you know by any chance if I can disable IPv6 without booting in Ubuntu
> 10.10?
>
> Thanks!
>
>
> On Sat, May 14, 2011 at 6:54 PM, Joel Witherspoon <
> joel.witherspoon@gmail.com> wrote:
>
>> So,
>> You''re running IPv6 and IPv4 on the same interface? Can you do
without
>> IPv6?
>>
>>
>> *Joel C. Witherspoon*
>>
>> (626) 502 - 7201
>>
>> joel.witherspoon@gmail.com
>> My profiles: [image: LinkedIn]
<http://www.linkedin.com/in/jcwitherspoon> [image:
>> Twitter] <http://www.twitter.com/joelwitherspoon>
>>  [image: Twitter] <http://twitter.com/joelwitherspoon> Latest
tweet: For
>> the Nintendo and Twitter lovers out there: The Fail Blooper.
>> http://www.cubeecraft.com/blog/fail-blooper/
>> Follow @joelwitherspoon <http://twitter.com/joelwitherspoon>
>>
<http://twitter.com/?status=@joelwitherspoon%20&in_reply_to_status_id=68414509013942270&in_reply_to=joelwitherspoon>
>>
Reply<http://twitter.com/?status=@joelwitherspoon%20&in_reply_to_status_id=68414509013942270&in_reply_to=joelwitherspoon>
>>
<http://twitter.com/?status=RT%20%40joelwitherspoon%3A%20For%20the%20Nintendo%20and%20Twitter%20lovers%20out%20there%3A%20The%20Fail%20Blooper.%20http%3A%2F%2Fwww.cubeecraft.com%2Fblog%2Ffail-blooper%2F>
>>
Retweet<http://twitter.com/?status=RT%20%40joelwitherspoon%3A%20For%20the%20Nintendo%20and%20Twitter%20lovers%20out%20there%3A%20The%20Fail%20Blooper.%20http%3A%2F%2Fwww.cubeecraft.com%2Fblog%2Ffail-blooper%2F>
>>    13:37
May-11<http://twitter.com/joelwitherspoon/statuses/68414509013942270>
>>   Get this email app!
<http://www.wisestamp.com/apps/twitter?utm_source=extension&utm_medium=email&utm_term=twitter&utm_campaign=apps>
>>
>> Signature powered by
>>
<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>
>>
WiseStamp<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>
>>
>>
>>
>> On Sat, May 14, 2011 at 9:49 AM, Emil Christopher Melar
<typeof@gmail.com
>> > wrote:
>>
>>> On Sat, May 14, 2011 at 6:14 PM, Erwan RENIER
<erwan.renier@laposte.net>
>>> 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.
>>>
>>> My bridge setup is pretty standard. Speed is OK right after boot.
But
>>> 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!
>>> --
>>> Emil Christopher Solli Melar
>>>
>>> _______________________________________________
>>> Xen-users mailing list
>>> Xen-users@lists.xensource.com
>>> http://lists.xensource.com/xen-users
>>>
>>
>>
>
>
> --
> Emil Christopher Solli Melar
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Erwan RENIER

2011-May-14 17:25 UTC

head link

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?
>
> *Joel C. Witherspoon*
>
> (626) 502 - 7201
>
> joel.witherspoon@gmail.com <mailto:joel.witherspoon@gmail.com>
>
> My profiles: LinkedIn <http://www.linkedin.com/in/jcwitherspoon> 
> Twitter <http://www.twitter.com/joelwitherspoon>
> Twitter <http://twitter.com/joelwitherspoon> 	Latest tweet: For the 
> Nintendo and Twitter lovers out there: The Fail Blooper. 
> http://www.cubeecraft.com/blog/fail-blooper/
> Follow @joelwitherspoon <http://twitter.com/joelwitherspoon> 
>
<http://twitter.com/?status=@joelwitherspoon%20&in_reply_to_status_id=68414509013942270&in_reply_to=joelwitherspoon>
> Reply 
>
<http://twitter.com/?status=@joelwitherspoon%20&in_reply_to_status_id=68414509013942270&in_reply_to=joelwitherspoon>
>
<http://twitter.com/?status=RT%20%40joelwitherspoon%3A%20For%20the%20Nintendo%20and%20Twitter%20lovers%20out%20there%3A%20The%20Fail%20Blooper.%20http%3A%2F%2Fwww.cubeecraft.com%2Fblog%2Ffail-blooper%2F>
> Retweet 
>
<http://twitter.com/?status=RT%20%40joelwitherspoon%3A%20For%20the%20Nintendo%20and%20Twitter%20lovers%20out%20there%3A%20The%20Fail%20Blooper.%20http%3A%2F%2Fwww.cubeecraft.com%2Fblog%2Ffail-blooper%2F>
> 13:37 May-11 
> <http://twitter.com/joelwitherspoon/statuses/68414509013942270>
>
> Get this email app! 
>
<http://www.wisestamp.com/apps/twitter?utm_source=extension&utm_medium=email&utm_term=twitter&utm_campaign=apps>
>
> Signature powered by 
>
<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>WiseStamp
>
<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>
>
>
>
> On Sat, May 14, 2011 at 9:49 AM, Emil Christopher Melar 
> <typeof@gmail.com <mailto:typeof@gmail.com>> wrote:
>
>     On Sat, May 14, 2011 at 6:14 PM, Erwan RENIER
>     <erwan.renier@laposte.net
<mailto:erwan.renier@laposte.net>> 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.
>
>     My bridge setup is pretty standard. Speed is OK right after boot. But
>     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 <tel:705262%20%28705.2> KB)  TX
>     bytes:705262 (705.2 <tel:705262%20%28705.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!
>     --
>     Emil Christopher Solli Melar
>
>     _______________________________________________
>     Xen-users mailing list
>     Xen-users@lists.xensource.com
<mailto:Xen-users@lists.xensource.com>
>     http://lists.xensource.com/xen-users
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Emil Christopher Melar

2011-May-14 17:35 UTC

head link

Re: [Xen-users] Slow networking problem in dom0

I mean disabling IPv6 without booting the linux machine for the changes to
take effect. I have applied them in sysconf, and I guess I have to boot.

On Sat, May 14, 2011 at 7:16 PM, Joel Witherspoon <
joel.witherspoon@gmail.com> wrote:
> I''m not sure what you mean by "without booting".
>
>
> *Joel C. Witherspoon*
>
> (626) 502 - 7201
>
> joel.witherspoon@gmail.com
> My profiles: [image: LinkedIn]
<http://www.linkedin.com/in/jcwitherspoon> [image:
> Twitter] <http://www.twitter.com/joelwitherspoon>
>  [image: Twitter] <http://twitter.com/joelwitherspoon> Latest tweet:
For
> the Nintendo and Twitter lovers out there: The Fail Blooper.
> http://www.cubeecraft.com/blog/fail-blooper/
> Follow @joelwitherspoon <http://twitter.com/joelwitherspoon>
>
<http://twitter.com/?status=@joelwitherspoon%20&in_reply_to_status_id=68414509013942270&in_reply_to=joelwitherspoon>
>
Reply<http://twitter.com/?status=@joelwitherspoon%20&in_reply_to_status_id=68414509013942270&in_reply_to=joelwitherspoon>
>
<http://twitter.com/?status=RT%20%40joelwitherspoon%3A%20For%20the%20Nintendo%20and%20Twitter%20lovers%20out%20there%3A%20The%20Fail%20Blooper.%20http%3A%2F%2Fwww.cubeecraft.com%2Fblog%2Ffail-blooper%2F>
>
Retweet<http://twitter.com/?status=RT%20%40joelwitherspoon%3A%20For%20the%20Nintendo%20and%20Twitter%20lovers%20out%20there%3A%20The%20Fail%20Blooper.%20http%3A%2F%2Fwww.cubeecraft.com%2Fblog%2Ffail-blooper%2F>
>    13:37
May-11<http://twitter.com/joelwitherspoon/statuses/68414509013942270>
>   Get this email app!
<http://www.wisestamp.com/apps/twitter?utm_source=extension&utm_medium=email&utm_term=twitter&utm_campaign=apps>
>
> Signature powered by
>
<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>
>
WiseStamp<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>
>
>
>
> On Sat, May 14, 2011 at 10:03 AM, Emil Christopher Melar
<typeof@gmail.com
> > wrote:
>
>> Yes. I noticed the same thing. I can do without IPV6. Maybe
there''s bridge
>> problem around this!
>> Do you know by any chance if I can disable IPv6 without booting in
Ubuntu
>> 10.10?
>>
>> Thanks!
>>
>>
>> On Sat, May 14, 2011 at 6:54 PM, Joel Witherspoon <
>> joel.witherspoon@gmail.com> wrote:
>>
>>> So,
>>> You''re running IPv6 and IPv4 on the same interface? Can
you do without
>>> IPv6?
>>>
>>>
>>> *Joel C. Witherspoon*
>>>
>>> (626) 502 - 7201
>>>
>>> joel.witherspoon@gmail.com
>>> My profiles: [image:
LinkedIn]<http://www.linkedin.com/in/jcwitherspoon> [image:
>>> Twitter] <http://www.twitter.com/joelwitherspoon>
>>>  [image: Twitter] <http://twitter.com/joelwitherspoon> Latest
tweet: For
>>> the Nintendo and Twitter lovers out there: The Fail Blooper.
>>> http://www.cubeecraft.com/blog/fail-blooper/
>>> Follow @joelwitherspoon <http://twitter.com/joelwitherspoon>
>>>
<http://twitter.com/?status=@joelwitherspoon%20&in_reply_to_status_id=68414509013942270&in_reply_to=joelwitherspoon>
>>>
Reply<http://twitter.com/?status=@joelwitherspoon%20&in_reply_to_status_id=68414509013942270&in_reply_to=joelwitherspoon>
>>>
<http://twitter.com/?status=RT%20%40joelwitherspoon%3A%20For%20the%20Nintendo%20and%20Twitter%20lovers%20out%20there%3A%20The%20Fail%20Blooper.%20http%3A%2F%2Fwww.cubeecraft.com%2Fblog%2Ffail-blooper%2F>
>>>
Retweet<http://twitter.com/?status=RT%20%40joelwitherspoon%3A%20For%20the%20Nintendo%20and%20Twitter%20lovers%20out%20there%3A%20The%20Fail%20Blooper.%20http%3A%2F%2Fwww.cubeecraft.com%2Fblog%2Ffail-blooper%2F>
>>>    13:37
May-11<http://twitter.com/joelwitherspoon/statuses/68414509013942270>
>>>   Get this email app!
<http://www.wisestamp.com/apps/twitter?utm_source=extension&utm_medium=email&utm_term=twitter&utm_campaign=apps>
>>>
>>> Signature powered by
>>>
<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>
>>>
WiseStamp<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>
>>>
>>>
>>>
>>> On Sat, May 14, 2011 at 9:49 AM, Emil Christopher Melar <
>>> typeof@gmail.com> wrote:
>>>
>>>> On Sat, May 14, 2011 at 6:14 PM, Erwan RENIER
<erwan.renier@laposte.net>
>>>> 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.
>>>>
>>>> My bridge setup is pretty standard. Speed is OK right after
boot. But
>>>> 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!
>>>> --
>>>> Emil Christopher Solli Melar
>>>>
>>>> _______________________________________________
>>>> Xen-users mailing list
>>>> Xen-users@lists.xensource.com
>>>> http://lists.xensource.com/xen-users
>>>>
>>>
>>>
>>
>>
>> --
>> Emil Christopher Solli Melar
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
>>
>
>

-- 
Emil Christopher Solli Melar


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Emil Christopher Melar

2011-May-27 15:02 UTC

head link

Re: [Xen-users] Slow networking problem in dom0

Switched off IPv6. No difference.

On Sat, May 14, 2011 at 6:54 PM, Joel Witherspoon <
joel.witherspoon@gmail.com> wrote:
> So,
> You''re running IPv6 and IPv4 on the same interface? Can you do
without
> IPv6?
>
>
> *Joel C. Witherspoon*
>
> (626) 502 - 7201
>
> joel.witherspoon@gmail.com
> My profiles: [image: LinkedIn]
<http://www.linkedin.com/in/jcwitherspoon> [image:
> Twitter] <http://www.twitter.com/joelwitherspoon>
>  [image: Twitter] <http://twitter.com/joelwitherspoon> Latest tweet:
For
> the Nintendo and Twitter lovers out there: The Fail Blooper.
> http://www.cubeecraft.com/blog/fail-blooper/
> Follow @joelwitherspoon <http://twitter.com/joelwitherspoon>
>
<http://twitter.com/?status=@joelwitherspoon%20&in_reply_to_status_id=68414509013942270&in_reply_to=joelwitherspoon>
>
Reply<http://twitter.com/?status=@joelwitherspoon%20&in_reply_to_status_id=68414509013942270&in_reply_to=joelwitherspoon>
>
<http://twitter.com/?status=RT%20%40joelwitherspoon%3A%20For%20the%20Nintendo%20and%20Twitter%20lovers%20out%20there%3A%20The%20Fail%20Blooper.%20http%3A%2F%2Fwww.cubeecraft.com%2Fblog%2Ffail-blooper%2F>
>
Retweet<http://twitter.com/?status=RT%20%40joelwitherspoon%3A%20For%20the%20Nintendo%20and%20Twitter%20lovers%20out%20there%3A%20The%20Fail%20Blooper.%20http%3A%2F%2Fwww.cubeecraft.com%2Fblog%2Ffail-blooper%2F>
>    13:37
May-11<http://twitter.com/joelwitherspoon/statuses/68414509013942270>
>   Get this email app!
<http://www.wisestamp.com/apps/twitter?utm_source=extension&utm_medium=email&utm_term=twitter&utm_campaign=apps>
>
> Signature powered by
>
<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>
>
WiseStamp<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>
>
>
>
> On Sat, May 14, 2011 at 9:49 AM, Emil Christopher Melar
<typeof@gmail.com>wrote:
>
>> On Sat, May 14, 2011 at 6:14 PM, Erwan RENIER
<erwan.renier@laposte.net>
>> 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.
>>
>> My bridge setup is pretty standard. Speed is OK right after boot. But
>> 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!
>> --
>> Emil Christopher Solli Melar
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
>>
>
>

-- 
Emil Christopher Solli Melar


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Emil Christopher Melar

2011-Jun-10 19:00 UTC

head link

Re: [Xen-users] Slow networking problem in dom0

I am now running the 2.6.32.40 kernel, but I  still use XEN 4.0.1. Still the
same problems.
However I discovered something:

dmesg:
[2011-06-10 19:31:48] irq 19: nobody cared (try booting with the
"irqpoll"
option)
[2011-06-10 19:31:48] Pid: 0, comm: swapper Not tainted 2.6.32.40 #1
[2011-06-10 19:31:48] Call Trace:
[2011-06-10 19:31:48]  <IRQ>  [<ffffffff810c14a2>]
__report_bad_irq+0x38/0x87
[2011-06-10 19:31:48]  [<ffffffff810c1603>] note_interrupt+0x112/0x177
[2011-06-10 19:31:48]  [<ffffffff810c1cbb>] handle_fasteoi_irq+0x97/0xbc
[2011-06-10 19:31:48]  [<ffffffff812f8b8d>]
__xen_evtchn_do_upcall+0x1bf/0x287
[2011-06-10 19:31:48]  [<ffffffff812f94c2>] xen_evtchn_do_upcall+0x32/0x47
[2011-06-10 19:31:48]  [<ffffffff8103de7e>]
xen_do_hypervisor_callback+0x1e/0x30
[2011-06-10 19:31:48]  <EOI>  [<ffffffff810093aa>] ?
hypercall_page+0x3aa/0x1000
[2011-06-10 19:31:48]  [<ffffffff810093aa>] ? hypercall_page+0x3aa/0x1000
[2011-06-10 19:31:48]  [<ffffffff810093aa>] ? hypercall_page+0x3aa/0x1000
[2011-06-10 19:31:48]  [<ffffffff81038d7b>] ? xen_safe_halt+0x10/0x1a
[2011-06-10 19:31:48]  [<ffffffff81044127>] ? default_idle+0x3f/0x6a
[2011-06-10 19:31:48]  [<ffffffff8103bde6>] ? cpu_idle+0x66/0xa4
[2011-06-10 19:31:48]  [<ffffffff81602249>] ? rest_init+0x6d/0x6f
[2011-06-10 19:31:48]  [<ffffffff81a18dd5>] ? start_kernel+0x43c/0x447
[2011-06-10 19:31:48]  [<ffffffff81a182c1>] ?
x86_64_start_reservations+0xac/0xb0
[2011-06-10 19:31:48]  [<ffffffff81a1caca>] ? xen_start_kernel+0x5b7/0x5be
[2011-06-10 19:31:48] handlers:
[2011-06-10 19:31:48] [<ffffffff813b5ff4>] (e1000_intr+0x0/0xf7)
[2011-06-10 19:31:48] Disabling IRQ #19

After this, it goes slow. I tried disabling everything I could (onboard NIC)
but nothing happens. I  also tried irqpoll in kernel params.
e1000 happens to be my intel NIC which I use.


On Sat, May 14, 2011 at 6:54 PM, Joel Witherspoon <
joel.witherspoon@gmail.com> wrote:
> So,
> You''re running IPv6 and IPv4 on the same interface? Can you do
without
> IPv6?
>
>
> *Joel C. Witherspoon*
>
> (626) 502 - 7201
>
> joel.witherspoon@gmail.com
> My profiles: [image: LinkedIn]
<http://www.linkedin.com/in/jcwitherspoon> [image:
> Twitter] <http://www.twitter.com/joelwitherspoon>
>  [image: Twitter] <http://twitter.com/joelwitherspoon> Latest tweet:
For
> the Nintendo and Twitter lovers out there: The Fail Blooper.
> http://www.cubeecraft.com/blog/fail-blooper/
> Follow @joelwitherspoon <http://twitter.com/joelwitherspoon>
>
<http://twitter.com/?status=@joelwitherspoon%20&in_reply_to_status_id=68414509013942270&in_reply_to=joelwitherspoon>
>
Reply<http://twitter.com/?status=@joelwitherspoon%20&in_reply_to_status_id=68414509013942270&in_reply_to=joelwitherspoon>
>
<http://twitter.com/?status=RT%20%40joelwitherspoon%3A%20For%20the%20Nintendo%20and%20Twitter%20lovers%20out%20there%3A%20The%20Fail%20Blooper.%20http%3A%2F%2Fwww.cubeecraft.com%2Fblog%2Ffail-blooper%2F>
>
Retweet<http://twitter.com/?status=RT%20%40joelwitherspoon%3A%20For%20the%20Nintendo%20and%20Twitter%20lovers%20out%20there%3A%20The%20Fail%20Blooper.%20http%3A%2F%2Fwww.cubeecraft.com%2Fblog%2Ffail-blooper%2F>
>    13:37
May-11<http://twitter.com/joelwitherspoon/statuses/68414509013942270>
>   Get this email app!
<http://www.wisestamp.com/apps/twitter?utm_source=extension&utm_medium=email&utm_term=twitter&utm_campaign=apps>
>
> Signature powered by
>
<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>
>
WiseStamp<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>
>
>
>
> On Sat, May 14, 2011 at 9:49 AM, Emil Christopher Melar
<typeof@gmail.com>wrote:
>
>> On Sat, May 14, 2011 at 6:14 PM, Erwan RENIER
<erwan.renier@laposte.net>
>> 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.
>>
>> My bridge setup is pretty standard. Speed is OK right after boot. But
>> 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!
>> --
>> Emil Christopher Solli Melar
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
>>
>
>

-- 
Emil Christopher Solli Melar


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Emil Christopher Melar

2011-Jun-14 14:21 UTC

head link

Re: [Xen-users] Slow networking problem in dom0

Tried swapping card slot. It got a different IRQ, but the problem remained.
It seems like XEN 4.0.1 has a problem with IRQ sharing on my H67 chipset.

I found a workaround:
http://lists.xensource.com/archives/html/xen-users/2006-06/msg00176.html
I now have ''noirqdebug'' as a kernel param, and it has been
fine for 24
hours. This is no ideal solution though.

On Fri, Jun 10, 2011 at 9:00 PM, Emil Christopher Melar
<typeof@gmail.com>wrote:
> I am now running the 2.6.32.40 kernel, but I  still use XEN 4.0.1. Still
> the same problems.
> However I discovered something:
>
> dmesg:
> [2011-06-10 19:31:48] irq 19: nobody cared (try booting with the
"irqpoll"
> option)
> [2011-06-10 19:31:48] Pid: 0, comm: swapper Not tainted 2.6.32.40 #1
> [2011-06-10 19:31:48] Call Trace:
> [2011-06-10 19:31:48]  <IRQ>  [<ffffffff810c14a2>]
> __report_bad_irq+0x38/0x87
> [2011-06-10 19:31:48]  [<ffffffff810c1603>]
note_interrupt+0x112/0x177
> [2011-06-10 19:31:48]  [<ffffffff810c1cbb>]
handle_fasteoi_irq+0x97/0xbc
> [2011-06-10 19:31:48]  [<ffffffff812f8b8d>]
> __xen_evtchn_do_upcall+0x1bf/0x287
> [2011-06-10 19:31:48]  [<ffffffff812f94c2>]
xen_evtchn_do_upcall+0x32/0x47
> [2011-06-10 19:31:48]  [<ffffffff8103de7e>]
> xen_do_hypervisor_callback+0x1e/0x30
> [2011-06-10 19:31:48]  <EOI>  [<ffffffff810093aa>] ?
> hypercall_page+0x3aa/0x1000
> [2011-06-10 19:31:48]  [<ffffffff810093aa>] ?
hypercall_page+0x3aa/0x1000
> [2011-06-10 19:31:48]  [<ffffffff810093aa>] ?
hypercall_page+0x3aa/0x1000
> [2011-06-10 19:31:48]  [<ffffffff81038d7b>] ? xen_safe_halt+0x10/0x1a
> [2011-06-10 19:31:48]  [<ffffffff81044127>] ? default_idle+0x3f/0x6a
> [2011-06-10 19:31:48]  [<ffffffff8103bde6>] ? cpu_idle+0x66/0xa4
> [2011-06-10 19:31:48]  [<ffffffff81602249>] ? rest_init+0x6d/0x6f
> [2011-06-10 19:31:48]  [<ffffffff81a18dd5>] ?
start_kernel+0x43c/0x447
> [2011-06-10 19:31:48]  [<ffffffff81a182c1>] ?
> x86_64_start_reservations+0xac/0xb0
> [2011-06-10 19:31:48]  [<ffffffff81a1caca>] ?
xen_start_kernel+0x5b7/0x5be
> [2011-06-10 19:31:48] handlers:
> [2011-06-10 19:31:48] [<ffffffff813b5ff4>] (e1000_intr+0x0/0xf7)
> [2011-06-10 19:31:48] Disabling IRQ #19
>
> After this, it goes slow. I tried disabling everything I could (onboard
> NIC) but nothing happens. I  also tried irqpoll in kernel params.
> e1000 happens to be my intel NIC which I use.
>
>
> On Sat, May 14, 2011 at 6:54 PM, Joel Witherspoon <
> joel.witherspoon@gmail.com> wrote:
>
>> So,
>> You''re running IPv6 and IPv4 on the same interface? Can you do
without
>> IPv6?
>>
>>
>> *Joel C. Witherspoon*
>>
>> (626) 502 - 7201
>>
>> joel.witherspoon@gmail.com
>> My profiles: [image: LinkedIn]
<http://www.linkedin.com/in/jcwitherspoon> [image:
>> Twitter] <http://www.twitter.com/joelwitherspoon>
>>  [image: Twitter] <http://twitter.com/joelwitherspoon> Latest
tweet: For
>> the Nintendo and Twitter lovers out there: The Fail Blooper.
>> http://www.cubeecraft.com/blog/fail-blooper/
>> Follow @joelwitherspoon <http://twitter.com/joelwitherspoon>
>>
<http://twitter.com/?status=@joelwitherspoon%20&in_reply_to_status_id=68414509013942270&in_reply_to=joelwitherspoon>
>>
Reply<http://twitter.com/?status=@joelwitherspoon%20&in_reply_to_status_id=68414509013942270&in_reply_to=joelwitherspoon>
>>
<http://twitter.com/?status=RT%20%40joelwitherspoon%3A%20For%20the%20Nintendo%20and%20Twitter%20lovers%20out%20there%3A%20The%20Fail%20Blooper.%20http%3A%2F%2Fwww.cubeecraft.com%2Fblog%2Ffail-blooper%2F>
>>
Retweet<http://twitter.com/?status=RT%20%40joelwitherspoon%3A%20For%20the%20Nintendo%20and%20Twitter%20lovers%20out%20there%3A%20The%20Fail%20Blooper.%20http%3A%2F%2Fwww.cubeecraft.com%2Fblog%2Ffail-blooper%2F>
>>    13:37
May-11<http://twitter.com/joelwitherspoon/statuses/68414509013942270>
>>   Get this email app!
<http://www.wisestamp.com/apps/twitter?utm_source=extension&utm_medium=email&utm_term=twitter&utm_campaign=apps>
>>
>> Signature powered by
>>
<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>
>>
WiseStamp<http://www.wisestamp.com/email-install?utm_source=extension&utm_medium=email&utm_campaign=footer>
>>
>>
>>
>> On Sat, May 14, 2011 at 9:49 AM, Emil Christopher Melar
<typeof@gmail.com
>> > wrote:
>>
>>> On Sat, May 14, 2011 at 6:14 PM, Erwan RENIER
<erwan.renier@laposte.net>
>>> 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.
>>>
>>> My bridge setup is pretty standard. Speed is OK right after boot.
But
>>> 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!
>>> --
>>> Emil Christopher Solli Melar
>>>
>>> _______________________________________________
>>> Xen-users mailing list
>>> Xen-users@lists.xensource.com
>>> http://lists.xensource.com/xen-users
>>>
>>
>>
>
>
> --
> Emil Christopher Solli Melar
>


-- 
Emil Christopher Solli Melar


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Xen users - Apr 2011 - Slow networking problem in dom0

[Xen-users] Slow networking problem in dom0

Re: [Xen-users] Slow networking problem in dom0

Re: [Xen-users] Slow networking problem in dom0

Re: [Xen-users] Slow networking problem in dom0

Re: [Xen-users] Slow networking problem in dom0

Re: [Xen-users] Slow networking problem in dom0

Re: [Xen-users] Slow networking problem in dom0

Re: [Xen-users] Slow networking problem in dom0

Re: [Xen-users] Slow networking problem in dom0

Re: [Xen-users] Slow networking problem in dom0

Re: [Xen-users] Slow networking problem in dom0

Re: [Xen-users] Slow networking problem in dom0

Re: [Xen-users] Slow networking problem in dom0

Re: [Xen-users] Slow networking problem in dom0

Re: [Xen-users] Slow networking problem in dom0

Re: [Xen-users] Slow networking problem in dom0

Re: [Xen-users] Slow networking problem in dom0

Re: [Xen-users] Slow networking problem in dom0