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: Wed, 21 Mar 2012 19:34:01 +0200 Message-ID: <4F6A1109.8060209@redhat.com> References: <4F58664D.1070800@cn.fujitsu.com> <4F66E14F.3040809@cn.fujitsu.com> <4F6854F4.3060703@cn.fujitsu.com> <20120320154517.GG27928@redhat.com> <4F692723.8050904@cn.fujitsu.com> <20120321091127.GO22368@redhat.com> <4F69FF48.3010200@acm.org> <4F6A00EC.3060706@redhat.com> <20120321170413.GD3101@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: minyard@acm.org, Corey Minyard , Gleb Natapov , Wen Congyang , kvm list , qemu-devel , "linux-kernel@vger.kernel.org" , KAMEZAWA Hiroyuki , Jan Kiszka To: "Daniel P. Berrange" Return-path: In-Reply-To: <20120321170413.GD3101@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 03/21/2012 07:04 PM, Daniel P. Berrange wrote: > > > > In fact the feature can be implemented 100% host side by searching for a > > panic string signature in the console logs. > > You can even go one better and search for the panic string in the > guest memory directly, which is what virt-dmesg does :-) > > http://people.redhat.com/~rjones/virt-dmesg/ > -ETOOHACKY Any guest change will break this, no? -- error compiling committee.c: too many arguments to function