All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Bainbridge <chris.bainbridge@gmail.com>
To: Ewan Mellor <ewan@xensource.com>,
	xen-devel <xen-devel@lists.xensource.com>
Subject: Re: xen.xend.XendProtocol.XendError: Exception: invalid reason:halt
Date: Wed, 5 Oct 2005 15:45:46 +0100	[thread overview]
Message-ID: <623652d50510050745p206ae241i@mail.gmail.com> (raw)
In-Reply-To: <20051001103638.GA11498@uk.xensource.com>

On 01/10/05, Ewan Mellor <ewan@xensource.com> 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?

  parent reply	other threads:[~2005-10-05 14:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-30 17:05 xen.xend.XendProtocol.XendError: Exception: invalid reason:halt Chris Bainbridge
2005-10-01 10:36 ` Ewan Mellor
2005-10-01 15:46   ` Chris Bainbridge
2005-10-05 14:45   ` Chris Bainbridge [this message]
2005-10-05 15:03     ` Ewan Mellor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=623652d50510050745p206ae241i@mail.gmail.com \
    --to=chris.bainbridge@gmail.com \
    --cc=ewan@xensource.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.