From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:46839)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1S8IBT-0004Xk-V7
	for qemu-devel@nongnu.org; Thu, 15 Mar 2012 17:26:09 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1S8IBS-0004sy-7M
	for qemu-devel@nongnu.org; Thu, 15 Mar 2012 17:26:07 -0400
Received: from mail-we0-f173.google.com ([74.125.82.173]:63095)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <paolo.bonzini@gmail.com>) id 1S8IBR-0004si-Od
	for qemu-devel@nongnu.org; Thu, 15 Mar 2012 17:26:06 -0400
Received: by werp12 with SMTP id p12so3811058wer.4
	for <qemu-devel@nongnu.org>; Thu, 15 Mar 2012 14:26:03 -0700 (PDT)
Sender: Paolo Bonzini <paolo.bonzini@gmail.com>
Message-ID: <4F625E68.9040001@redhat.com>
Date: Thu, 15 Mar 2012 22:26:00 +0100
From: Paolo Bonzini <pbonzini@redhat.com>
MIME-Version: 1.0
References: <20120315191439.GM2894@illuin>
In-Reply-To: <20120315191439.GM2894@illuin>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Subject: Re: [Qemu-devel] BSOD when using Hyper-V extensions with Win2k8R2
	guests
List-Id: <qemu-devel.nongnu.org>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.nongnu.org/archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Michael Roth <mdroth@linux.vnet.ibm.com>
Cc: aliguori@us.ibm.com, vrozenfe@redhat.com, qemu-devel@nongnu.org

Il 15/03/2012 20:14, Michael Roth ha scritto:
> 
> Unfortunately the BSOD is too early to get a kernel dump, but here are
> the error params in case that's useful:
> 
> 0xFC0000096, 0xF800027F6200, 0x0, 0x0
> 
> Let me know if you need any other details.

You can use the Windows Boot Debugger.  (Disclaimer: I only used it
once).  Enable it with "bcdedit /bootdebug {current} ON".

To use it, you need two Windows VMs (the one that fails and one with
WinDbg installed).  It is the same as doing normal kernel debugging
except that the debuggee will hang waiting for a connection even before
showing the boot loader prompt.  You need to connect the serial consoles
of the VMs; I usually use socat like

socat "PIPE:$tty1,unlink-close=0,noctty=1" \
      "PIPE:$tty2,unlink-close=0,noctty=1

with the tty names taken from libvirt's XML.  It probably works with
Unix sockets too but I never tried.

>>From WinDbg you should be able to get a backtrace.  If you never used
WinDbg, remember to set it up for downloading symbols:
http://support.microsoft.com/kb/311503

HTH,

Paolo