Xen users - Dec 2009 - Windows 2008 64 bits + gplpv driver = BSOD

Hello,

Each time I try to install GPLPV drivers on a Windows 2008 Server 64
bits, I''ve got a BSOD "0x0000007b".
I follow this :
http://wiki.xensource.com/xenwiki/XenWindowsGplPv/Installing


      bcdedit /enum /v         <-- note the guid string next to
"identifier" under "Windows Boot Loader"
      bcdedit /copy {string from above} /d "Microsoft Windows Server
2008 GPLPV"    <-- change description to whatever suits you and note
the new guid that gets printed as a result
      bcdedit /set {new guid from above} LOADOPTIONS "GPLPV"

And on the first reboot, I boot on the "normal" (not Windows 2008 with
option GPLPV).
And after few seconds (when it loads xenpci.sys), I''ve got the BSOD.

Here is :
/var/log/xen/qemu-dm-winpv.log

ACPI PCI hotplug: read addr=0x10e1, val=0x0.
track_dirty_vram(f0000000, 26) failed (-1, 22)
Unknown PV product 2 loaded in guest
PV driver build 1
region type 1 at [c100,c200).
region type 0 at [f3001000,f3001100).
squash iomem [f3001000, f3001100).
track_dirty_vram(f0000000, 26) failed (-1, 22)
[...] lot''s of time this line
[...]
reset requested in cpu_handle_ioreq.
Issued domain 56 reboot

My winpv.cfg (with all comments removed for better reading) :
import os, re

arch_libdir = ''lib''
arch = os.uname()[4]
if os.uname()[0] == ''Linux'' and
re.search(''64'', arch):
    arch_libdir = ''lib64''

kernel = "/usr/lib64/xen-3.4/boot/hvmloader"
builder=''hvm''
memory = 1024
name = "winpv"
boot = "c"
vif = [ ''type=ioemu, bridge=eth1'' ]
disk = [  ''phy:/dev/vg_xen/winbackup,ioemu:hda,w'',]

on_poweroff = ''preserve''
on_reboot   = ''preserve''
on_crash    = ''preserve''

device_model = ''/usr/lib64/xen/bin/qemu-dm''
sdl=0
opengl=1
vnc=1
vnclisten="0.0.0.0"
vncdisplay=1
vncpasswd=''foobar''
stdvga=0
serial=''pty''
localtime=1
usbdevice=''tablet''
keymap=''fr''

Drivers tested :
gplpv_Vista2008x64_0.10.0.134.msi
gplpv_Vista2008x64_0.10.0.138.msi
gplpv_Vista2008x64_0.10.0.142.msi

Same results !

Regards,

Olivier.

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Mon, Dec 14, 2009 at 4:59 PM, Olivier LAMBERT
<lambert.olivier@gmail.com> wrote:
> Hello,
>
> Each time I try to install GPLPV drivers on a Windows 2008 Server 64
> bits, I''ve got a BSOD "0x0000007b".
> I follow this :
> http://wiki.xensource.com/xenwiki/XenWindowsGplPv/Installing
That page seriously needs updating :P
>
>
>      bcdedit /enum /v         <-- note the guid string next to
> "identifier" under "Windows Boot Loader"
>      bcdedit /copy {string from above} /d "Microsoft Windows Server
> 2008 GPLPV"    <-- change description to whatever suits you and
note
> the new guid that gets printed as a result
>      bcdedit /set {new guid from above} LOADOPTIONS "GPLPV"
You don''t need it now. However I recommend that you add a NOGPLPV
entry instead so you can disable GPLPV driver when needed.
>
> And on the first reboot, I boot on the "normal" (not Windows 2008
with
> option GPLPV).
> And after few seconds (when it loads xenpci.sys), I''ve got the
BSOD.
See this thread first
http://lists.xensource.com/archives/html/xen-users/2009-11/msg00412.html

In your case, you could probably enter safe mode, uninstall GPLPV, and
retry installation using the above method.

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> 
> >
> >
> >      bcdedit /enum /v         <-- note the guid string next to
> > "identifier" under "Windows Boot Loader"
> >      bcdedit /copy {string from above} /d "Microsoft Windows
Server
> > 2008 GPLPV"    <-- change description to whatever suits you
and note
> > the new guid that gets printed as a result
> >      bcdedit /set {new guid from above} LOADOPTIONS "GPLPV"
> 
> You don''t need it now. However I recommend that you add a NOGPLPV
> entry instead so you can disable GPLPV driver when needed.
Safe mode does the same thing, but see below.
> 
> >
> > And on the first reboot, I boot on the "normal" (not Windows
2008 with
> > option GPLPV).
> > And after few seconds (when it loads xenpci.sys), I''ve got
the BSOD.
> 
> See this thread first
> http://lists.xensource.com/archives/html/xen-users/2009-11/msg00412.html
> 
> In your case, you could probably enter safe mode, uninstall GPLPV, and
> retry installation using the above method.
> 
Unfortunately, that might not work. Windows will refuse to load xenpci.sys if
testsigning isn''t right, and because it integrates itself into the ata
driver stack as an ''upper filter'', when it fails windows might
fail the whole stack, even in safe mode. I haven''t experimented with
driver load options that might still let the ata drivers work even if one of
their filters is not loading...

James


