WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

[Xen-users] Disabling driver signature enforcement for Windows DomUs

To: Xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Disabling driver signature enforcement for Windows DomUs
From: Adam Wead <awead@xxxxxxxxxxx>
Date: Wed, 6 May 2009 13:37:33 -0400
Cc:
Delivery-date: Wed, 06 May 2009 10:38:15 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Hi all,

After loading the GplPV drivers for Windows Server 2008, I wanted to get rid of the annoying F8 option when rebooting each time. I looked at Ready Driver Plus, which seemed to work, but was only a workaround. It also seemed to kill my terminal connection from Dom0. After some research, I found another way:

http://www.ngohq.com/home.php?page=dseo

Which will disable driver signature enforcement. Also, it's reversible too. Here's a breakdown of what I did:

- started with clean install of Windows Server 2008 Enterprise (64-bit)
- installed latest GplPV drivers, verified everything was working with the driver enforcement enabled at each boot - as per DSEO instructions, disabled all User Account Controls via windows secpol.msc snap-in
- installed DSEO and enabled test mode
- reboot
- GplPV drivers came up disabled, so I reinstalled the GplPV drivers, then ran DSEO and test singed each xen file under C:\Windows \system32\drivers which was about 4 files total
- reboot
- OS booted up without prompting for driver enforcement override
- re-enabled the User Account Controls, and rebooted to verify that everything was still working

I'd be curious to know if this works or not for anyone else. For now, I'm moving on to do more tests on my windows DomU, and hoping that I can put the driver enforcement issue behind me.

...adam




Attachment: smime.p7s
Description: S/MIME cryptographic signature

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
<Prev in Thread] Current Thread [Next in Thread>