From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NrXpH-0000yf-M6 for qemu-devel@nongnu.org; Tue, 16 Mar 2010 10:32:55 -0400 Received: from [199.232.76.173] (port=46391 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NrXpH-0000yX-9q for qemu-devel@nongnu.org; Tue, 16 Mar 2010 10:32:55 -0400 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1NrXpG-0002R1-Lg for qemu-devel@nongnu.org; Tue, 16 Mar 2010 10:32:55 -0400 Received: from smtp2-g21.free.fr ([212.27.42.2]:37337) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NrXpF-0002Qo-UW for qemu-devel@nongnu.org; Tue, 16 Mar 2010 10:32:54 -0400 Received: from smtp2-g21.free.fr (localhost [127.0.0.1]) by smtp2-g21.free.fr (Postfix) with ESMTP id 6EA804B00E6 for ; Tue, 16 Mar 2010 15:32:48 +0100 (CET) Received: from laptop (vaf26-2-82-244-111-82.fbx.proxad.net [82.244.111.82]) by smtp2-g21.free.fr (Postfix) with ESMTP id 62AFA4B013D for ; Tue, 16 Mar 2010 15:32:46 +0100 (CET) In-Reply-To: <20100316105358.0831df27@redhat.com> Subject: Re: [Qemu-devel] wake-on-lan & IPMI implementation; real power-off and -no-shutdown From: "=?utf-8?q?Fran=C3=A7ois?= Revol" Date: Tue, 16 Mar 2010 15:26:14 +0100 CET Message-Id: <869578612-BeMail@laptop> Mime-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org > > > Also, it seems -no-shutdown doesn't actually "stop the emulation" > > > as > > > said in the manual, it actually keeps the vm running (and using > > > cpu), > > > despite the OS trying to shutdown via ACPI. At least I tested so > > > with > > > Haiku (and acpi=3Dtrue in kernel config), which properly exits QEMU > > > without -no-shutdown. > > > > Hmm, I think -no-shutdown should at least stop the CPUs executing. > > It is > > not really useful on its own though. The app managing QEMU would > > want to > > use the new JSON based monitor to listen for the SHUTDOWN event to > > be > > emitted, so it can detect the shutdown completing & then take > > action it > > wants either reset the guest, or kill QEMU, etc > > If I'm not missing something, -no-shutdown calls vm=5Fstop(), which > calls > pause=5Fall=5Fvcpus(). Oh indeed, "info status" shows the VM as "paused". I was misled because the GUI window was still open... Fran=C3=A7ois.