I wish it had to do with RTAS, but it does not.
The DomUs do not get an RTAS and power down by sending xen/xend a message
-JX
On Dec 12, 2006, at 6:56 PM, Maria Butrico wrote:

I just remembered a fact perhaps relevant to this. At some point in the past I applied a patch to the linux tree we ('we' is the community that is reporting this problem) use on xen which was forwarded to me by Jimi. The patch subject is: "[RFC/PATCH] Maple: Use RTAS power off methods if available". I applied this patch to make reboot possible. At the time, Nov 7th, I tested this change and (I am going by memory now) and I recall that it worked. When I regenerated the linux tree, after all the changes made to the base, I also tested, but I have _not_ been able to reboot. This seemed not too important at the time so I did not chase it. So I believe that the issue with xm shutdown reduces to why are we not able to reboot. Once more, if you let a bug go by, it becomes a monster.

On the subject of xm destroy, the domU libos is destroyed often, without any trouble. I will try to verify that we can do this more than once with domU linux. Sorry that this is taking so long, but with all the machine shuffles I lost agility in rebooting a particular image.
Doron Shiloach wrote:

Hi Jimi,

>> Please try executing "/sbin/poweroff" manually on the DomU and see if that works.

(none):/ # /sbin/poweroff
WARNING: could not determine runlevel - doing soft poweroff
(it's better to use shutdown instead of poweroff from the command line)
shutdown: /dev/initctl: No such file or directory
init: /dev/initctl: No such file or directory

I am using a custom init script with this domU, which from what you wrote previously, seems to not be creating a "real" init process, preventing the xm shutdown from working. What do you mean by a "real" init process? Is it possible for me to define init and still be able to use the shutdown command? As for the xm destroy, I mean that I can use the command once (usually) , and it works, removing that domU. However, when I try to use it on a second domU, the machine freezes. From what I understand, it is preferable to use the "shutdown" command, so this is a secondary issue, for me at least.. Thanks,


Doron Shiloach
Tieline: 862-3110
Phone: (914) 945-3110


*Jimi Xenidis/Watson/IBM*

12/07/2006 04:18 PM

        
To
        Doron Shiloach/Watson/[EMAIL PROTECTED]
cc
David M Daly/Watson/[EMAIL PROTECTED], Dilma M Da silva/Watson/[EMAIL PROTECTED], Maged Michael/Watson/[EMAIL PROTECTED]
Subject
Re: shutdown/destroy domU problemLink <Notes:// D01ML605/85256A9D0011A9FD/ ABA3A23F266A9ECE85257107007CB006/8077794957E643DF8525723D005C2A80>



        




Doron,
First, these are awesome questions for the mailing list and I wish you would use it, I've asked for this time and time again. Second, when you say "xm shutdown" this sends a message to the DomU to execute the program "/sbin/poweroff", if this command does not work then you will never shut down. Please try executing "/ sbin/poweroff" manually on the DomU and see if that works. For example, if I try on one of our NFSROOT images with "init=/bin/sh" the following happens:
9:/# /sbin/poweroff
Broadcast message from root (console) (Wed Dec 31 19:02:07 1969):
The system is going down for system halt NOW!
shutdown: timeout opening/writing control channel /dev/initctl
init: timeout opening/writing control channel /dev/initctl
9:/#
and the DomU does not shut down because there is no "real" init process to create the /dev/intctl pipe, this is why I cannot "xm shutdown" this domain. If I boot the same thing but this time I do not define "init" but add " S " to the kernel parameters, init runs (but places be in single user mode) and now /sbin/poweroff runs if I run it manually or if I run it from XM.

Third, I have _never_ had a problem with "xm destroy" and it works instantly for me and I _hate_ saying "for me".
What do you mean "but using it a second time"?
The system freezing usually indicates that a DomU has panic()ed, this is currently an ourstanding bug in XenPPC but is usually only seen on UP versions. It would be news to me to see this on an SMP system.


thank you
http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ppc-devel

-JX


*Doron Shiloach/Watson/IBM*

12/07/06 11:55 AM

        
To
        Jimi Xenidis/Watson/[EMAIL PROTECTED]
cc
Dilma M Da silva/Watson/[EMAIL PROTECTED], David M Daly/Watson/[EMAIL PROTECTED], Maged Michael/Watson/[EMAIL PROTECTED]
Subject
        shutdown/destroy domU problem



        




Hi Jimi,

I'm having problems with the shutdown/destroy domU functionality with the latest version of Xen that David released. Here are the versions for Xen (top) and Linux (bottom) that we are using.

cso85:~/xen-maria-12-4/xen-ppc # hg tip
changeset: 13183:0e85b389980a
tag: tip
user: Jimi Xenidis <[EMAIL PROTECTED]>
date: Fri Dec 01 19:11:02 2006 -0500
summary: [XEN][POWERPC] should comment the Power Managment workaround in the code as well

so85:~/xen-maria-12-4/linux/linux-xen-ppc # hg tip
changeset: 33309:f0981398b745
tag: tip
user: [EMAIL PROTECTED]
date: Mon Nov 27 13:10:34 2006 -0500
summary: Applied LTT patch

In short, the shutdown feature does not work properly; after issuing xm shutdown domUid, the xm list still shows the domU present. The xm destroy causes the domain to go away, but using it a second time causes the machine to freeze. Do you have time to follow this thread? Are there other people I should talk to about this? Thanks for your help,

Doron Shiloach
Tieline: 862-3110
Phone: (914) 945-3110

--------------------------------------------------------------------- ---

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



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


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

Reply via email to