From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:51745) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S7NVM-0003qI-6A for qemu-devel@nongnu.org; Tue, 13 Mar 2012 04:55:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1S7NUx-00063Y-N5 for qemu-devel@nongnu.org; Tue, 13 Mar 2012 04:54:51 -0400 Received: from mx1.redhat.com ([209.132.183.28]:40583) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1S7NUx-00062u-F6 for qemu-devel@nongnu.org; Tue, 13 Mar 2012 04:54:27 -0400 Message-ID: <4F5F0B36.1020808@redhat.com> Date: Tue, 13 Mar 2012 10:54:14 +0200 From: Avi Kivity MIME-Version: 1.0 References: <4F58664D.1070800@cn.fujitsu.com> <4F58943E.1050402@redhat.com> <4F595B31.9090301@cn.fujitsu.com> <4F5DBC26.7060204@cn.fujitsu.com> <4F5DD0FD.9070904@redhat.com> <4F5EECD9.8050508@cn.fujitsu.com> In-Reply-To: <4F5EECD9.8050508@cn.fujitsu.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 0/2 v3] kvm: notify host when guest panicked List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Wen Congyang Cc: Gleb Natapov , kvm list , Jan Kiszka , qemu-devel , "linux-kernel@vger.kernel.org" , KAMEZAWA Hiroyuki On 03/13/2012 08:44 AM, Wen Congyang wrote: > 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. You can use virtio-serial with any guest that has a driver. There are drivers available for Windows. > 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. > The hypercall implementation must exist in the hypervisor. virtio-serial is used by the guest agent, so it's likely to be availalble in all cloud or data center deployments. -- error compiling committee.c: too many arguments to function