[Xen-users] Status of "4GB byte count overflow hangs networking"

[Frank Schubert <f.schubert@xxxxxxxxxxxx>]

Hi all,

I'm referring to an email to xen-users on Fri, 8 Dec 2006
where Dominic Hargreaves reports about tests with version 3.0.2 and 3.0.3.

He reported that with both version the 4GB byte count hang occurs.

Here is another site where S. Burke reported the same problem with version 
3.0.2-3:
http://wiki.kartbuilding.net/index.php/Ongoing_Experiences_with_Xen#16th_Jan_2007_Xen_Report

Currently I'm seeing the same problem with the official Xen 3.0.2-2 PAE kernel.

dom0 uptime is > 300days

The first domU hang occured at dom0 uptime between 280-290days.
Days 0-280 with the same domUs load and traffic without any error.

xentop:
    NAME  STATE   CPU(sec) CPU(%)     MEM(k) MEM(%)  MAXMEM(k) MAXMEM(%) VCPUS 
NETS NETTX(k) NETRX(k) SSID
          ds----      30865    0.0          8    0.0     131072       3.1     1 
   1  4194303  1221445    0
          d-b---       4303    0.0          8    0.0     524288      12.5     1 
   1  4194303  1349417    0
          ds----       3195    0.0          8    0.0     524288      12.5     1 
   1  4194303  1226187    0
          ds----       5606    0.0          8    0.0     524288      12.5     1 
   1  4194303   577034    0
          ds----       8948    0.0          8    0.0     524288      12.5     1 
   1  4194303   557577    0
 Domain-0 -----r     103478    0.3     257064    6.1   no limit       n/a     2 
   8  3560993  1609201    0
   vm01 --b---     157894    0.1    1048360   25.0    1048576      25.0     1   
 1   401137   499516    0
   vm02 --b---       4951    0.2     524136   12.5     524288      12.5     1   
 1  2583543   266227    0
   vm03 --b---     723872    0.1    1048428   25.0    1048576      25.0     1   
 1    73381  2813667    0
   vm04 --b---     114504    0.2     524068   12.5     524288      12.5     1   
 1  3004136  1557914    0
   vm05 --b---       2023    0.0     130896    3.1     131072       3.1     1   
 1   555819   123315    0

The first 5 are domUs in zombie-state. As you can see all hang at NETTX(k) 
4194303.

When a guest hangs:
xm console <domu> is possible, there i can shutdown the guest.
After that i can "xm create </etc/xen/domU>" the guest.

Now everything runs fine until the NETTX counter hits 4194303.

Is this fixed in 3.0.4 or is there a workaround?

Thanks in advance!
Frank Schubert

--
Frank Schubert
Systemadministration
EsPresto AG
Breite Str. 30-31
10178 Berlin/Germany
Tel: +49.(0)30.90 226.750
Fax: +49.(0)30.90 226.760
f.schubert@xxxxxxxxxxxx

HRB 77554 AG - Berlin-Charlottenburg
Vorstand: Alexander Biersack und Maya Biersack
Vorsitzender des Aufsichtsrats: Oli Kai Paulus

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