From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:59490) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VC3dM-0001Ip-P9 for qemu-devel@nongnu.org; Wed, 21 Aug 2013 04:19:25 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VC3dE-0007E9-CR for qemu-devel@nongnu.org; Wed, 21 Aug 2013 04:19:16 -0400 Received: from mail-ee0-x229.google.com ([2a00:1450:4013:c00::229]:48724) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VC3dE-0007Dd-5G for qemu-devel@nongnu.org; Wed, 21 Aug 2013 04:19:08 -0400 Received: by mail-ee0-f41.google.com with SMTP id d17so65383eek.0 for ; Wed, 21 Aug 2013 01:19:07 -0700 (PDT) Sender: Paolo Bonzini Message-ID: <521477CF.4010703@redhat.com> Date: Wed, 21 Aug 2013 10:18:23 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <1376233843-19410-1-git-send-email-marcel.a@redhat.com> <520B2B8D.8070401@redhat.com> <1377072197.1888.35.camel@localhost.localdomain> In-Reply-To: <1377072197.1888.35.camel@localhost.localdomain> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH for-1.6 V2 0/2] pvpanic: Separate pvpanic from machine type List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Marcel Apfelbaum Cc: aliguori@us.ibm.com, gleb@redhat.com, mst@redhat.com, hutao@cn.fujitsu.com, qemu-devel@nongnu.org, Ronen Hod , kraxel@redhat.com, afaerber@suse.de, vrozenfe@redhat.com Il 21/08/2013 10:03, Marcel Apfelbaum ha scritto: > On Wed, 2013-08-14 at 10:02 +0300, Ronen Hod wrote: >> How about adding a flag that tells QEMU whether to pause or reboot the guest >> after the panic? >> We cannot assume that we always have a management layer that takes care >> of this. >> One example is Microsoft's WHQL that deliberately generates a BSOD, and then >> examines the dump files. > After this patch the pvpanic is not part of the global devices anymore so just > don't enable it if you want to reboot on BSOD. > In my opinion "reboot after panic" equals "run without pvpanic device" This is not entirely possible, since "reboot after panic" is a guest setting while "run without pvpanic device" is a host setting (that the guest administrator may not even have access to: Ronen's case is a good example of this, because the "administrator" there is the WHQL harness). However, I think this is a driver problem. The driver should just probe the "reboot after panic" setting and not issue the outb to the pvpanic port. Paolo