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

Re: [Xen-devel] refcount errors then crash on XenoLinux with the latest

To: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] refcount errors then crash on XenoLinux with the latest source
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Tue, 24 Feb 2004 08:35:33 +0000
Cc: Kip Macy <kmacy@xxxxxxxxxxx>, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 24 Feb 2004 08:39:38 +0000
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Tue, 24 Feb 2004 08:15:52 GMT." <E1AvXjN-00077j-00@xxxxxxxxxxxxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> > It happened again. Is it possible that Xen isn't disabling network
> > interrupts while it is "auditing all pages"?
> 
> Quite possibly. The auditing code was added fairly recently
> specifically to assist debugging of a guest OS that was
> internally 'leaking' references to pages.
> 
> Its not in any of the non-debug builds, and is not well
> tested. In the circumstance we were using it the problem with the
> guestOS was rather subtle and just a couple of pages were failing
> the audit and generating log messages. (The audit code gets
> called when the guest does something 'weird', or when you invoke
> the appropriate keyboard handler)
> 
> If your machine has lots of physical memory, the auditing will
> take some time, and I'm not surprised that its causing
> problems. If its not helping you, just comment it out, or invoke
> it via the keyboard handler when you want it.

In fact the auditing code is only ever invoked in response to keyboard
or serial input. Just avoid pressing the 'm' key. :-)

 -- Keir


-------------------------------------------------------
SF.Net is sponsored by: Speed Start Your Linux Apps Now.
Build and deploy apps & Web services for Linux with
a free DVD software kit from IBM. Click Now!
http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel