From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1NrDHG-0005cD-0a
	for qemu-devel@nongnu.org; Mon, 15 Mar 2010 12:36:26 -0400
Received: from [199.232.76.173] (port=52276 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1NrDHE-0005aG-3R
	for qemu-devel@nongnu.org; Mon, 15 Mar 2010 12:36:24 -0400
Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim
	4.60) (envelope-from <revol@free.fr>) id 1NrDHD-0003C2-B2
	for qemu-devel@nongnu.org; Mon, 15 Mar 2010 12:36:23 -0400
Received: from smtp2-g21.free.fr ([212.27.42.2]:52946)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <revol@free.fr>) id 1NrDHC-0003Ba-Kt
	for qemu-devel@nongnu.org; Mon, 15 Mar 2010 12:36:23 -0400
Received: from smtp2-g21.free.fr (localhost [127.0.0.1])
	by smtp2-g21.free.fr (Postfix) with ESMTP id ABB564B01BE
	for <qemu-devel@nongnu.org>; Mon, 15 Mar 2010 17:36:18 +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 B20C94B0261
	for <qemu-devel@nongnu.org>; Mon, 15 Mar 2010 17:36:15 +0100 (CET)
In-Reply-To: <4B9E6059.3040400@codemonkey.ws>
Subject: Re: [Qemu-devel] wake-on-lan & IPMI implementation; real power-off
	and -no-shutdown
From: "=?utf-8?q?Fran=C3=A7ois?= Revol" <revol@free.fr>
Date: Mon, 15 Mar 2010 17:36:29 +0100 CET
Message-Id: <8080978835-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: <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: 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
> >    
> 
> The semantics of -no-shutdown are awful.
> 
> I'd personally prefer to see the option deprecated and a new set of 
> options introduced with clearer semantics.
> 
> Currently, -no-shutdown does too many things.  It affects reboot 
> behaviour, shutdown behaviour, the behavior of the SDL close button.  
> Each of these things should be individual tunables.

Indeed, it both means "do not allow user to close the vm" and "do not 
allow the guest to stop (or reboot =3F)" it seems...

Fran=C3=A7ois.