From mboxrd@z Thu Jan  1 00:00:00 1970
From: Keir Fraser <keir.fraser@eu.citrix.com>
Subject: Re: domains not shutting down properly
	-theproblemisbackagain
Date: Fri, 02 Jan 2009 15:31:55 +0000
Message-ID: <C583E3EB.20ADF%keir.fraser@eu.citrix.com>
References: <AEC6C66638C05B468B556EA548C1A77D01550177@trantor>
Mime-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D01550177@trantor>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: James Harper <james.harper@bendigoit.com.au>, xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

On 02/01/2009 13:27, "James Harper" <james.harper@bendigoit.com.au> wrote:

> I added some debugging to the send_guest_global_virq code path too, but
> as soon as the DomU I created for testing shut down, my Dom0 became
> unresponsive so I suspect I have botched my debug statements. It's
> nearly 12:30am here and the server is at work so I'm done for the day.
> 
> The most frustrating thing is that I just know it's going to be some
> stupid little configuration thing on my server causing all of this!!!

Perhaps multiprocessor dom0, plus a bug in the dom0 kernel which means that
the VCPU which Xen notifies for the virq is not the one which dom0 kernel is
expecting to receive the notification to? What do you use as dom0 kernel?

 -- Keir