Xen devel - Sep 2005 - xen.xend.XendProtocol.XendError: Exception: invalid reason:halt

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

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

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.

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

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.
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.

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

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?

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

On Wed, Oct 05, 2005 at 03:45:46PM +0100, Chris Bainbridge wrote:
> 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?
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.

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