From mboxrd@z Thu Jan 1 00:00:00 1970 From: Wen Congyang Subject: Re: [PATCH 0/2 v3] kvm: notify host when guest panicked Date: Tue, 13 Mar 2012 14:44:41 +0800 Message-ID: <4F5EECD9.8050508@cn.fujitsu.com> References: <4F58664D.1070800@cn.fujitsu.com> <4F58943E.1050402@redhat.com> <4F595B31.9090301@cn.fujitsu.com> <4F5DBC26.7060204@cn.fujitsu.com> <4F5DD0FD.9070904@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" , "Daniel P. Berrange" , KAMEZAWA Hiroyuki , Jan Kiszka , Gleb Natapov To: Avi Kivity Return-path: In-Reply-To: <4F5DD0FD.9070904@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org At 03/12/2012 06:33 PM, Avi Kivity Wrote: > On 03/12/2012 11:04 AM, Wen Congyang wrote: >> Do you have any other comments about this patch? >> > > Not really, but I'm not 100% convinced the patch is worthwhile. It's > likely to only be used by Linux, which has kexec facilities, and you can > put talk to management via virtio-serial and describe the crash in more > details than a simple hypercall. Hmm, can we use virtio-serial to talk with not-linux OS? I guess the answer is no. If so, virtio-serial is also used by linux. Another problem is: virtio-serial is available on many deployed versions but the guest must have virtio-serial device. So we cannot know the guest is panicked if it does not have virtio-serial device while the hypercall does not depend on any device. Thanks Wen Congyang