On 01/10/05, Ewan Mellor <ewan@xxxxxxxxxxxxx> 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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|