From: xen.org <ian.jackson@eu.citrix.com>
To: xen-devel@lists.xensource.com
Cc: ian.jackson@eu.citrix.com
Subject: [xen-4.0-testing test] 8085: regressions - trouble: broken/pass
Date: Sat, 16 Jul 2011 16:10:09 +0100 [thread overview]
Message-ID: <osstest-8085-mainreport@xen.org> (raw)
flight 8085 xen-4.0-testing real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/8085/
Regressions :-(
Tests which did not succeed and are blocking:
test-amd64-i386-pv 6 leak-check/basis(6) fail REGR. vs. 8010
test-i386-i386-pv 6 leak-check/basis(6) fail REGR. vs. 8010
test-amd64-amd64-pv 6 leak-check/basis(6) fail REGR. vs. 8015
test-amd64-i386-xl-multivcpu 6 leak-check/basis(6) fail REGR. vs. 8010
test-amd64-amd64-pair 10 leak-check/basis/dst_host(10) fail REGR. vs. 8015
test-amd64-amd64-pair 9 leak-check/basis/src_host(9) fail REGR. vs. 8015
test-i386-i386-xl 6 leak-check/basis(6) fail REGR. vs. 8010
test-amd64-i386-xl 6 leak-check/basis(6) fail REGR. vs. 8010
test-amd64-amd64-xl 6 leak-check/basis(6) fail REGR. vs. 8015
test-i386-i386-win 6 leak-check/basis(6) fail REGR. vs. 8010
test-amd64-amd64-win 6 leak-check/basis(6) fail REGR. vs. 8015
test-amd64-i386-rhel6hvm-intel 6 leak-check/basis(6) fail REGR. vs. 8010
test-i386-i386-pair 9 leak-check/basis/src_host(9) fail REGR. vs. 8010
test-i386-i386-pair 10 leak-check/basis/dst_host(10) fail REGR. vs. 8010
test-amd64-i386-pair 9 leak-check/basis/src_host(9) fail REGR. vs. 8010
test-amd64-i386-pair 10 leak-check/basis/dst_host(10) fail REGR. vs. 8010
test-amd64-i386-rhel6hvm-amd 6 leak-check/basis(6) fail REGR. vs. 8010
test-amd64-i386-win-vcpus1 6 leak-check/basis(6) fail REGR. vs. 8010
test-amd64-i386-win 6 leak-check/basis(6) fail REGR. vs. 8010
test-amd64-i386-xl-win-vcpus1 6 leak-check/basis(6) fail REGR. vs. 8010
test-amd64-amd64-xl-win 6 leak-check/basis(6) fail REGR. vs. 8015
test-i386-i386-xl-win 6 leak-check/basis(6) fail REGR. vs. 8010
Tests which did not succeed, but are not blocking,
including regressions (tests previously passed) regarded as allowable:
test-amd64-amd64-xl-pcipt-intel 6 leak-check/basis(6) fail never pass
test-amd64-i386-xl-credit2 6 leak-check/basis(6) fail blocked in 8015
version targeted for testing:
xen 89608751ccfc
baseline version:
xen a353b8304f7a
------------------------------------------------------------
People who touched revisions under test:
David Vrabel <david.vrabel@citrix.com>
Ian Campbell <ian.campbell@citrix.com>
Jan Beulich <jbeulich@novell.com>
Paul Durrant <paul.durrant@citrix.com>
------------------------------------------------------------
jobs:
build-amd64 pass
build-i386 pass
build-amd64-oldkern pass
build-i386-oldkern pass
build-amd64-pvops pass
build-i386-pvops pass
test-amd64-amd64-xl broken
test-amd64-i386-xl broken
test-i386-i386-xl broken
test-amd64-i386-rhel6hvm-amd broken
test-amd64-i386-xl-credit2 broken
test-amd64-amd64-xl-pcipt-intel broken
test-amd64-i386-rhel6hvm-intel broken
test-amd64-i386-xl-multivcpu broken
test-amd64-amd64-pair broken
test-amd64-i386-pair broken
test-i386-i386-pair broken
test-amd64-amd64-pv broken
test-amd64-i386-pv broken
test-i386-i386-pv broken
test-amd64-i386-win-vcpus1 broken
test-amd64-i386-xl-win-vcpus1 broken
test-amd64-amd64-win broken
test-amd64-i386-win broken
test-i386-i386-win broken
test-amd64-amd64-xl-win broken
test-i386-i386-xl-win broken
------------------------------------------------------------
sg-report-flight on woking.cam.xci-test.com
logs: /home/xc_osstest/logs
images: /home/xc_osstest/images
Logs, config files, etc. are available at
http://www.chiark.greenend.org.uk/~xensrcts/logs
Test harness code can be found at
http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary
Not pushing.
------------------------------------------------------------
changeset: 21521:89608751ccfc
tag: tip
user: Jan Beulich <jbeulich@novell.com>
date: Sat Jul 16 09:35:13 2011 +0100
x86: fix guest migration after c/s 20892:d311d1efc25e
Guests would not manage to run successfully after being migrated to a
host having sufficiently much more memory than the host they were
originally started on.
Subsequently the plan is to re-enable the changes behavior under the
control of a guest kernel announced feature flag.
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Acked-by: Ian Campbell <ian.campbell@citrix.com>
xen-unstable changeset: 23706:3dd399873c9e
xen-unstable date: Sat Jul 16 09:18:21 2011 +0100
changeset: 21520:fd9e72e1b1c3
user: David Vrabel <david.vrabel@citrix.com>
date: Sat Jul 16 09:34:57 2011 +0100
xen/libxc: set CPUID topology leaf as unsupported for PV guests
The result of a CPUID Extended Topology Enumeration leaf for PV guests
is invalid as the level in ECX is ignored. This can cause some guests
to loop endlessly when trying to enumerate the topology.
Since the physical topology isn't useful to PV guests set the topology
leaf as unsupported.
Guests affected include Linux kernels prior 2.6.32 where a workaround
was applied ("xen: mask extended topology info in cpu",
82d6469916c6fcfa345636a49004c9d1753905d1).
Signed-off-by: David Vrabel <david.vrabel@citrix.com>
xen-unstable changeset: 23700:867bb675b57b
xen-unstable date: Sat Jul 16 09:05:45 2011 +0100
changeset: 21519:a353b8304f7a
user: Paul Durrant <paul.durrant@citrix.com>
date: Fri Jul 08 09:02:03 2011 +0100
x86/hvm: Don't expose CPUID time leaf when not using PVRDTSCP
Some versions of Oracle's Solaris PV drivers make a check that the
maximal Xen hypervisor CPUID leaf is <= base leaf + 2 and refuse to
work if this is not the case. The addition of the time leaf makes the
maximal leaf == base leaf + 3 so this patch introduces a workaround
that obscures the time leaf unless PVRDTSCP is in operation.
Signed-off-by: Paul Durrant <paul.durrant@citrix.com>
xen-unstable changeset: 23661:8fe6f4be18aa
xen-unstable date: Fri Jul 08 08:31:10 2011 +0100
(qemu changes not included)
reply other threads:[~2011-07-16 15:10 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=osstest-8085-mainreport@xen.org \
--to=ian.jackson@eu.citrix.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.