From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ewan Mellor Subject: Re: xen.xend.XendProtocol.XendError: Exception: invalid reason:halt Date: Wed, 5 Oct 2005 16:03:45 +0100 Message-ID: <20051005150345.GE21042@uk.xensource.com> References: <623652d50509301005h16138dc8n@mail.gmail.com> <20051001103638.GA11498@uk.xensource.com> <623652d50510050745p206ae241i@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <623652d50510050745p206ae241i@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 List-Id: xen-devel@lists.xenproject.org On Wed, Oct 05, 2005 at 03:45:46PM +0100, Chris Bainbridge wrote: > 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 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. > > Hi, did this get fixed? I was just looking at the latest > xmexample.vmx, xmexample1, xmexample2 and noticed that they don't > mention halt as a valid reason, just poweroff reboot and crash. Is > halt now treated the same as poweroff, or can these files be fixed > please? Halt means "poweroff and don't restart regardless of the configuration settings", so as far as those config files are concerned, halt is not a valid reason (i.e. you don't want to have an on_halt handler). I think what you want in normal use is just xm shutdown --wait server2, with on_poweroff set to the default (destroy). There's no need to specify --halt in normal use. The actual behaviour of --halt is less broken than it was before, so the problem that you experienced is now fixed, but --halt is still broken (bug #282). I'm working on that now. Ewan.