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] xen_changeset : Mon Oct 3 05:26:29 2005 +0100 f22fba6731

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] xen_changeset : Mon Oct 3 05:26:29 2005 +0100 f22fba673196 updates 4k and 8 k kernel stacks
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Tue, 4 Oct 2005 08:21:09 +0100
Delivery-date: Tue, 04 Oct 2005 07:18:49 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1128358440.16758.92.camel@xxxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <1128358440.16758.92.camel@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Mon, Oct 03, 2005 at 12:54:00PM -0400, Ted Kaczmarek wrote:

> changeset:   7157:f22fba673196
> 
> #########################################
> FC4 dom0, Tyan 2462 SMP, 4k kernel stack
> #########################################
> 
> xm shutdown does not  work at all, always get the d flag , that d flag
> also seems to be the stopper for xm destroy as well.
> I have yet to be able to destroy a domain with the d flag.

The d flag is most likely a symptom of your problem, not a cause, as it
indicates that something is holding the domain open.  A broken driver might do
this, for example.  I don't expect xm destroy to be able to destroy a domain
with the d flag.  Domains with that flag have _already_ been destroyed, and it
is the broken whatever-it-is that is preventing final cleanup.

Since you are also having problems with the network drivers, I'd hazard a
guess that the brokenness there is causing the domain to hang around.

Cheers,

Ewan.

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

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