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] xm shutdown broke ...

To: Gerd Knorr <kraxel@xxxxxxx>
Subject: Re: [Xen-devel] xm shutdown broke ...
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Tue, 15 Nov 2005 23:39:34 +0000
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Tue, 15 Nov 2005 23:39:34 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <437A29CD.6050206@xxxxxxx>
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: <437A2521.3050904@xxxxxxx> <20051115182301.GE15386@xxxxxxxxxxxxxxxxxxxxxx> <437A29CD.6050206@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Tue, Nov 15, 2005 at 07:32:45PM +0100, Gerd Knorr wrote:

> Ewan Mellor wrote:
> >On Tue, Nov 15, 2005 at 07:12:49PM +0100, Gerd Knorr wrote:
> >
> >>  Hi,
> >>
> >>look here:
> >>
> >>  # /usr/sbin/xm shutdown -a -w
> >>  Error: Domain '-a' not found when running 'xm shutdown'
> >
> >Could you post your /var/log/xend.log?  Thanks.
> 
> Not right now, sorry.  The one where this happened is gone, and seems it 
> isn't trivially reproducable (looked like a simple command line parsing 
> bug, but appearently it isn't).

No, it's a diabolical error-reporting bug (#172, if anyone has the strength)
but that message indicates that one of the two XendError exceptions (no, really,
we have two separate exceptions, both called XendError) has been thrown, and
the string associated with the exception is "Not found".  You really do need
to look in the xend.log to discover what the real error is.

Ewan. 

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

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