[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xen-users
Subject:    Re: [Xen-users] Removing old glpv windows drivers to install new -> inaccessible boot device
From:       Paul Durrant <Paul.Durrant () citrix ! com>
Date:       2015-10-30 9:51:30
Message-ID: 9AAE0902D5BC7E449B7C8E4E778ABCD02F63DAD8 () AMSPEX01CL01 ! citrite ! net
[Download RAW message or body]

> -----Original Message-----
> From: dunlapg@gmail.com [mailto:dunlapg@gmail.com] On Behalf Of
> George Dunlap
> Sent: 29 October 2015 09:39
> To: Éliás Tamás
> Cc: Matthias; xen-users@lists.xen.org; Paul Durrant
> Subject: Re: [Xen-users] Removing old glpv windows drivers to install new ->
> inaccessible boot device
> 
> On Wed, Oct 28, 2015 at 8:50 AM, Éliás Tamás <et@etit.hu> wrote:
> > Hi. Yes, I confirm, that booting into safe mode is possible. I turned on
> > testsigning with bcdedit, and tried installing the drivers again.
> > 
> > The isntall went fine, I could reboot. Unfortunately since then (it is
> > more then 8 hours now) I'm facing the attached screen. The animation is
> > just rolling, rolling rolling and nothing happens. CPU ticks are used,
> > so I assume something is happening, but it seemes pretty much stuck.
> > 
> > Any ideas?
> 
> I *think* the XenServer PV drivers are using miniport; in which case
> this KB article might be of use:
> 
> https://support.microsoft.com/en-us/kb/2795397
> 
> Paul Durrant can correct me if I'm wrong about miniport (and may be
> able to point you to a more useful fix if so).
> 

Miniport is just a Windows driver programming paradigm and doesn't mean a lot without \
qualification. However, looking at the KB article it seems that the subject is our \
old friend that 0x7B BSOD. In Xen PV driver installations this usually occurs when \
there is an incomplete driver installation or removal such that the 'master' PV \
driver (the Xen Project drivers actually have two: XENBUS and XENFILT) has requested \
unplug of the emulated disks, but the PV disk driver (the Xen Project one is called \
XENVBD) is missing. This means Windows has no system disk and the BSOD is the result.

The usual way to recover from this is to boot into safe mode (most PV drivers, \
including the Xen Project ones, will be disabled in this mode) and clean up the \
registry to get things back into a consistent state. Unfortunately you really need to \
know your way around the drivers you're trying to remove to be able to do this but \
blowing way all the service keys (under HKLM/system/currentcontrolset/services) for \
drivers you no longer want will usually do the trick.

  Paul

> -George
_______________________________________________
Xen-users mailing list
Xen-users@lists.xen.org
http://lists.xen.org/xen-users


[prev in list] [next in list] [prev in thread] [next in thread]