[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] BSOD after installing EJB Digital GPLPV Drivers on fresh Windows 2008 R2 Enterprise

  • To: Jan Hejl <jh@xxxxxxxxxx>, "xen-users@xxxxxxxxxxxxx" <xen-users@xxxxxxxxxxxxx>
  • From: James Harper <james.harper@xxxxxxxxxxxxxxxx>
  • Date: Wed, 8 Jan 2014 00:06:05 +0000
  • Accept-language: en-AU, en-US
  • Delivery-date: Wed, 08 Jan 2014 00:07:40 +0000
  • List-id: Xen user discussion <xen-users.lists.xen.org>
  • Thread-index: AQHPC7LPNigXDkd0MEaHGJL3FvTzc5p58eKw
  • Thread-topic: [Xen-users] BSOD after installing EJB Digital GPLPV Drivers on fresh Windows 2008 R2 Enterprise

> Hi everyone,
> i've just installed new (clean and fully updated) Windows 2008 R2
> Enterprise domU on Xen 4.3.1-r1 (Gentoo, hardened, kernel 3.11.2) as
> PVHVM and tried to install GPLPV to make it work as proper PVHVM domU.
> But after installing the newest signed drivers from
> http://www.ejbdigital.com.au/GPLPV/ (doesn't matter which version) it
> seems fine until reboot. Then it throws BSOD with
> DRIVER_IRQL_NOT_LESS_OR_EQUAL (see attached image).
> Same problem with older Univention drivers.
> When I remove vif device from xen config file, windows domU goes fine,
> but it's useless without internet connection.
> Any ideas what can be wrong? Disabling IPv6 through regedit didn't help
> at all.
> vif = [
>       'bridge=xenbr1, script=vif-bridge, mac=00:16:3e:58:cc:24,
> model=e1000'
> ]

Can you try omitting the model from the vif declaration? That's the only 
difference I can see between yours and my servers.

The crashing driver is reported as sacdrv.sys, but that's part of the OS as far 
as I can tell. Maybe there is something about the e1000 driver that windows 
doesn't like having it unplugged by GPLPV?


Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.