From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 0/2 v3] kvm: notify host when guest panicked Date: Thu, 08 Mar 2012 13:13:02 +0200 Message-ID: <4F58943E.1050402@redhat.com> References: <4F58664D.1070800@cn.fujitsu.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Gleb Natapov , kvm list , Jan Kiszka , qemu-devel , "linux-kernel@vger.kernel.org" , KAMEZAWA Hiroyuki To: Wen Congyang Return-path: In-Reply-To: <4F58664D.1070800@cn.fujitsu.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org List-Id: kvm.vger.kernel.org On 03/08/2012 09:57 AM, Wen Congyang wrote: > We can know the guest is paniced when the guest runs on xen. > But we do not have such feature on kvm. > > Another purpose of this feature is: management app(for example: > libvirt) can do auto dump when the guest is crashed. If management > app does not do auto dump, the guest's user can do dump by hand if > he sees the guest is paniced. > > I touch the hypervisor instead of using virtio-serial, because > 1. it is simple > 2. the virtio-serial is an optional device, and the guest may > not have such device. > > Changes from v2 to v3: > 1. correct spelling > > Changes from v1 to v2: > 1. split up host and guest-side changes > 2. introduce new request flag to avoid changing return values. I see no Documentation/ changes. -- error compiling committee.c: too many arguments to function