I need a head check, if you please. I've been playing with Windows Server 2008 R2 and Windows 7 (Ultimate; full release) on snv_121; both domU's are 64bit OS's. By default the emulated Realtek NIC seems to work fine if:
1) You don't mind being capped at 100Mbps 2) You are on an untagged network Even though I'm bridging to a VNIC which has a vlanid attached, Windows doesn't want to talk on a tagged network. So I was forced down the PV Driver path. After playing with several different drivers (http://www.meadowcourt.org/downloads/) and reading around on mailing lists, I got results with "gplpv_fre_wlh_AMD64_0.10.0.130.msi". On Windows7 it installed with no modifications, I reboot and everything is dandy. However, on Windows Server 2008 R2 I install it and reboot only to be greated by a recovery screen. If I rollback the ZVol and first put it in "testsigning" mode (bcdedit /set testsigning on) and then install the msi above everything goes well. So I'm curious why I need to put it in testsigning mode in one case but not the other. Furthermore, is there a way around this? I thought I saw that you can sign it yourself but not a procedure. On a side note... I tried the latest driver ("gplpv_Vista2008x64_0.11.0.188.msi") and it won't even install. Claims that it needs test mode on and 64bit... but it is in test mode, rebooted and is a 64bit install; so I don't know what thats all about. I can only think that the 0.11 version drivers are for Xen 3.4 instead of Xen 3.3? I've got things working but I could use some help filling in the gaps of my understanding. benr. -- This message posted from opensolaris.org _______________________________________________ xen-discuss mailing list [email protected]
