Re: [Xen-devel] [xen-unstable test] 65141: regressions - FAIL

[Ian Campbell <ian.campbell@xxxxxxxxxx>]

On Thu, 2015-12-03 at 05:58 +0000, Tian, Kevin wrote:
> > From: Ian Campbell [mailto:ian.campbell@xxxxxxxxxx]
> > 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@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel