Re: [Xen-devel] [xen-4.0-testing test] 2032: regressions - FAIL

[Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>]

On Thu, 2010-08-19 at 08:42 +0100, Keir Fraser wrote:
> This looks more like the switch to xen/stable-2.6.32.x branch is to blame?
> Seeing as the baseline is immediately before that switch.
> 
> Is there a known-good changeset in the branch that we could try testing
> against?

I think we should try e6b9b2cbca5093e8e38d3e314e2f6415ad951c60. This is
the commit before e73f4955a821f850f5b88c32d12a81714523a95f which was
fingered as bad by the xen-unstable bisect yesterday.

e73f4 is the merge of 2.6.32.19, e6b9b is the merge of 2.6.32.18, there
are no proper xen.git changesets between the two -- only the contents of
2.6.32.19, which does include some Xen save/restore "fixes".

I'm still trying to repro in my environment but I think it likely that
either those fixes made something worse for configurations other than
the ones I test with (I'm going to pull in Ian's config) or that they
backported to 2.6.32 badly.

IanJ: Are the guest consoles logged anywhere by your test suite? If not
then could you apply this (perhaps to /etc/sysconfig/xencommons after
install rather than to the source tree) and
collect /var/log/xen/console.

diff -r e898a4d74a21 -r da1648640fd9 
tools/hotplug/Linux/init.d/sysconfig.xencommons
--- a/tools/hotplug/Linux/init.d/sysconfig.xencommons   Wed Aug 18 13:14:57 
2010 +0100
+++ b/tools/hotplug/Linux/init.d/sysconfig.xencommons   Wed Aug 18 13:14:57 
2010 +0100
@@ -1,5 +1,5 @@
 # Log xenconsoled messages (cf xl dmesg)
-#XENCONSOLED_TRACE=[none|guest|hv|all]
+XENCONSOLED_TRACE=guest
 
 # Log xenstored messages
 #XENSTORED_TRACE=[yes|on|1]

Thanks,
Ian.



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel