From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1M2Uas-0005Cx-BI
	for qemu-devel@nongnu.org; Fri, 08 May 2009 14:14:46 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1M2Uan-0005C1-Fp
	for qemu-devel@nongnu.org; Fri, 08 May 2009 14:14:45 -0400
Received: from [199.232.76.173] (port=33393 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1M2Uan-0005Bx-9T
	for qemu-devel@nongnu.org; Fri, 08 May 2009 14:14:41 -0400
Received: from mail-gx0-f176.google.com ([209.85.217.176]:60310)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <anthony@codemonkey.ws>) id 1M2Uan-0002Ch-0V
	for qemu-devel@nongnu.org; Fri, 08 May 2009 14:14:41 -0400
Received: by gxk24 with SMTP id 24so3909601gxk.10
	for <qemu-devel@nongnu.org>; Fri, 08 May 2009 11:14:40 -0700 (PDT)
Message-ID: <4A04768E.5020705@codemonkey.ws>
Date: Fri, 08 May 2009 13:14:38 -0500
From: Anthony Liguori <anthony@codemonkey.ws>
MIME-Version: 1.0
Subject: Re: [Qemu-devel] Re: [PATCH] Add monitor command for system_reboot
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>
In-Reply-To: <20090508174533.GF3233@us.ibm.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Ryan Harper <ryanh@us.ibm.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>

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.

Regards,

Anthony Liguori