Re: [Xen-devel] [qemu-upstream-4.2-testing test] 16779: regressions - FAIL

[Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>]

xen.org writes ("[qemu-upstream-4.2-testing test] 16779: regressions - FAIL"):
> flight 16779 qemu-upstream-4.2-testing real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/16779/
> 
> Regressions :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  test-i386-i386-xl-qemuu-winxpsp3  7 windows-install       fail REGR. vs. 
> 15122

This is a persistent failure.

> version targeted for testing:
>  qemuu                eccc68722696864fc4823f048c7be58d11281b97
> baseline version:
>  qemuu                70454385eeee6f0b3f7a9eddca9f7340b5060824

Looking at the changes, it seems likely to be related to the migration
dirty bit tracking series.  These were originally written by Anthony
Perard and committed to qemu-upstream-unstable where they work, and
then backported by Alex Blight.

So the problem is probably something in Alex's backports ?

The logs show this, most relevantly:

  Mar  1 09:19:52 field-cricket kernel: [   74.765641]
  qemu-system-i38[2474]: segfault at b909fed0 ip b77b3b3e sp bff1bae0
  error 6 in qemu-system-i386[b7554000+2a5000]

I'm afraid we don't have a stack backtrace.

qemu seems to have printed this:

  DSsDSsDSsDSs

which is a bit odd!


We want to be able to release Xen 4.2 soon.  Our next step is probably
to revert the migration changes so that we have a tree which works as
well as it did before.

Ian.

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