From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:40529) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z7L7s-0002l3-Ej for qemu-devel@nongnu.org; Tue, 23 Jun 2015 06:08:21 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Z7L7n-0004kS-9S for qemu-devel@nongnu.org; Tue, 23 Jun 2015 06:08:20 -0400 Received: from mx2.parallels.com ([199.115.105.18]:33863) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Z7L7n-0004kG-45 for qemu-devel@nongnu.org; Tue, 23 Jun 2015 06:08:15 -0400 Message-ID: <55893002.7020609@openvz.org> Date: Tue, 23 Jun 2015 13:08:02 +0300 From: "Denis V. Lunev" MIME-Version: 1.0 References: <1434989108-20924-1-git-send-email-den@openvz.org> <1434989108-20924-8-git-send-email-den@openvz.org> <55892B49.3040507@openvz.org> <55892C2D.1010407@redhat.com> In-Reply-To: <55892C2D.1010407@redhat.com> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH 07/11] kvm/x86: added hyper-v crash data and ctl msr's get/set'ers List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Andrey Smetanin , Gleb Natapov , qemu-devel@nongnu.org, kvm@vger.kernel.org, Peter Hornyack On 23/06/15 12:51, Paolo Bonzini wrote: > > On 23/06/2015 11:47, Denis V. Lunev wrote: >>> The current implementation is potentially more flexible but makes the >>> MSR handling a little more awkward since the host_initiated bool needs >>> to be passed around (patch 09). I guess either approach seems ok to >>> me. >>> >>> Also, if this patchset is used then it looks like >>> HV_X64_MSR_CRASH_CTL_CONTENTS can be removed. >> Paolo, >> >> do you have any opinion on this? I prefer >> configurable way but there is no problem >> to enable it by default dropping 'hv_panic' >> property. > I also prefer the configurable way. Would hv_panic prevent > reboot-on-BSOD from rebooting the VM? > > Paolo the behavior becomes controlled by libvirt, which has appropriate event configuration, specified here https://libvirt.org/formatdomain.html namely restart Thus it looks like without libvirt help the guest will stuck in RUN_STATE_GUEST_PANICKED state. Den