From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33)
	id 1CYsXA-0000L0-0W
	for qemu-devel@nongnu.org; Mon, 29 Nov 2004 15:54:08 -0500
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33)
	id 1CYsX7-0000Kc-Dc
	for qemu-devel@nongnu.org; Mon, 29 Nov 2004 15:54:07 -0500
Received: from [199.232.76.173] (helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.33) id 1CYsX7-0000KS-9n
	for qemu-devel@nongnu.org; Mon, 29 Nov 2004 15:54:05 -0500
Received: from [131.111.8.134] (helo=ppsw-4.csi.cam.ac.uk)
	by monty-python.gnu.org with esmtp (Exim 4.34) id 1CYsNL-0000kY-PM
	for qemu-devel@nongnu.org; Mon, 29 Nov 2004 15:43:59 -0500
Received: from rn214.trin.cam.ac.uk ([131.111.193.203]:33193)
	by ppsw-4.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.134]:25)
	with esmtp id 1CYsNJ-0000pD-DA (Exim 4.44) for qemu-devel@nongnu.org
	(return-path <rn214@hermes.cam.ac.uk>); Mon, 29 Nov 2004 20:43:57 +0000
Message-ID: <41AB8A0C.4050509@hermes.cam.ac.uk>
Date: Mon, 29 Nov 2004 20:43:56 +0000
From: Richard Neill <rn214@hermes.cam.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Qemu-devel] Suggestion - trap window-close of VM
Reply-To: qemu-devel@nongnu.org
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 <qemu-devel@nongnu.org>

Dear All,

A thought that occurred to me. If one is running a virtual machine (eg 
copy of WinXP), then simply closing the qemu window is a really bad 
idea, since it will effectively crash the guest.

BUT, given that the user expects to be running an *application* rather 
than an operating system, the natural thing to do is to close the qemu 
window, rather than remembering to first do a full shutdown of the 
guest. This is a very easy mistake to make.

I'd suggest that:

if ((qemu's window is closed from the GUI) and (the guest has not shut 
down)); then
	qemu should pop up a warning dialog:
		"Are you sure you want to quit - you should really shut
	down the guest first, or you may suffer dataloss [yes] [no]"
fi


Is it possible to know whether the guest has finished shutting down from 
the CPU state?


Regards

Richard