[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Network problem: packets are lost in domU



Hi,

> I am using Xen 3.0.4-1 and Linux 2.6.16.x in both dom0 and domU.
> I have tried kernel 2.6.16.35 and 2.6.16.41. 
> I have compiled the kernel and xen with PAE support and without it,
> using gcc 3.3 and gcc 4.2 (snapshot). I have played with various kernel
> compilation options. No luck: the same problem in every case.
> 
> [...]
>
> And there are errors in dmesg of domU for each package lost this way:
> 
> netfront: rx->offset: 12, size: 4294967295
> netfront: rx->offset: 12, size: 4294967295
> netfront: rx->offset: 12, size: 4294967295
> netfront: rx->offset: 12, size: 4294967295
> [...]
> 
> No other suspicious messages in dmesg of domU, nothing worying in dmesg
> of dom0.

I have the exact same problem. I just wanted to upgrade to 2.6.19 +
3.0.4 from the Fedora development and boom, same problem.

It works when I use my old Dom0 (2.6.18 + 3.0.3) with 3.0.4 guests. The
only visible difference is that with the new (broken) Dom0, the guests
are using the "copying receive path" while with the working old Dom0
they are using the "flipping receive path".

This smells like a serious bug in the netback or netfront driver in the
copying receive path.

I don't know what can trigger this, but my configuration is:

Dom0: xenbr0 with one netloop attached (int0) and several vif#.0 for
DomU's (no physical network card attached, done via routing on Dom0).

4294967295 is -1 writted as unsigned, which indicates some sort of error
state in the code, but I don't know from where that one might come.



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.