From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Bainbridge Subject: Re: xen.xend.XendProtocol.XendError: Exception: invalid reason:halt Date: Sat, 1 Oct 2005 15:46:17 +0000 Message-ID: <623652d50510010846r27a426f3m@mail.gmail.com> References: <623652d50509301005h16138dc8n@mail.gmail.com> <20051001103638.GA11498@uk.xensource.com> Reply-To: Chris Bainbridge Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20051001103638.GA11498@uk.xensource.com> Content-Disposition: inline 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 List-Id: xen-devel@lists.xenproject.org On 01/10/05, Ewan Mellor wrote: > On Fri, Sep 30, 2005 at 06:05:51PM +0100, Chris Bainbridge wrote: > > > With current xen-unstable. Looks like some kind of argument parsing pro= blem? > > > > # 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 ar= e you > using? I always see 'poweroff' as the reason, not 'halt'. I can fix tha= t > easily, of course. I'm using a gentoo domU. Kernel and xen sources are a snapshot from 2 days ago. No shutdown was done in domU, I just run "xm shutdown --all --wait --halt " in domain 0.