Re: [win-pv-devel] Initial driver release

[Fabio Fantoni <fabio.fantoni@xxxxxxx>]

Il 04/09/2015 16:21, Paul Durrant ha scritto:
> > -----Original Message-----
> > From: Fabio Fantoni [mailto:fabio.fantoni@xxxxxxx]
> > Sent: 04 September 2015 15:13
> > To: Paul Durrant; win-pv-devel@xxxxxxxxxxxxxxxxxxxx
> > Subject: Re: [win-pv-devel] Initial driver release
> >
> > Il 04/09/2015 15:08, Paul Durrant ha scritto:
> > > Hi,
> > >
> > >     We've been working hard here in Citrix to test all the (now) 8.1 drivers
> > and I think we're getting close to having all our tests and the latest Microsoft
> > logo tests pass. Hence I think it's probably time to create a 8.1-staging branch
> > for each of the drivers and tag an 8.1.0-rc1 for each of the drivers. I'll then
> > bump the versions in the master branches to 8.2.
> > >     Cheers,
> > >
> > >       Paul
> > Big thanks for all your work.
> > About signed drivers with xen project, are there any news? at least
> > build each component rc and stable builds with a certificate to avoid
> > windows 10 problem in case of automatic boot repair and major update
> > (seems only when windows build number increase) where after windows is
> > unable to boot (seems that disable testsigning) on domUs where new pv
> > drivers unsigned are installed, W10 (on same dom0 and with same xl
> > parameters) with gplpv signed are still working instead.
> > If I remember good this is blue screen of first case (after tried
> > windows auto boot repair) and the second is same:
> > http://lists.xen.org/archives/html/win-pv-devel/2015-
> > 08/pngS7ZYFAuB3k.png
> Windows 10's behaviour does seem to be annoying. I think getting an EV cert and 
> signing release builds is probably feasible but there's no way we can sign 
> every development build via the Microsoft portal so to some extent everyone is 
> going to have to live with the problem by turning test-signing on and 
> re-enabling after any such update (assuming you can still hit F8 and disable 
> signature verification to allow the VM to boot).
>
>    Paul
I already tried F8 (before windows load and also on blue screen) and 
enter on blue screen in many way but I not found working "repair" 
solution for now. I suppose that there a windows bug about. I not tried 
latest insider build for now (I'll try probably next week).
In any case now that windows (10) is a "rolling-release" with automatic 
update "mandatory" (only delayable) is a big problem.
Any workaround for devel builds (still unsigned) on testing systems it 
is appreciated but signing of stable release for production windows 10 
domUs seems needed or will be a "bloodbath" each time that W10 
automatically disabled testsigning :(
Thanks for any reply and sorry for my bad english.

_______________________________________________
win-pv-devel mailing list
win-pv-devel@xxxxxxxxxxxxxxxxxxxx
http://lists.xenproject.org/cgi-bin/mailman/listinfo/win-pv-devel