From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MOXUf-0006mB-O2 for qemu-devel@nongnu.org; Wed, 08 Jul 2009 09:47:29 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MOXUb-0006fr-PN for qemu-devel@nongnu.org; Wed, 08 Jul 2009 09:47:29 -0400 Received: from [199.232.76.173] (port=42252 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MOXUb-0006fX-Gw for qemu-devel@nongnu.org; Wed, 08 Jul 2009 09:47:25 -0400 Received: from e33.co.us.ibm.com ([32.97.110.151]:38107) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MOXUb-0003qr-0s for qemu-devel@nongnu.org; Wed, 08 Jul 2009 09:47:25 -0400 Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [9.17.195.227]) by e33.co.us.ibm.com (8.13.1/8.13.1) with ESMTP id n68Dj91G011592 for ; Wed, 8 Jul 2009 07:45:09 -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 n68DlLNp256192 for ; Wed, 8 Jul 2009 07:47:21 -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 n68DlKlm005298 for ; Wed, 8 Jul 2009 07:47:21 -0600 Message-ID: <4A54A367.3010603@us.ibm.com> Date: Wed, 08 Jul 2009 08:47:19 -0500 From: Anthony Liguori MIME-Version: 1.0 Subject: Re: [Qemu-devel] [PATCH][RESEND] Add monitor command for system_reboot References: <20090707192631.GQ11590@us.ibm.com> <20090708075601.GJ28046@redhat.com> <4A549990.2060205@us.ibm.com> <20090708132623.GN26640@redhat.com> In-Reply-To: <20090708132623.GN26640@redhat.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: "Daniel P. Berrange" Cc: Ryan Harper , qemu-devel@nongnu.org, Gleb Natapov Daniel P. Berrange wrote: > > Only other option I think of is a pure paravirt shutdown/reboot > handler, ala Xen. That sucks in different ways though, namely > needing a driver in the guest, which is probably worse. > What do you think about Avi's suggestion of using -no-shutdown, doing a system_powerdown, waiting to receive a powerdown (you can poll 'info status' too to see when you entered into the paused state), and then doing a system_reset? I'd suggesting doing a timeout too while waiting to avoid waiting forever. > Daniel > -- Regards, Anthony Liguori