From owner-freebsd-xen@FreeBSD.ORG Tue Feb 10 19:40:12 2009 Return-Path: Delivered-To: freebsd-xen@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DECE5106564A; Tue, 10 Feb 2009 19:40:12 +0000 (UTC) (envelope-from kai@freshx.de) Received: from zim.freshx.de (zim.freshx.de [83.137.99.113]) by mx1.freebsd.org (Postfix) with ESMTP id 991BD8FC1D; Tue, 10 Feb 2009 19:40:12 +0000 (UTC) (envelope-from kai@freshx.de) Received: from localhost (localhost.localdomain [127.0.0.1]) by zim.freshx.de (Postfix) with ESMTP id 73BA78C017C; Tue, 10 Feb 2009 20:40:11 +0100 (CET) X-Virus-Scanned: amavisd-new at zim.freshx.de Received: from zim.freshx.de ([127.0.0.1]) by localhost (zim.freshx.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bDSwpcHVhi1D; Tue, 10 Feb 2009 20:40:09 +0100 (CET) Received: from [192.168.1.42] (55-218.76-83.cust.bluewin.ch [83.76.218.55]) by zim.freshx.de (Postfix) with ESMTP id B4A8E8C00F9; Tue, 10 Feb 2009 20:40:07 +0100 (CET) User-Agent: Microsoft-Entourage/12.15.0.081119 Date: Tue, 10 Feb 2009 20:40:05 +0100 From: Kai Mosebach To: Kip Macy , Kai Mosebach Message-ID: Thread-Topic: domU page faults under heavy network load Thread-Index: AcmLt18+DOqUwOc8akOm6ygRouDlaw== In-Reply-To: <3c1674c90902101130r58c05f07we473c0897fe29481@mail.gmail.com> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Cc: freebsd-xen Subject: Re: domU page faults under heavy network load X-BeenThere: freebsd-xen@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion of the freebsd port to xen - implementation and usage List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Feb 2009 19:40:13 -0000 1024meg On 2/10/09 8:30 PM, "Kip Macy" wrote: > How big is the memory allocation to the VM? > > Thanks, > Kip > > > On Tue, Feb 10, 2009 at 7:59 AM, Kai Mosebach wrote: >> Hi, >> >> running r188436M on Xen3.3.1 (Centos5, x86_64). The reason is not to clear >> but seems related to heavy load on pipes + memory + network? >> It is repeatable with : >> >> bsd8# dd if=/dev/zero | nc otherhost 12345 >> >> Fatal trap 12: page fault while in kernel mode >> cpuid = 0; apic id = 00 >> fault virtual address = 0xd216dd00 >> fault code = supervisor read, page not present >> instruction pointer = 0x21:0xc02e4d40 >> stack pointer = 0x29:0xc332aba8 >> frame pointer = 0x29:0xc332abfc >> code segment = base 0x0, limit 0xfffff, type 0x1b >> = DPL 1, pres 1, def32 1, gran 1 >> processor eflags = interrupt enabled, resume, IOPL = 0 >> current process = 12 (irq137: xn) >> [thread pid 12 tid 100025 ] >> Stopped at xlvbd_add+0x2f70: movl 0x900(%edx,%eax,4),%edx >> db> bt >> >> >> >> On otherhost i get some stuff (between 19 and 62 MB), after nc closes down >> eventually >> >> otherhost# nc -l 12345 | cpipe -vt -b 65535 >/dev/null >> ... >> thru: 108930.791ms at 184.3kB/s ( 184.3kB/s avg) 19.6MB >> >> best Kai >> _______________________________________________ >> freebsd-xen@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-xen >> To unsubscribe, send any mail to "freebsd-xen-unsubscribe@freebsd.org" >>