Re: [Xen-devel] Windows "heinsenbug" (WAS: Re: Notes Design Session: Making Releases Lessons Learned: Improving Our Release Process and Tooling)

[Paul Durrant <Paul.Durrant@xxxxxxxxxx>]

> -----Original Message-----
> From: Xen-devel [mailto:xen-devel-bounces@xxxxxxxxxxxxx] On Behalf Of
> Paul Durrant
> Sent: 26 September 2017 08:41
> To: 'Julien Grall' <julien.grall@xxxxxxx>; Ian Jackson
> <Ian.Jackson@xxxxxxxxxx>; Jan Beuli ch <jbeulich@xxxxxxxx>
> Cc: Juergen Gross <jgross@xxxxxxxx>; Wei Liu <wei.liu2@xxxxxxxxxx>;
> ross.philipson@xxxxxxxxx; lars.kurth.xen@xxxxxxxxx; xen-
> devel@xxxxxxxxxxxxx; committers@xxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] Windows "heinsenbug" (WAS: Re: Notes Design
> Session: Making Releases Lessons Learned: Improving Our Release Process
> and Tooling)
> 
> > -----Original Message-----
> > From: Julien Grall [mailto:julien.grall@xxxxxxx]
> > Sent: 25 September 2017 22:32
> > To: Paul Durrant <Paul.Durrant@xxxxxxxxxx>; Ian Jackson
> > <Ian.Jackson@xxxxxxxxxx>; Jan Beuli ch <jbeulich@xxxxxxxx>
> > Cc: Juergen Gross <jgross@xxxxxxxx>; Wei Liu <wei.liu2@xxxxxxxxxx>;
> > ross.philipson@xxxxxxxxx; lars.kurth.xen@xxxxxxxxx; xen-
> > devel@xxxxxxxxxxxxx; committers@xxxxxxxxxxxxxx
> > Subject: Re: [Xen-devel] Windows "heinsenbug" (WAS: Re: Notes Design
> > Session: Making Releases Lessons Learned: Improving Our Release Process
> > and Tooling)
> >
> > Hi Paul,
> >
> > On 09/14/2017 03:33 PM, Paul Durrant wrote:
> > > Julien,
> > >
> > >    That should not be too hard. We have a driver install agent for
> XenServer
> > that will manage all the necessary driver staging and required reboots.
> > Hopefully it should mainly be a question of building that installer to pick 
> > up
> > drivers from the upstream master branches rather than the internal
> > XenServer branches. AFAIK osstest is using XenRT customized Windows
> > images so hopefully we can use the slipstreamed XenRT agent to then
> fetch
> > and run the driver installer. IIRC it sets some form of cookie in xenstore
> once
> > it is done, so the rest of the test cycle would just need to wait for that 
> > to
> > appear. >
> > >    I'll look into how to progress this when I get back from the US.
> >
> > I wanted to bump the discussion. Do you have any update here?
> >
> 
> A bit snowed for the next day or so, and unfortunately Ben (who maintains
> the installer) is on vacation until next week. I'll try to use a vanilla 
> XenServer
> installer in a VM running on upstream and see if that works. If it does then
> we can probably just include running that in the osstest sequence. Using
> XenServer  PV drivers is probably prudent anyway, since they have already
> undergone extensive testing (albeit in a slightly different environment).
> 

Happily I finally found some time to look into this and the news is good... I 
took the latest XenServer driver installer and ran it inside a Windows 10 VM on 
one of my upstream test rigs and it ran to completion (managing the necessary 
reboots to displace emulated devices) in non-interactive mode with no problems, 
so this could definitely be used in osstest to get PV drivers into Windows VMs 
as longs as osstest can handle waiting for the intaller's "I'm finished" flag 
to appear in xenstore (attr/PVAddons/Installed = 1).

  Paul

>   Paul
> 
> > Cheers,
> >
> > --
> > Julien Grall
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> https://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel