From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ewan Mellor Subject: Re: xen.xend.XendProtocol.XendError: Exception: invalid reason:halt Date: Sat, 1 Oct 2005 11:36:38 +0100 Message-ID: <20051001103638.GA11498@uk.xensource.com> References: <623652d50509301005h16138dc8n@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <623652d50509301005h16138dc8n@mail.gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On Fri, Sep 30, 2005 at 06:05:51PM +0100, Chris Bainbridge wrote: > With current xen-unstable. Looks like some kind of argument parsing problem? > > # xm shutdown --wait --halt server2 > Traceback (most recent call last): > File "/usr/sbin/xm", line 10, in ? > main.main(sys.argv) > File "/usr/lib/python2.3/site-packages/xen/xm/main.py", line 703, in main > handle_xend_error(argv[1], args[0], ex) > File "/usr/lib/python2.3/site-packages/xen/xm/main.py", line 164, in > handle_xend_error > raise ex > xen.xend.XendProtocol.XendError: Exception: invalid reason:halt That's interesting -- how did you shut down the domain, and what guest are you using? I always see 'poweroff' as the reason, not 'halt'. I can fix that easily, of course. Ewan.