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-users

[Xen-users] File server in domU dies on heavy traffic

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] File server in domU dies on heavy traffic
From: Itai Tavor <itai@xxxxxxxxx>
Date: Fri, 14 Jul 2006 16:20:29 +1000
Delivery-date: Thu, 13 Jul 2006 23:21:23 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi,

Got a very painful problem with my Xen 3 setup... I can run 6-7 guests fairly stably, but as soon as traffic to the file server guest picks up, it dies (guest console message below). I've seen this happen with NFS and SCP traffic and it's very consistent. After that, networking to/from all guests is gone, until the host is rebooted.

The setup is:

AMD Athlon64, Nforce 4 chipset, Marvel Yukon gigabit ethernet, xen- unstable from 7/4/06, Debian sarge amd64 on host and guests, shoe size 8.5.

Any ideas?

TIA, Itai



Unable to handle kernel NULL pointer dereference at 000000000000017e RIP:
<ffffffff80257bfd>{network_tx_buf_gc+253}
PGD aeb2067 PUD aeb3067 PMD 0
Oops: 0002 [1]
CPU 0
Modules linked in: ipv6 nfsd xfs exportfs
Pid: 0, comm: swapper Not tainted 2.6.16.13-xenU #2
RIP: e030:[<ffffffff80257bfd>] <ffffffff80257bfd>{network_tx_buf_gc+253}
RSP: e02b:ffffffff80399718  EFLAGS: 00010092
RAX: 00000000000000c1 RBX: 00000000000000b6 RCX: 0000000000000000
RDX: 0000000000000000 RSI: 0000000000000000 RDI: ffff880000451550
RBP: 00000000000000ba R08: 0000000000000000 R09: 0000000000000001
R10: 0000000000000000 R11: 0000000000000246 R12: ffff8800004503e0
R13: 00000000000164ec R14: 0000000000016502 R15: ffff880000450540
FS: 00002ac5d8e746d0(0000) GS:ffffffff803cb000(0000) knlGS: 0000000000000000
CS:  e033 DS: 0000 ES: 0000
Process swapper (pid: 0, threadinfo ffffffff803d6000, task ffffffff803337a0) Stack: ffff880000450000 0000000000000000 ffff880000450000 ffff8800004503e0 0000000000000106 0000000000000000 ffffffff803d7ec8 ffffffff802588b4
       ffff880009b2d740 0000000000000000
Call Trace: <IRQ> <ffffffff802588b4>{netif_int+52} <ffffffff8014776d> {handle_IRQ_event+61}
       <ffffffff80147820>{__do_IRQ+112} <ffffffff8010d461>{do_IRQ+65}
<ffffffff8024cab8>{evtchn_do_upcall+136} <ffffffff8010b416> {do_hypervisor_callback+30} <EOI> <ffffffff801073aa>{hypercall_page+938} <ffffffff801073aa> {hypercall_page+938}
       <ffffffff8010f4fd>{safe_halt+29} <ffffffff80108b45>{xen_idle+85}
<ffffffff80108b95>{cpu_idle+53} <ffffffff803d983a> {start_kernel+426}
       <ffffffff803d91ff>{x86_64_start_kernel+351}

Code: ff 8d c4 00 00 00 0f 94 c0 84 c0 74 46 48 8b 05 af cb 0d 00
RIP <ffffffff80257bfd>{network_tx_buf_gc+253} RSP <ffffffff80399718>
CR2: 000000000000017e
<0>Kernel panic - not syncing: Aiee, killing interrupt handler!

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] File server in domU dies on heavy traffic, Itai Tavor <=