From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:48156) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QYgso-0005iq-1w for qemu-devel@nongnu.org; Mon, 20 Jun 2011 11:59:28 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QYgsm-0003No-7U for qemu-devel@nongnu.org; Mon, 20 Jun 2011 11:59:25 -0400 Received: from goliath.siemens.de ([192.35.17.28]:27117) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QYgsl-0003NW-M6 for qemu-devel@nongnu.org; Mon, 20 Jun 2011 11:59:24 -0400 Message-ID: <4DFF6E57.7040109@siemens.com> Date: Mon, 20 Jun 2011 17:59:19 +0200 From: Jan Kiszka MIME-Version: 1.0 References: <1308577094-17551-1-git-send-email-gollub@b1-systems.de> <4DFF67CB.3060807@redhat.com> <20110620153825.GH13042@redhat.com> <4DFF6B20.7090107@redhat.com> In-Reply-To: <4DFF6B20.7090107@redhat.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 0/2] Introduce panic hypercall List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Daniel Gollub , qemu-devel , kvm@vger.kernel.org On 2011-06-20 17:45, Avi Kivity wrote: >> This series does need to introduce a QMP event notification upon >> crash, so that the crash notification can be propagated to mgmt >> layers above QEMU. > > Yes. I think the best way to deal with that is to stop the VM on guest panic. There is already WIP to signal stop reasons via QMP. Maybe we need to differentiate between hypervisor and guest triggered panics (VMSTOP_GUEST_PANIC?), but the rest should come for free. Jan -- Siemens AG, Corporate Technology, CT T DE IT 1 Corporate Competence Center Embedded Linux