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/
Home Products Support Community News


Re: [Xen-devel] Tapdisk failures / kernel general protection fault at xe

To: Daniel Stodden <daniel.stodden@xxxxxxxxxx>
Subject: Re: [Xen-devel] Tapdisk failures / kernel general protection fault at xen 4.0.2rc3 / kernel pvops
From: Gerd Jakobovitsch <gerd@xxxxxxxxxxx>
Date: Thu, 14 Apr 2011 15:05:19 -0300
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Delivery-date: Thu, 14 Apr 2011 11:14:13 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1302803034.24534.24.camel@xxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4DA60F55.4000604@xxxxxxxxxxx> <20110414131543.GE5548@xxxxxxxxxxxx> <1302799089.24534.18.camel@xxxxxxxxxxxxxxxxxxxxxxx> <1302803034.24534.24.camel@xxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20110223 Lightning/1.0b2 Thunderbird/3.1.8
Hello Daniel:

I applied the patch and the bug at VM startup was solved. Thank you for your help.



On 04/14/2011 02:43 PM, Daniel Stodden wrote:
On Thu, 2011-04-14 at 12:38 -0400, Daniel Stodden wrote:
On Thu, 2011-04-14 at 09:15 -0400, Konrad Rzeszutek Wilk wrote:
On Wed, Apr 13, 2011 at 06:02:13PM -0300, Gerd Jakobovitsch wrote:
I'm trying to run several VMs (linux hvm, with tapdisk:aio disks at
a storage over nfs) on a CentOS system, using the up-to-date version
of xen 4.0 / kernel pvops 2.6.32.x stable. With a configuration
without (most of) debug activated, I can start several instances -
I'm running 7 of them - but shortly afterwards the system stops
responding. I can't find any information on this.
First time I see it.
Activating several debug configuration items, among them
DEBUG_PAGEALLOC, I get an exception as soon as I try to start up a
VM. The system reboots.
Oooh, and is the log below from that situation?

Daniel, any thoughs?
          Unmap pages from the kernel linear mapping after free_pages().
          This results in a large slowdown, but helps to find certain types
          of memory corruption.

Stunning. Our I/O page allocator is a sort of twisted mempool. Unless
the allocation is explicitly modified in sysfs/, everything should stay
pinned. We might be just tripping over debug code alone, but I didn't
figure it out yet.
Ah, that's just missing Dominic's spinlock fix.



Xen-devel mailing list