On Sat, Apr 4, 2009 at 2:53 PM, Fajar A. Nugraha <fajar@xxxxxxxxx> wrote:
> So I just tried it on Linux dom0, Windows 2008 x64, and found out two things:
> - Your signing script is correct, but Windows needs additional setting.
> From
> http://www.mydigitallife.info/2008/02/26/unable-to-disable-integrity-checks-cause-drivers-not-found-in-64-bit-vista-x64/
> , I have to run "bcdedit.exe /set TESTSIGNING ON" to have Windows
> honor testsign drivers. Perhaps you should update instructions on
> http://wiki.xensource.com/xenwiki/XenWindowsGplPv/Installing
> - Xen vbd works, but Xen Net doesn't work. It says "Windows cannot
> load the device driver for this hardware. The driver may be corrupted
> or missing (Code 39)". Realtek NIC is also not working (which is
> correct when GPLV active), which leaves me no NIC.
Upon further testing on Linux dom0, I find out that "testsigning"
behaves differently from "Disable driver signing enforcement" for
GPLV.
- With "testsigning" : Xen vbd works, Xen net does not work (which is
what I posted above)
- With "Disable driver signing enforcement": both Xen vbd and Xen net works.
Is it possible that perhaps with "testsigning" Xen net (incorrectly)
assume that it's on safe mode and thus refused to start?
WIth Opensolaris dom0, the behavior is somewhat similar to Linux dom0
with the difference that :
- with "testsigning": Xennet refused to start (with yellow
exclamantion mark) on both 0.9.12-pre13 and 0.10.0.47 while Xen vbd
works correctly (the same behavior as Linux dom0)
- with 0.9.12-pre13 and "Disable driver signing enforcement" : xen net
works if I set LSO off
- with 0.10.0.47 and "Disable driver signing enforcement" : xen net
seems to start, but no packet pass through. Perhaps I need to disable
some more offload, will check later.
Regards,
Fajar
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home