From: Michael Roth <mdroth@linux.vnet.ibm.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: aliguori@us.ibm.com, vrozenfe@redhat.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] BSOD when using Hyper-V extensions with Win2k8R2 guests
Date: Thu, 15 Mar 2012 16:39:45 -0500 [thread overview]
Message-ID: <20120315213945.GN2894@illuin> (raw)
In-Reply-To: <4F625E68.9040001@redhat.com>
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
>
next prev parent reply other threads:[~2012-03-15 21:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 19:14 [Qemu-devel] BSOD when using Hyper-V extensions with Win2k8R2 guests Michael Roth
2012-03-15 19:54 ` Vadim Rozenfeld
2012-03-15 20:00 ` Anthony Liguori
2012-03-15 20:32 ` Vadim Rozenfeld
2012-03-15 21:26 ` Paolo Bonzini
2012-03-15 21:39 ` Michael Roth [this message]
2012-03-15 22:10 ` Vadim Rozenfeld
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120315213945.GN2894@illuin \
--to=mdroth@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=vrozenfe@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.