From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M2Uo5-00004u-54 for qemu-devel@nongnu.org; Fri, 08 May 2009 14:28:25 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M2Uo0-0008W6-L6 for qemu-devel@nongnu.org; Fri, 08 May 2009 14:28:24 -0400 Received: from [199.232.76.173] (port=34854 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M2Uo0-0008W3-E4 for qemu-devel@nongnu.org; Fri, 08 May 2009 14:28:20 -0400 Received: from e39.co.us.ibm.com ([32.97.110.160]:50701) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1M2Uo0-0003fn-16 for qemu-devel@nongnu.org; Fri, 08 May 2009 14:28:20 -0400 Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by e39.co.us.ibm.com (8.13.1/8.13.1) with ESMTP id n48IOgEu027355 for ; Fri, 8 May 2009 12:24:42 -0600 Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v9.2) with ESMTP id n48IQxUj166254 for ; Fri, 8 May 2009 12:26:59 -0600 Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id n48IQx1n007382 for ; Fri, 8 May 2009 12:26:59 -0600 Date: Fri, 8 May 2009 13:26:58 -0500 From: Ryan Harper Subject: Re: [Qemu-devel] Re: [PATCH] Add monitor command for system_reboot Message-ID: <20090508182658.GH3233@us.ibm.com> References: <1241801561-11441-1-git-send-email-ryanh@us.ibm.com> <4A046503.8050209@us.ibm.com> <20090508171305.GC3233@us.ibm.com> <4A046E09.6080101@us.ibm.com> <20090508174533.GF3233@us.ibm.com> <4A04768E.5020705@codemonkey.ws> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4A04768E.5020705@codemonkey.ws> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Anthony Liguori , Ryan Harper , "qemu-devel@nongnu.org" * Anthony Liguori [2009-05-08 13:15]: > Ryan Harper wrote: > >well, I think this is where we're missing each other. I figured if the > >users requested a reboot, that we also trigger the powerdown, and that's > >what I'm doing. If in the monitor you issue system_reboot, I'm > >triggering a powerdown automatically. Are you saying you want the users > >to do, system_reset, and then system_powerdown in their own? > > No, I'm saying that if a user does a system_reboot, and that fails for > one reason or another (like the user hits Cancel in the GUI that pops > up), the flag is still present. > > If the user later does a proper shutdown of his system (in the guest > itself), instead of shutting down, it'll reboot. > > Try this: > > 1) do system_reboot in the monitor > 2) In the guest, when you get the Gnome GUI, hit cancel > 3) Go to the Gnome menu to do a normal system shutdown. > > It'll end up doing a reboot. Hrm, yeah -- I'll have to see what path a guest shutdown travels and if it's the same as what would happen with a system_powerdown via the monitor we can clear the reboot flag. -- Ryan Harper Software Engineer; Linux Technology Center IBM Corp., Austin, Tx ryanh@us.ibm.com