From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752381Ab2FMHyI (ORCPT ); Wed, 13 Jun 2012 03:54:08 -0400 Received: from mx1.redhat.com ([209.132.183.28]:57091 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751456Ab2FMHyF (ORCPT ); Wed, 13 Jun 2012 03:54:05 -0400 Message-ID: <4FD8470B.8010507@redhat.com> Date: Wed, 13 Jun 2012 09:53:47 +0200 From: Paolo Bonzini User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120605 Thunderbird/13.0 MIME-Version: 1.0 To: Wen Congyang CC: kvm list , qemu-devel , "linux-kernel@vger.kernel.org" , Avi Kivity , "Daniel P. Berrange" , KAMEZAWA Hiroyuki , Jan Kiszka , Gleb Natapov Subject: Re: [PATCH 3/3] deal with guest panicked event References: <4FB9E4CE.8060709@cn.fujitsu.com> <4FB9E5CB.2020208@cn.fujitsu.com> <4FD74447.2090906@redhat.com> <4FD83B20.9060203@cn.fujitsu.com> In-Reply-To: <4FD83B20.9060203@cn.fujitsu.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Il 13/06/2012 09:02, Wen Congyang ha scritto: >>> >> +Other possible actions are: >>> >> +@code{pause} (emit QEVENT_GUEST_PANICKED and pause VM), >>> >> +@code{quit} (emit QEVENT_GUEST_PANICKED and quit VM). >> > >> > Rather than just "quit", there should be choices for "shutdown", >> > "poweroff" and "reset" for consistency with -watchdog-action. > Hmm, quit means poweroff. I will add reset, but I think we donot > need shutdown, because we cannot shutdown the system when it is > panicked. Right. :) Can you also rename quit to poweroff? >> > Also, this option should also be accessible from "-machine", please. > I don't understand this. Do you mean we can also specify this action > in -machine option? Yes, like -machine panic_action=poweroff. Paolo From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH 3/3] deal with guest panicked event Date: Wed, 13 Jun 2012 09:53:47 +0200 Message-ID: <4FD8470B.8010507@redhat.com> References: <4FB9E4CE.8060709@cn.fujitsu.com> <4FB9E5CB.2020208@cn.fujitsu.com> <4FD74447.2090906@redhat.com> <4FD83B20.9060203@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" , Avi Kivity , KAMEZAWA Hiroyuki To: Wen Congyang Return-path: In-Reply-To: <4FD83B20.9060203@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 Il 13/06/2012 09:02, Wen Congyang ha scritto: >>> >> +Other possible actions are: >>> >> +@code{pause} (emit QEVENT_GUEST_PANICKED and pause VM), >>> >> +@code{quit} (emit QEVENT_GUEST_PANICKED and quit VM). >> > >> > Rather than just "quit", there should be choices for "shutdown", >> > "poweroff" and "reset" for consistency with -watchdog-action. > Hmm, quit means poweroff. I will add reset, but I think we donot > need shutdown, because we cannot shutdown the system when it is > panicked. Right. :) Can you also rename quit to poweroff? >> > Also, this option should also be accessible from "-machine", please. > I don't understand this. Do you mean we can also specify this action > in -machine option? Yes, like -machine panic_action=poweroff. Paolo From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:42588) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SeiP3-0001TS-Sr for qemu-devel@nongnu.org; Wed, 13 Jun 2012 03:54:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SeiOx-0004JL-QJ for qemu-devel@nongnu.org; Wed, 13 Jun 2012 03:54:09 -0400 Received: from mx1.redhat.com ([209.132.183.28]:38565) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SeiOx-0004JA-Hl for qemu-devel@nongnu.org; Wed, 13 Jun 2012 03:54:03 -0400 Message-ID: <4FD8470B.8010507@redhat.com> Date: Wed, 13 Jun 2012 09:53:47 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <4FB9E4CE.8060709@cn.fujitsu.com> <4FB9E5CB.2020208@cn.fujitsu.com> <4FD74447.2090906@redhat.com> <4FD83B20.9060203@cn.fujitsu.com> In-Reply-To: <4FD83B20.9060203@cn.fujitsu.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 3/3] deal with guest panicked event 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" , Avi Kivity , KAMEZAWA Hiroyuki Il 13/06/2012 09:02, Wen Congyang ha scritto: >>> >> +Other possible actions are: >>> >> +@code{pause} (emit QEVENT_GUEST_PANICKED and pause VM), >>> >> +@code{quit} (emit QEVENT_GUEST_PANICKED and quit VM). >> > >> > Rather than just "quit", there should be choices for "shutdown", >> > "poweroff" and "reset" for consistency with -watchdog-action. > Hmm, quit means poweroff. I will add reset, but I think we donot > need shutdown, because we cannot shutdown the system when it is > panicked. Right. :) Can you also rename quit to poweroff? >> > Also, this option should also be accessible from "-machine", please. > I don't understand this. Do you mean we can also specify this action > in -machine option? Yes, like -machine panic_action=poweroff. Paolo