Re: 4GB byte count overflow hangs networking (was Re: [Xen-users] domUs dropping off the network (Xen 3.0.2))

[Steven Yelton <steveny@xxxxxxxxxxxxxxx>]

Dominic,

We are seeing this as well.  We were going to upgrade to 3.0.3 this 
weekend, but with what you are seeing this won't fix it (we are 
currently using xen-3.0.2-2).
Here are some other details on our hardware and configuration:

xm top:
     NAME  STATE   CPU(sec) CPU(%)     MEM(k) MEM(%)  MAXMEM(k) 
MAXMEM(%) VCPUS NETS NETTX(k) NETRX(k) SSID
          d-----      79276    0.0          8    0.0     393216       
6.3     1    1  4194303  1973846    0
          d-----       5462    0.0          8    0.0    1048576      
16.7     2    1  4194303   727438    0
          d-----       4653    0.0          8    0.0    1048576      
16.7     1    1  4194303   644714    0
          d-----       4843    0.0          8    0.0    1048576      
16.7     1    1  4194302   675675    0
          d-----       4244    0.0          8    0.0    1048576      
16.7     1    1  4194302   638509    0
          d-----       4886    0.0          8    0.0     786432      
12.5     1    1  4194303   691506    0
 Domain-0 -----r     106893    0.5     262272    4.2   no limit       
n/a     4    8  2991003  3711014    0
  domU1 --b---       1774    1.7     392788    6.2     393216       
6.3     1    2  2433841  1190900    0
domU2 --b---     220877    0.1     392780    6.2     393216       
6.3     1    2  4208965  3047409    0
  domU3 --b---      18591    0.0     392840    6.2     393216       
6.3     1    2  5759556   545256    0
    domU4 --b---       2060    0.1     786012   12.5     786432      
12.5     1    2  2579388  2731866    0

As you can see, domU3 is happily above 4G.  We see domU4 crash 
repeatedly, and domU1 has crashed once.  I wonder if it crashes once it 
will continue to do so.
We are running on a dell 2850 with PAE enabled.  The machine has been up 
for around 280 days.  We didn't start seeing the problem until it had 
been up about 240 days.  We were hoping an upgrade and/or a reboot would 
get us back to a good state.
Is there any other information I can give that can help track down this 
issue?  Has anyone found *any* workaround?
Thanks,
Steven





Dominic Hargreaves wrote:
> On Mon, Dec 04, 2006 at 03:57:10PM +0000, Dominic Hargreaves wrote:
>   
> > Hello,
> >
> > We've recently started seeing several domUs on multiple machines losing
> > all network connectivity. At least one of these machines (since they are
> > customer machines I can't verify it for all of them) give the error:
> >
> > $ sudo ifup eth0
> > eth0: full queue wasn't stopped!
> >     
> To follow up on this post: the problem happens when the number of bytes
> received by the vif on the dom0 side (and therefore transmitted by the
> domU) hits 4GB (or within a few kB thereof).
>
> In tests I have verified this against a Xen 3.0.2 system (although it
> doesn't always manifest, so perhaps there are other factors in place
> too), and have also verified that with Xen 3.0.3 it seems to happen less
> often.
>
> Cheers,
>
> Dominic.
>
>   
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users