Can you try the same thing with the 0.10.0.98 drivers? Chked version. I
have the symbols for those
> -----Original Message-----
> From: Nick Couchman [mailto:Nick.Couchman@xxxxxxxxx]
> Sent: Monday, 7 September 2009 08:59
> To: James Harper; XEN Mailing List
> Subject: RE: [Xen-users] GPLPV: Windows Server 2008 BSOD 0x1000007E
> I'm using the 0.10.0.86 version of the driver - I can try the
> donotuse version, but I thought I understood that the main purpose of
> version was to test the driver signing requirements in the 64-bit
> Vista/2008. There's nothing real special about my setup...here's the
> config file:
> disk=[ 'file:/xenstore/vmdevel/Server2008/disk0,hda,w',
> 'file:/xenstore/iso/Windows/Server2008.iso,hdc:cdrom,r', ]
> vif=[ 'mac=00:16:3e:3a:50:a0,bridge=xenbr30,model=rtl8139,type=ioemu',
> I just did a clean install of Server 2008 Enterprise 32-bit, joined it
> domain, downloaded the GPLPV drivers (0.10.0.86 - this time I grabbed
> drivers) and tried, again, with the same result (0x7E). I've attached
> most recent output, including the !analyze -v output.
> >>> On 2009/09/06 at 01:51, "James Harper"
> > James,
> > Attached is a text file with the output from the WinDbg session I
> > the server. This error actually occurs during startup after
> attempting to
> > load the GPL PV drivers, but it's close to the error I get during
> > I couldn't get DebugView to give any output.
> I think the symbols are making sense but I'm not completely sure. Is
> windbg session done with the very latest binary version?
> If the symbols are correct, then it appears that the crash is
> when checking the id's of a pci devices... can you please email me a
> copy of your domain config? Are you passing through any pci devices?
> Anything else that might be unusual about your setup?
> This e-mail may contain confidential and privileged material for the
> of the intended recipient. If this email is not intended for you, or
> not responsible for the delivery of this message to the intended
> please note that this message may contain SEAKR Engineering (SEAKR)
> Privileged/Proprietary Information. In such a case, you are strictly
> prohibited from downloading, photocopying, distributing or otherwise
> this message, its contents or attachments in any way. If you have
> this message in error, please notify us immediately by replying to
> and delete the message from your mailbox. Information contained in
> message that does not relate to the business of SEAKR is neither
> nor attributable to SEAKR.