From: Erik Damrose <damrose@univention.de>
To: James Harper <james@ejbdigital.com.au>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Cc: Steven Haigh <netwiz@crc.id.au>
Subject: Re: Xen4.4 / Win7 (32 bit) / gplpv blue screens in xenvbd.sys
Date: Tue, 16 Sep 2014 10:11:16 +0200 [thread overview]
Message-ID: <5417F0A4.4010303@univention.de> (raw)
In-Reply-To: <1ee9f4db8e7c4c16877d92523012df5a@SIXPR04MB304.apcprd04.prod.outlook.com>
On 15.09.2014 23:18, James Harper wrote:
>>
>> Hi guys,
>>
>> I've clean installed Win7 32 bit under Xen 4.4 - then tried to
>> install the gplpv drivers from:
>> http://www.ejbdigital.com.au/1-0-1100/
>>
>> Every boot from then on results in a blue screen in xenvbd.sys.
>>
>> Has anyone come across this? more importantly, solved the issue?
>>
>
> Someone else reported this but I never got an answer to some
> questions I asked.
>
> I don't have x86 media on hand, but it's probably a regression on
> the 32 bit side of things - can you test with x64 to confirm that
> it's only 32 bit that's broken and not something else?
Hi,
i can confirm that the bluescreens only happen on 32bit systems. I
have tested driver versions .1089 .1092 and .1100 on 32bit and 64bit.
Is there additional information that might help you?
Thanks for looking into this
Erik
>
> Thanks
>
> James
next prev parent reply other threads:[~2014-09-16 8:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-15 11:40 Xen4.4 / Win7 (32 bit) / gplpv blue screens in xenvbd.sys Steven Haigh
2014-09-15 21:18 ` James Harper
2014-09-16 4:00 ` Steven Haigh
2014-09-16 7:24 ` Pasi Kärkkäinen
2014-09-19 10:11 ` James Harper
2014-09-16 8:11 ` Erik Damrose [this message]
2014-09-16 12:35 ` Steven Haigh
2014-09-25 12:41 ` James Harper
2014-09-25 16:16 ` Steven Haigh
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=5417F0A4.4010303@univention.de \
--to=damrose@univention.de \
--cc=james@ejbdigital.com.au \
--cc=netwiz@crc.id.au \
--cc=xen-devel@lists.xen.org \
/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.