From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([208.118.235.92]:39102)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <vrozenfe@redhat.com>) id 1S8Isj-0005bS-3R
	for qemu-devel@nongnu.org; Thu, 15 Mar 2012 18:10:50 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <vrozenfe@redhat.com>) id 1S8Ish-00055r-2H
	for qemu-devel@nongnu.org; Thu, 15 Mar 2012 18:10:48 -0400
Received: from mx1.redhat.com ([209.132.183.28]:55290)
	by eggs.gnu.org with esmtp (Exim 4.71)
	(envelope-from <vrozenfe@redhat.com>) id 1S8Isg-00055g-PS
	for qemu-devel@nongnu.org; Thu, 15 Mar 2012 18:10:46 -0400
From: Vadim Rozenfeld <vrozenfe@redhat.com>
Date: Fri, 16 Mar 2012 00:10:38 +0200
References: <20120315191439.GM2894@illuin> <4F625E68.9040001@redhat.com>
In-Reply-To: <4F625E68.9040001@redhat.com>
MIME-Version: 1.0
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Message-Id: <201203160010.39999.vrozenfe@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, Michael Roth <mdroth@linux.vnet.ibm.com>, qemu-devel@nongnu.org

On Thursday, March 15, 2012 11:26:00 PM 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".
> 
It is not a loader problem. You even don't need to turn halbreakpoint option 
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