WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Network drop on domU (netfront: rx->offset: 0, size: 429

To: xen-devel@xxxxxxxxxxxxxxxxxxx, M A Young <m.a.young@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Network drop on domU (netfront: rx->offset: 0, size: 4294967295)
From: Boris Derzhavets <bderzhavets@xxxxxxxxx>
Date: Wed, 10 Jun 2009 10:14:43 -0700 (PDT)
Cc:
Delivery-date: Wed, 10 Jun 2009 10:15:25 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1244654083; bh=uYGHUSMXIBj2OXPtUWhIdh5dYnCgbEAC1ngd5G4shoc=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=kfw7XBlri4vNXImfw1LKG/SpjCfglSOtSJRvOXeP3fyYEVTlN8Am2ylODY4gL+0GwGg54fPH2TOYbfzw3Fht1YjpmO5nEkwUuQoc8A+AAR0cxV0NmIVbuoH5a206WPrf0Uz+33LBhTMTs7lo3NNAiw4M8DdYcTYu5cl/Enqmjkc=
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=j1dOZ+G0WP54eN7x1QZIVNun65hkgt+NT2tNkqmyCsgCZSDUFMzuWQG3EG4MYBlJeQZp+Lp/SiiU7PAi2U5R8SjGGkt3XhuQH+i4qq/Yw/Fn4UBo7OtlWXW/WAvUZIQou++jGkLj9bPlX43XOBujtNxLC1BNyqmuTLCQ3oi3J2g=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
 F11 PV DomU running for about 1 hr at Xen 3.4.1 Dom0 (2.6.30-rc6-tip) , been built
on top of F11. During this time frame:-
1.  4GB ISO file scp'ed from Dom0 to DomU at 30 MB/sec
2.  Same file scp'ed from DomU to Dom0 at  17-24 MB/sec
"yum update" was running at DomU in parallel with both "scp" about 20-25 min and succeeded. File /var/log/messages captured and attached. It doesn't look to me to have network problems. However, speed of data transfer from DomU to Dom0 is noticable
lower then vice versa.

Hardware: Q9550,8GB RAM, SATA Drive 500 GB ( attached to ICH10R).
2 GB and 2 vcpus been allocated  for F11 DomU

--- On Thu, 5/28/09, M A Young <m.a.young@xxxxxxxxxxxx> wrote:

From: M A Young <m.a.young@xxxxxxxxxxxx>
Subject: [Xen-devel] Network drop on domU (netfront: rx->offset: 0, size: 4294967295)
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Date: Thursday, May 28, 2009, 6:02 PM

I have started to see this error as well now on a Fedora Rawhide + xen-tip/next dom0 kernel on Fedora 11 and a Fedora 11 domU. The base system has just been reinstalled and used to be running Fedora 8 dom0, the domU machine hasn't changed. This is on a fairly old machine with 512M memory shared between the two instances.

/var/log/messages is packed with errors like
net eth0: rx->offset: 0, size: 4294967295
with the more occasional
__ratelimit: 25 callbacks suppressed
about every 10 lines, while updating some packages using rpm where the packages are on an NFS mount, which is maybe running at 1/10th or less the speed than I would expect. The network setup on dom0 is

bridge name    bridge id        STP enabled    interfaces
eth0        8000.0011110a766f    no        peth0
                            vif4.0

with only a handful of dropped packets on vif4.0
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:524716 errors:0 dropped:0 overruns:0 frame:0
          TX packets:658136 errors:0 dropped:39 overruns:0 carrier:0
          collisions:0 txqueuelen:32
          RX bytes:36703881 (35.0 MiB)  TX bytes:862875521 (822.9 MiB)

On domU however ifconfig reports
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:567462 errors:73814 dropped:0 overruns:0 frame:0
          TX packets:511318 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:719940314 (686.5 MiB)  TX bytes:42982009 (40.9 MiB)
          Interrupt:9

I tried enabling debugging in drivers/xen/netback/netback.c by setting
#define NETBE_DEBUG_INTERRUPT
but when I try to build the kernel I get the error
drivers/xen/blkback/xenbus.c: In function 'blkif_xenbus_init':
drivers/xen/blkback/xenbus.c:541: warning: ignoring return value of 'xenbus_register_backend', declared with attribute warn_unused_result
drivers/xen/netback/netback.c: In function 'netback_init':
drivers/xen/netback/netback.c:1503: error: 'SA_SHIRQ' undeclared (first use in this function)
drivers/xen/netback/netback.c:1503: error: (Each undeclared identifier is reported only once
drivers/xen/netback/netback.c:1503: error: for each function it appears in.)
drivers/xen/netback/netback.c:1505: warning: passing argument 3 of 'bind_virq_to_irqhandler' from incompatible pointer type

    Michael Young

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

Attachment: var-log-messages-PV.gz
Description: GNU Zip compressed data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>