_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Mon, Dec 14, 2009 at 6:43 PM, James Harper
<james.harper@bendigoit.com.au> wrote:
>> In your case, you could probably enter safe mode, uninstall GPLPV, and
>> retry installation using the above method.
>>
>
> Unfortunately, that might not work. Windows will refuse to load xenpci.sys
if testsigning isn''t right, and because it integrates itself into the
ata driver stack as an ''upper filter'', when it fails windows
might fail the whole stack, even in safe mode.
That''s new. At least for me :D
So how can we recover from an incorrectly-installed GPLPV installation then?

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Using LVM snapshots ;)
That''s how I''m avoiding reinstall.

On Mon, Dec 14, 2009 at 1:38 PM, Fajar A. Nugraha <fajar@fajar.net>
wrote:
> On Mon, Dec 14, 2009 at 6:43 PM, James Harper
> <james.harper@bendigoit.com.au> wrote:
>>> In your case, you could probably enter safe mode, uninstall GPLPV,
and
>>> retry installation using the above method.
>>>
>>
>> Unfortunately, that might not work. Windows will refuse to load
xenpci.sys if testsigning isn''t right, and because it integrates itself
into the ata driver stack as an ''upper filter'', when it fails
windows might fail the whole stack, even in safe mode.
>
> That''s new. At least for me :D
> So how can we recover from an incorrectly-installed GPLPV installation
then?
>
> --
> Fajar
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Ok, so after disabling signature and reboot BEFORE installing GPLPV
drivers, it works.
But I''ve got a big perf. issue :
Before GPLPV, test with Crystal Disk Mark 2.2 :
Read 512K : 295 MB/s Write : 9.3 MB/s

After GPLPV :
Read 512K : 8.3 MB/s Write : 7.7 MB/s

Wow. It''s really slower !

Furthermore, without or with GPLPV driver, when I reboot my guest, it
freezes on a black screen with blinking cursor, just after the
"Shutdown computer" message.
xm list show a "s" state, and xend log says :

Domain has shutdown: name=winpv id=61 reason=reboot.
[2009-12-14 16:22:24 20062] INFO (XendDomainInfo:2091) Preserving dead
domain winpv (61).

So it''s dead, but why ?

Thanks for the help :)

Regards,


Olivier

On Mon, Dec 14, 2009 at 1:43 PM, Olivier LAMBERT
<lambert.olivier@gmail.com> wrote:
> Using LVM snapshots ;)
> That''s how I''m avoiding reinstall.
>
> On Mon, Dec 14, 2009 at 1:38 PM, Fajar A. Nugraha <fajar@fajar.net>
wrote:
>> On Mon, Dec 14, 2009 at 6:43 PM, James Harper
>> <james.harper@bendigoit.com.au> wrote:
>>>> In your case, you could probably enter safe mode, uninstall
GPLPV, and
>>>> retry installation using the above method.
>>>>
>>>
>>> Unfortunately, that might not work. Windows will refuse to load
xenpci.sys if testsigning isn''t right, and because it integrates itself
into the ata driver stack as an ''upper filter'', when it fails
windows might fail the whole stack, even in safe mode.
>>
>> That''s new. At least for me :D
>> So how can we recover from an incorrectly-installed GPLPV installation
then?
>>
>> --
>> Fajar
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
>>
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> 
> On Mon, Dec 14, 2009 at 6:43 PM, James Harper
> <james.harper@bendigoit.com.au> wrote:
> >> In your case, you could probably enter safe mode, uninstall GPLPV,
and
> >> retry installation using the above method.
> >>
> >
> > Unfortunately, that might not work. Windows will refuse to load
xenpci.sys
> if testsigning isn''t right, and because it integrates itself into
the
ata
> driver stack as an ''upper filter'', when it fails windows
might fail
the whole
> stack, even in safe mode.
> 
> That''s new. At least for me :D
> So how can we recover from an incorrectly-installed GPLPV installation
then?
> 
Have good backups :)

Boot from the Install CD, go into recovery mode, and fix the registry.
Remove any value where XenPCI is in UpperFilters. Remove all xen*.sys
from windows\system32\drivers too.

James

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

On Tue, Dec 15, 2009 at 5:18 AM, James Harper
<james.harper@bendigoit.com.au> wrote:
>> > Unfortunately, that might not work. Windows will refuse to load
> xenpci.sys
>> if testsigning isn''t right, and because it integrates itself
into the
> ata
>> driver stack as an ''upper filter'', when it fails
windows might fail
> the whole
>> stack, even in safe mode.
> Boot from the Install CD, go into recovery mode, and fix the registry.
> Remove any value where XenPCI is in UpperFilters. Remove all xen*.sys
> from windows\system32\drivers too.
That''s ... a pain :P

You did say the main problem is testsigining, right? So is it safe to
assume that if we can get windows to disable driver signing
enforcement by first pressing F8 (or tab key, on 2008r2) then the
NOGPLV switch will work as expected?

-- 
Fajar

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

> 
> On Tue, Dec 15, 2009 at 5:18 AM, James Harper
> <james.harper@bendigoit.com.au> wrote:
> >> > Unfortunately, that might not work. Windows will refuse to
load
> > xenpci.sys
> >> if testsigning isn''t right, and because it integrates
itself into
the
> > ata
> >> driver stack as an ''upper filter'', when it fails
windows might fail
> > the whole
> >> stack, even in safe mode.
> 
> > Boot from the Install CD, go into recovery mode, and fix the
registry.
> > Remove any value where XenPCI is in UpperFilters. Remove all
xen*.sys
> > from windows\system32\drivers too.
> 
> That''s ... a pain :P
> 
> You did say the main problem is testsigining, right? So is it safe to
> assume that if we can get windows to disable driver signing
> enforcement by first pressing F8 (or tab key, on 2008r2) then the
> NOGPLV switch will work as expected?
> 
Hmmm... yes that might work.

James

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users