Hi, During the install of the univention.de-signed GPLPV drivers (gplpv_Vista2008x64_signed_0.11.0.308.msi) on my Windows 7 guest, I get a BSOD "DRIVER_IRQL_NOT_LESS_OR_EQUAL" in xenvbd.sys. Afterwards, Windows won''t start. I''m now trying to do a System Restore. I will try not installing the VBD driver afterwards and see if the others do work. Full BSOD: http://jbeekman.nl/bsod20120117_1953.png ~ #xl info host : jethro release : 3.0.0-14-generic version : #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 machine : x86_64 nr_cpus : 4 nr_nodes : 1 cores_per_socket : 2 threads_per_core : 2 cpu_mhz : 2691 hw_caps : bfebfbff:28100800:00000000:00003f40:13bae3ff:00000000:00000001:00000000 virt_caps : hvm hvm_directio total_memory : 3978 free_memory : 861 free_cpus : 0 xen_major : 4 xen_minor : 1 xen_extra : .1 xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 hvm-3.0-x86_32p hvm-3.0-x86_64 xen_scheduler : credit xen_pagesize : 4096 platform_params : virt_start=0xffff800000000000 xen_changeset : unavailable xen_commandline : placeholder cc_compiler : gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) cc_compile_by : zulcss cc_compile_domain : ubuntu.com cc_compile_date : Tue Oct 11 07:31:13 UTC 2011 xend_config_format : 4 ~ #cat /etc/xen/Windows7.cfg name="Windows7" builder="hvm" memory="768" disk = [ ''phy:/dev/xenvg/windows7,hda,w'', ''file:/path/to/Windows7x64.iso,hdc:cdrom,r'' ] vif = [ ''type=vif,mac=6a:69:66:98:ce:b2'' ] vnclisten="127.0.0.1" xen_platform_pci=1 viridian=1 Any ideas how to resolve this issue? Jethro
This happened to me quite some time ago and I think I worked around it by booting windows without gplpv. You can do this by adding /nogplv to boot.ini On Tue, Jan 17, 2012 at 11:27 PM, Jethro Beekman <jethro@jbeekman.nl> wrote:> Hi, > > During the install of the univention.de-signed GPLPV drivers > (gplpv_Vista2008x64_signed_0.**11.0.308.msi) on my Windows 7 guest, I get > a BSOD "DRIVER_IRQL_NOT_LESS_OR_**EQUAL" in xenvbd.sys. Afterwards, > Windows won''t start. I''m now trying to do a System Restore. I will try not > installing the VBD driver afterwards and see if the others do work. > > Full BSOD: http://jbeekman.nl/**bsod20120117_1953.png<http://jbeekman.nl/bsod20120117_1953.png> > > ~ #xl info > host : jethro > release : 3.0.0-14-generic > version : #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 > machine s : x86_64 > nr_cpus : 4 > nr_nodes : 1 > cores_per_socket : 2 > threads_per_core : 2 > cpu_mhz : 2691 > hw_caps : bfebfbff:28100800:00000000:** > 00003f40:13bae3ff:00000000:**00000001:00000000 > virt_caps : hvm hvm_directio > total_memory : 3978 > free_memory : 861 > free_cpus : 0 > xen_major : 4 > xen_minor : 1 > xen_extra : .1 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3.0-x86_32p hvm-3.0-x86_64 > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=0xffff800000000000 > xen_changeset : unavailable > xen_commandline : placeholder > cc_compiler : gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) > cc_compile_by : zulcss > cc_compile_domain : ubuntu.com > cc_compile_date : Tue Oct 11 07:31:13 UTC 2011 > xend_config_format : 4 > > ~ #cat /etc/xen/Windows7.cfg > name="Windows7" > builder="hvm" > memory="768" > disk = [ ''phy:/dev/xenvg/windows7,hda,**w'', ''file:/path/to/Windows7x64.**iso,hdc:cdrom,r'' > ] > vif = [ ''type=vif,mac=6a:69:66:98:ce:**b2'' ] > vnclisten="127.0.0.1" > xen_platform_pci=1 > viridian=1 > > Any ideas how to resolve this issue? > > Jethro > > ______________________________**_________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/**xen-users<http://lists.xensource.com/xen-users> >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Of course you can, but then you won''t have GPLPV installed. I can confirm (by not installing xenvbd) that the other drivers do seem to work. Jethro On 17-01-12 21:06, chris wrote:> This happened to me quite some time ago and I think I worked around it by > booting windows without gplpv. You can do this by adding /nogplv to boot.ini > > On Tue, Jan 17, 2012 at 11:27 PM, Jethro Beekman <jethro@jbeekman.nl > <mailto:jethro@jbeekman.nl>> wrote: > > Hi, > > During the install of the univention.de-signed GPLPV drivers > (gplpv_Vista2008x64_signed_0.__11.0.308.msi) on my Windows 7 guest, I get a > BSOD "DRIVER_IRQL_NOT_LESS_OR___EQUAL" in xenvbd.sys. Afterwards, Windows > won''t start. I''m now trying to do a System Restore. I will try not > installing the VBD driver afterwards and see if the others do work. > > Full BSOD: http://jbeekman.nl/__bsod20120117_1953.png > <http://jbeekman.nl/bsod20120117_1953.png> > > ~ #xl info > host : jethro > release : 3.0.0-14-generic > version : #23-Ubuntu SMP Mon Nov 21 20:28:43 UTC 2011 > machine s : x86_64 > nr_cpus : 4 > nr_nodes : 1 > cores_per_socket : 2 > threads_per_core : 2 > cpu_mhz : 2691 > hw_caps : > bfebfbff:28100800:00000000:__00003f40:13bae3ff:00000000:__00000001:00000000 > virt_caps : hvm hvm_directio > total_memory : 3978 > free_memory : 861 > free_cpus : 0 > xen_major : 4 > xen_minor : 1 > xen_extra : .1 > xen_caps : xen-3.0-x86_64 xen-3.0-x86_32p hvm-3.0-x86_32 > hvm-3.0-x86_32p hvm-3.0-x86_64 > xen_scheduler : credit > xen_pagesize : 4096 > platform_params : virt_start=0xffff800000000000 > xen_changeset : unavailable > xen_commandline : placeholder > cc_compiler : gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3) > cc_compile_by : zulcss > cc_compile_domain : ubuntu.com <http://ubuntu.com> > cc_compile_date : Tue Oct 11 07:31:13 UTC 2011 > xend_config_format : 4 > > ~ #cat /etc/xen/Windows7.cfg > name="Windows7" > builder="hvm" > memory="768" > disk = [ ''phy:/dev/xenvg/windows7,hda,__w'', > ''file:/path/to/Windows7x64.__iso,hdc:cdrom,r'' ] > vif = [ ''type=vif,mac=6a:69:66:98:ce:__b2'' ] > vnclisten="127.0.0.1" > xen_platform_pci=1 > viridian=1 > > Any ideas how to resolve this issue? > > Jethro > > _________________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com <mailto:Xen-users@lists.xensource.com> > http://lists.xensource.com/__xen-users <http://lists.xensource.com/xen-users> > >
> > Thanks. That does seem to fix the problem, but when I try installing the non- > debug version, Windows complains about the signature. >Can you send me a screenshot of the signature complaint? Is it just asking for confirmation before installing? Thanks James
It seems to happen when you run the installer for either version while the other is still installed. See http://jbeekman.nl/GplPvSignatureWarning.png . I had trouble deinstalling the driver via the Control Panel, so I fixed it by going back to a restore point and then installing the non-debug version. I now have another problem. My network device and one of my two block devices say "This device cannot start. (Code 10).". The internet seems to think that this mostly happens with PCI-passthrough and USB devices, but that''s not the case here. I also got another random BSOD, but I can''t reproduce that (yet). Jethro On 17-01-12 22:17, James Harper wrote:>> >> Thanks. That does seem to fix the problem, but when I try installing the non- >> debug version, Windows complains about the signature. >> > > Can you send me a screenshot of the signature complaint? Is it just asking for confirmation before installing? > > Thanks > > James
> > It seems to happen when you run the installer for either version while the > other is still installed. See http://jbeekman.nl/GplPvSignatureWarning.png . I > had trouble deinstalling the driver via the Control Panel, so I fixed it by going > back to a restore point and then installing the non-debug version.I wonder if it doesn''t like having the same product installed with two different signatures or something? I''ve installed my signed version over the top of my testsigned version without any problems before. Or maybe the extra mucking around you''ve had to do might have upset something somewhere.> I now have another problem. My network device and one of my two block > devices say "This device cannot start. (Code 10).". The internet seems to > think that this mostly happens with PCI-passthrough and USB devices, but > that''s not the case here. > > I also got another random BSOD, but I can''t reproduce that (yet). >If you use the _debug drivers from meadowcourt.org and can get me the memory.dmp file (or minidump file) I should be able to run it through the debugger easily enough. The exception would be a really old version where I''ve purged the symbol files from my build station. If it doesn''t write a memory dump then the /var/log/xen/qemu-dm-<domu name>.log file might be useful. What other software are you running on the system? I''ve seen problems with some antivirus software before with GPLPV. James
Nothing on the ''code 10'' front? When I figure out how to reproduce that BSOD I will certainly try to send you a memory dump. I''m not running any other software, this is a clean install. Jethro On 18-01-12 00:20, James Harper wrote:>> >> It seems to happen when you run the installer for either version while the >> other is still installed. See http://jbeekman.nl/GplPvSignatureWarning.png . I >> had trouble deinstalling the driver via the Control Panel, so I fixed it by going >> back to a restore point and then installing the non-debug version. > > I wonder if it doesn''t like having the same product installed with two different signatures or something? I''ve installed my signed version over the top of my testsigned version without any problems before. > > Or maybe the extra mucking around you''ve had to do might have upset something somewhere. > >> I now have another problem. My network device and one of my two block >> devices say "This device cannot start. (Code 10).". The internet seems to >> think that this mostly happens with PCI-passthrough and USB devices, but >> that''s not the case here. >> >> I also got another random BSOD, but I can''t reproduce that (yet). >> > > If you use the _debug drivers from meadowcourt.org and can get me the memory.dmp file (or minidump file) I should be able to run it through the debugger easily enough. The exception would be a really old version where I''ve purged the symbol files from my build station. If it doesn''t write a memory dump then the /var/log/xen/qemu-dm-<domu name>.log file might be useful. > > What other software are you running on the system? I''ve seen problems with some antivirus software before with GPLPV. > > James >