xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Paul Durrant <Paul.Durrant@citrix.com>
To: Paul Durrant <Paul.Durrant@citrix.com>,
	'Julien Grall' <julien.grall@arm.com>,
	Ian Jackson <Ian.Jackson@citrix.com>,
	Jan Beuli ch <jbeulich@suse.com>
Cc: Juergen Gross <jgross@suse.com>, Wei Liu <wei.liu2@citrix.com>,
	"ross.philipson@gmail.com" <ross.philipson@gmail.com>,
	"lars.kurth.xen@gmail.com" <lars.kurth.xen@gmail.com>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"committers@xenproject.org" <committers@xenproject.org>
Subject: Re: Windows "heinsenbug" (WAS: Re: Notes Design Session: Making Releases Lessons Learned: Improving Our Release Process and Tooling)
Date: Mon, 9 Oct 2017 15:54:17 +0000	[thread overview]
Message-ID: <f95308f8415b42f8afe9aeba5d517ae6@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <3a3a829c78ba46b49918d038b5277ac2@AMSPEX02CL03.citrite.net>

> -----Original Message-----
> From: Xen-devel [mailto:xen-devel-bounces@lists.xen.org] On Behalf Of
> Paul Durrant
> Sent: 26 September 2017 08:41
> To: 'Julien Grall' <julien.grall@arm.com>; Ian Jackson
> <Ian.Jackson@citrix.com>; Jan Beuli ch <jbeulich@suse.com>
> Cc: Juergen Gross <jgross@suse.com>; Wei Liu <wei.liu2@citrix.com>;
> ross.philipson@gmail.com; lars.kurth.xen@gmail.com; xen-
> devel@lists.xen.org; committers@xenproject.org
> 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@arm.com]
> > Sent: 25 September 2017 22:32
> > To: Paul Durrant <Paul.Durrant@citrix.com>; Ian Jackson
> > <Ian.Jackson@citrix.com>; Jan Beuli ch <jbeulich@suse.com>
> > Cc: Juergen Gross <jgross@suse.com>; Wei Liu <wei.liu2@citrix.com>;
> > ross.philipson@gmail.com; lars.kurth.xen@gmail.com; xen-
> > devel@lists.xen.org; committers@xenproject.org
> > 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@lists.xen.org
> https://lists.xen.org/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

      reply	other threads:[~2017-10-09 15:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-18 12:18 Notes Design Session: Making Releases Lessons Learned: Improving Our Release Process and Tooling Lars Kurth
2017-07-26 12:53 ` Lars Kurth
2017-07-26 15:33   ` Lars Kurth
2017-07-27 16:54 ` Jan Beulich
2017-07-27 16:56   ` Ian Jackson
2017-09-13 17:51     ` Windows "heinsenbug" (WAS: Re: Notes Design Session: Making Releases Lessons Learned: Improving Our Release Process and Tooling) Julien Grall
2017-09-13 18:26       ` Paul Durrant
2017-09-14 10:49         ` Julien Grall
2017-09-14 14:33           ` Paul Durrant
2017-09-25 21:32             ` Julien Grall
2017-09-26  7:41               ` Paul Durrant
2017-10-09 15:54                 ` Paul Durrant [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f95308f8415b42f8afe9aeba5d517ae6@AMSPEX02CL03.citrite.net \
    --to=paul.durrant@citrix.com \
    --cc=Ian.Jackson@citrix.com \
    --cc=committers@xenproject.org \
    --cc=jbeulich@suse.com \
    --cc=jgross@suse.com \
    --cc=julien.grall@arm.com \
    --cc=lars.kurth.xen@gmail.com \
    --cc=ross.philipson@gmail.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xen.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).