All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: "Tian, Kevin" <kevin.tian@intel.com>,
	"Hu, Robert" <robert.hu@intel.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	"Nakajima, Jun" <jun.nakajima@intel.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	osstest service owner <osstest-admin@xenproject.org>,
	Jan Beulich <jbeulich@suse.com>
Subject: Re: [xen-unstable test] 65141: regressions - FAIL
Date: Thu, 3 Dec 2015 09:25:47 +0000	[thread overview]
Message-ID: <1449134747.4424.106.camel@citrix.com> (raw)
In-Reply-To: <AADFC41AFE54684AB9EE6CBC0274A5D15F72B198@SHSMSX101.ccr.corp.intel.com>

On Thu, 2015-12-03 at 05:58 +0000, Tian, Kevin wrote:
> > From: Ian Campbell [mailto:ian.campbell@citrix.com]
> > Sent: Wednesday, December 02, 2015 9:51 PM
> > > 
> > > According to
> > > http://osstest.test-lab.xenproject.org/~osstest/pub/results/bisect/xe
> > > n-un
> > > stable/test-amd64-amd64-qemuu-nested-intel.debian-hvm-install--l1
> > > --l2.html
> > > it was unable to reproduce a baseline, probably because it didn't
> > > have
> > > enough historical data.
> > 
> > So I have run an adhoc test of the version of Xen tested by flight
> > 64494,
> > i.e. the one which passed on godello under the old job name test-amd64-
> > amd64-qemuu-nested but using the new name and current test harness and
> > it
> > was successful:
> > 
> > http://osstest.test-lab.xenproject.org/~osstest/pub/logs/65301/
> > 
> > I think that ought to give a baseline for the bisector to work with.
> > I'll
> > prod it to do so.
> > 
> > Given the number of commits I expect this is going to take a little
> > while
> > to produce results, given that the regression is already a week old it
> > would be good if the VT-d maintainers could investigate in parallel.
> 
> Is the test case VT-d related? From earlier thread looks it's related to
> nested virtualization?

It's the nested-vmx/VT-x test case which Intel contributed to osstest over
the last few months. AFAIK VT-d is not involved in any way (no passthrough
etc).

> I can't access above link. If you can help describe the test steps in
> plain text, I can check whether we can reproduce locally.

Sorry, I hadn't spotted that the adhoc link was internal to the colo when I
c&p'd it.

This test case has failed in the last half-dozen real xen-unstable flights,
including the one which started this thread and the latest one which is at 
http://logs.test-lab.xenproject.org/osstest/logs/65287/test-amd64-amd64-qemuu-nested-intel/info.html

The test case is installing Xen in an HVM guest to produce an L1 host and
then trying to boot an L2 HVM guest within that L1, which fails.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

  reply	other threads:[~2015-12-03  9:25 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-27 15:45 [xen-unstable test] 65141: regressions - FAIL osstest service owner
2015-11-27 15:54 ` Ian Jackson
2015-11-30  5:35   ` Hu, Robert
2015-12-02 10:34     ` Ian Campbell
2015-12-02 10:52       ` Jan Beulich
2015-12-02 10:57         ` Andrew Cooper
2015-12-02 11:07         ` Ian Campbell
2015-12-02 13:51       ` Ian Campbell
2015-12-03  5:58         ` Tian, Kevin
2015-12-03  9:25           ` Ian Campbell [this message]
2015-12-05  8:09         ` Ian Campbell
2015-12-07 16:18           ` Jan Beulich
2015-12-07 16:28             ` Ian Campbell
2015-12-07 16:48               ` Jan Beulich
2015-12-08  2:46             ` Tian, Kevin
2015-12-08  7:28               ` Jan Beulich
2015-12-08  8:06           ` Hu, Robert
2015-12-08 10:29             ` Ian Campbell
2015-12-09  6:27               ` Robert Hu
2015-12-09  8:35                 ` Jin, Gordon
2015-12-09 10:21                   ` Ian Campbell
2015-12-11  4:04               ` Robert Hu
2015-12-11 11:49                 ` Ian Campbell

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=1449134747.4424.106.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=jun.nakajima@intel.com \
    --cc=kevin.tian@intel.com \
    --cc=osstest-admin@xenproject.org \
    --cc=robert.hu@intel.com \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.