From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:39493)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <flukshun@gmail.com>) id 1S8IOq-0002iJ-Qh
	for qemu-devel@nongnu.org; Thu, 15 Mar 2012 17:39:58 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <flukshun@gmail.com>) id 1S8IOo-0007PR-GK
	for qemu-devel@nongnu.org; Thu, 15 Mar 2012 17:39:56 -0400
Received: from mail-pz0-f45.google.com ([209.85.210.45]:55548)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <flukshun@gmail.com>) id 1S8IOo-0007P7-7L
	for qemu-devel@nongnu.org; Thu, 15 Mar 2012 17:39:54 -0400
Received: by dadp14 with SMTP id p14so5026563dad.4
	for <qemu-devel@nongnu.org>; Thu, 15 Mar 2012 14:39:51 -0700 (PDT)
Sender: fluxion <flukshun@gmail.com>
Date: Thu, 15 Mar 2012 16:39:45 -0500
From: Michael Roth <mdroth@linux.vnet.ibm.com>
Message-ID: <20120315213945.GN2894@illuin>
References: <20120315191439.GM2894@illuin>
 <4F625E68.9040001@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4F625E68.9040001@redhat.com>
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: Paolo Bonzini <pbonzini@redhat.com>
Cc: aliguori@us.ibm.com, vrozenfe@redhat.com, qemu-devel@nongnu.org

On Thu, Mar 15, 2012 at 10:26:00PM +0100, Paolo Bonzini wrote:
> 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.

Nice. I knew it was possible but never tried setting it up before. Really
useful to know, thanks!

> 
> 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
>