From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH] kvm: notify host when guest paniced Date: Wed, 29 Feb 2012 12:00:41 +0200 Message-ID: <4F4DF749.7060507@redhat.com> References: <4F4AF1FB.6000903@cn.fujitsu.com> <4F4CB926.6050600@redhat.com> <4F4D7F5E.5040202@cn.fujitsu.com> <4F4DF4C6.90609@redhat.com> <20120229095557.GE24600@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: kvm list , qemu-devel , linux-kernel@vger.kernel.org, KAMEZAWA Hiroyuki To: Gleb Natapov Return-path: In-Reply-To: <20120229095557.GE24600@redhat.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 02/29/2012 11:55 AM, Gleb Natapov wrote: > > > > > > > How about using a virtio-serial channel for this? You can transfer any > > amount of information (including the dump itself). > > > Isn't it unreliable after the guest panicked? So is calling hypercalls, or dumping, or writing to the screen. Of course calling a hypercall is simpler and so is more reliable. > Having special kdump > kernel that transfers dump to a host via virtio-serial channel though > sounds interesting. May be that's what you mean. Yes. The "panic, starting dump" signal should be initiated by the panicking kernel though, in case the dump fails. -- error compiling committee.c: too many arguments to function