From: Paul Durrant <Paul.Durrant@citrix.com>
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" <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: Thu, 14 Sep 2017 14:33:33 +0000 [thread overview]
Message-ID: <3f2d1e4d6ba14e7fb62dad5d13f512f0@AMSPEX02CL03.citrite.net> (raw)
In-Reply-To: <716c4b02-8952-3ae5-331b-0197ee0b888c@arm.com>
> -----Original Message-----
> From: Julien Grall [mailto:julien.grall@arm.com]
> Sent: 14 September 2017 03:49
> 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 13/09/17 19:26, Paul Durrant wrote:
> >> -----Original Message-----
> >> From: Xen-devel [mailto:xen-devel-bounces@lists.xen.org] On Behalf Of
> >> Julien Grall
> >> Sent: 13 September 2017 10:52
> >> To: 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: [Xen-devel] Windows "heinsenbug" (WAS: Re: Notes Design
> >> Session: Making Releases Lessons Learned: Improving Our Release
> Process
> >> and Tooling)
> >>
> >> Hi all,
> >>
> >> On 07/27/2017 05:56 PM, Ian Jackson wrote:
> >>> Jan Beulich writes ("Re: Notes Design Session: Making Releases Lessons
> >> Learned: Improving Our Release Process and Tooling"):
> >>>> [Lars:]
> >>>>> Ian: These are most likely software problems, most likely in Xen.
> >>>>> ISSUE: nobody wants to debug Windows Heisenbugs
> >>>>
> >>>> Hmm, I think we believe to have understood what the issue is, it's just
> >> that
> >>>> the change needed is on the tool stack side (gracefully deal with a
> domain
> >>>> rebooting while being migrated).
> >>>
> >>> No, the problem is that we don't understand why the domain is
> >>> rebooting. It should not be.
> >>
> >> This bug still seem to be around and likely going to impact once again
> >> the release testing.
> >>
> >> As discussed during the summit, I am really thinking to make this
> >> "heinsenbug" a blocker until somehow finally spend sometimes
> >> investigating the problem and suggest actions.
> >
> > If testing was done with PV drivers installed then we could get a lot more
> information into the logs. BSODs vs. clean shutdowns (perhaps due to
> Windows Update) would then become obvious.
>
> Would it be feasible to get those installed in osstest?
>
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.
Cheers,
Paul
> Cheers,
>
> --
> Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-09-14 14:33 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 [this message]
2017-09-25 21:32 ` Julien Grall
2017-09-26 7:41 ` Paul Durrant
2017-10-09 15:54 ` Paul Durrant
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=3f2d1e4d6ba14e7fb62dad5d13f512f0@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).