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] domains not shutting down properly -theproblemisbackagai

To: James Harper <james.harper@xxxxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] domains not shutting down properly -theproblemisbackagain
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Fri, 02 Jan 2009 15:31:55 +0000
Cc:
Delivery-date: Fri, 02 Jan 2009 07:32:15 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D01550177@trantor>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AclsEUiDJwnrGfQLQ6G5Bsw4GM+wzgAAL2RgAAIdJkkAHEzXYAAA9a8QAAD1UUAACaHcAAABmirxAAEexXAAAH2McAAAGpUAAAH94BAAAdTsvgABrLdgAASGj2I=
Thread-topic: [Xen-devel] domains not shutting down properly -theproblemisbackagain
User-agent: Microsoft-Entourage/12.15.0.081119
On 02/01/2009 13:27, "James Harper" <james.harper@xxxxxxxxxxxxxxxx> 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



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

<Prev in Thread] Current Thread [Next in Thread>