From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 0/2] Introduce panic hypercall Date: Mon, 20 Jun 2011 18:31:23 +0300 Message-ID: <4DFF67CB.3060807@redhat.com> References: <1308577094-17551-1-git-send-email-gollub@b1-systems.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org To: Daniel Gollub Return-path: Received: from mx1.redhat.com ([209.132.183.28]:53486 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751787Ab1FTPb2 (ORCPT ); Mon, 20 Jun 2011 11:31:28 -0400 In-Reply-To: <1308577094-17551-1-git-send-email-gollub@b1-systems.de> Sender: kvm-owner@vger.kernel.org List-ID: On 06/20/2011 04:38 PM, Daniel Gollub wrote: > Introduce panic hypercall to enable the crashing guest to notify the > host. This enables the host to run some actions as soon a guest > crashed (kernel panic). > > This patch series introduces the panic hypercall at the host end. > As well as the hypercall for KVM paravirtuliazed Linux guests, by > registering the hypercall to the panic_notifier_list. > > The basic idea is to create KVM crashdump automatically as soon the > guest paniced and power-cycle the VM (e.g. libvirt). This would be more easily done via a "panic device" (I/O port or memory-mapped address) that the guest hits. It would be intercepted by qemu without any new code in kvm.\ However, I'm not sure I see the gain. Most enterprisey guests already contain in-guest crash dumpers which provide more information than a qemu memory dump could, since they know exact load addresses etc. and are integrated with crash analysis tools. What do you have in mind? -- error compiling committee.c: too many arguments to function