Xen users - May 2009 - gplpv driver signature problem under win2k8_64bit

Hi, 

I am at a complete loss of ideas here: 

I have a
- xen3.3.1 hypervisor compiled from source with
- dom0 being 2.6.26-1-xen-amd64 kernel from debian/lenny repository with
- windows 2008 64bit as hvm guest.
I use the gplpv drivers 0.10.0.69 from James Harper. 

The included files (xenpci.sys and xennet.sys) are apparently test-signed,
so applying test-signing as boot option does enable windows to boot 

bcdedit /set testsigning on 

without this, windows complaints about xenpci.sys not beeing digitally
signed. 

BUT even with test signing enabled, the network device does not work. The
Device Manager reports an Error Code 39 for the Xen PV Net Device. 

when I manually choose the F8 option "Disable digital signature
verification" at boot time (on every boot), everything works fine. 

I have also tried to test-sign the files with signtool.exe from the
windows sdk, but I think I could not grasp the concept and made something
wrong.
However, as James Harper seemed to already have
test signed the .sys
files, there should be no need to use signtool.exe 

Has anybody any idea what I could try to make this work? 

I am already brute-forcing any possible configuration, but could not find
a working solution so far. 

There where other reports on this list, that the above combination does
not work for unknown reasons.
If there is no solution to this problem, maybe there are some hints where
I could start debugging the problem? 

thanks a lot, 

Max-Julian Pogner 

 

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

On Tue, May 26, 2009 at 1:35 AM,  <mjp@netmonic.com>
wrote:
> BUT even with test signing enabled, the network device does not work. The
> Device Manager reports an Error Code 39 for the Xen PV Net Device.
>
> when I manually choose the F8 option "Disable digital signature
> verification" at boot time (on every boot), everything works fine.
It''s a known problem.
> Has anybody any idea what I could try to make this work?
Workarounds (search these in google):
- ready driver plus
- dseo. Use it to to resign xennet.sys and enable testsigning

-- 
Fajar

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

> Workarounds (search these in google):
> - ready driver plus
> - dseo. Use it to to resign xennet.sys and enable testsigning
I have already tried dseo, but it did not work (Still Code 39 in Device
Manager at the NIC).

For the ReadyDriverPlus, I only find a not-so-trustworthy looking
Homepage. Could you please point me to the ReadyDriverPlus project homepage?


thanks,

Max-Julian Pogner

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

On Tue, May 26, 2009 at 3:23 PM, Max-Julian Pogner <mjp@netmonic.com>
wrote:
>> Workarounds (search these in google):
>> - ready driver plus
>> - dseo. Use it to to resign xennet.sys and enable testsigning
>
> I have already tried dseo, but it did not work (Still Code 39 in Device
> Manager at the NIC).
Weird. It worked for me. Did you re-sign xennet.sys using dseo? What
does file properties page say about the signature?
This is actually the best method if you want to use testsigning (well,
either this, or create selfsigned certificates yourself)
>
> For the ReadyDriverPlus, I only find a not-so-trustworthy looking
> Homepage. Could you please point me to the ReadyDriverPlus project
homepage?
http://www.citadelindustries.net/readydriverplus/index.php :D
It basically automates the process of choosing disable signature
enforcement on Windows boot menu (you can see the cursor moving in the
process). Somewhat funny :)

-- 
Fajar

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