flight 2032 xen-4.0-testing real
http://www.chiark.greenend.org.uk/~xensrcts/logs/2032/
Regressions :-(
tests which did not succeed:
test-amd64-amd64-pair 12 guest-migrate/src_host/dst_host fail never pass
test-amd64-amd64-pv 9 guest-localmigrate fail REGR. vs. 1993
test-amd64-amd64-xl 10 guest-stop fail never pass
test-amd64-i386-pair 12 guest-migrate/src_host/dst_host fail REGR. vs. 1993
test-amd64-i386-pv 8 guest-saverestore fail REGR. vs. 1993
test-amd64-i386-win 5 windows-install fail REGR. vs. 1993
test-amd64-i386-xl 9 guest-localmigrate fail REGR. vs. 1993
test-amd64-xcpkern-i386-xl 10 guest-stop fail never pass
test-i386-i386-pair 12 guest-migrate/src_host/dst_host fail never pass
test-i386-i386-pv 9 guest-localmigrate fail REGR. vs. 1993
test-i386-i386-win 5 windows-install fail REGR. vs. 1993
test-i386-i386-xl 8 guest-saverestore fail REGR. vs. 1993
test-i386-xcpkern-i386-pair 12 guest-migrate/src_host/dst_host fail like 1993
test-i386-xcpkern-i386-xl 10 guest-stop fail never pass
version targeted for testing:
xen 5e8df2d2ef6f
baseline version:
xen 8e8dd38374e9
jobs:
build-amd64 pass
build-amd64-oldkern pass
build-i386 pass
build-i386-oldkern pass
build-i386-xcpkern pass
test-amd64-amd64-pair fail
test-amd64-amd64-pv fail
test-amd64-amd64-win pass
test-amd64-amd64-xl fail
test-amd64-i386-pair fail
test-amd64-i386-pv fail
test-amd64-i386-win fail
test-amd64-i386-xl fail
test-amd64-xcpkern-i386-pair pass
test-amd64-xcpkern-i386-pv pass
test-amd64-xcpkern-i386-win pass
test-amd64-xcpkern-i386-xl fail
test-i386-i386-pair fail
test-i386-i386-pv fail
test-i386-i386-win fail
test-i386-i386-xl fail
test-i386-xcpkern-i386-pair fail
test-i386-xcpkern-i386-pv pass
test-i386-xcpkern-i386-win pass
test-i386-xcpkern-i386-xl fail
-------------------------------------------------------------------------------
build-amd64:
1 host-install(1) pass
2 host-build-prep pass
3 xen-build pass
linux e73f4955a821f850f5b8
qemu 0a940d892e90c820567c
xen 21321:5e8df2d2ef6f
-------------------------------------------------------------------------------
build-amd64-oldkern:
1 xen-build pass
linux 1025:042c8cd71081
qemu 0a940d892e90c820567c
xen 21321:5e8df2d2ef6f
-------------------------------------------------------------------------------
build-i386:
1 host-install(1) pass
2 host-build-prep pass
3 xen-build pass
linux e73f4955a821f850f5b8
qemu 0a940d892e90c820567c
xen 21321:5e8df2d2ef6f
-------------------------------------------------------------------------------
build-i386-oldkern:
1 xen-build pass
linux 1025:042c8cd71081
qemu 0a940d892e90c820567c
xen 21321:5e8df2d2ef6f
-------------------------------------------------------------------------------
build-i386-xcpkern:
1 kernel-build pass
linux 110879:32fc6955a6a5
pq_linux 154:61499f9e9a87
-------------------------------------------------------------------------------
test-amd64-amd64-pair:
1 xen-build-check(1) pass
2 host-install/src_host(2) pass
3 host-install/dst_host(3) pass
4 xen-install/src_host pass
5 xen-install/dst_host pass
6 xen-boot/src_host pass
7 xen-boot/dst_host pass
8 debian-install/dst_host pass
9 debian-fixup/dst_host pass
10 guests-nbd-mirror pass
11 guest-start pass
12 guest-migrate/src_host/dst_host fail
13 capture-logs/src_host(13) pass
14 capture-logs/dst_host(14) pass
-------------------------------------------------------------------------------
test-amd64-amd64-pv:
1 xen-build-check(1) pass
2 host-install(2) pass
3 xen-install pass
4 xen-boot pass
5 debian-install pass
6 debian-fixup pass
7 guest-start pass
8 guest-saverestore pass
9 guest-localmigrate fail
10 capture-logs(10) pass
-------------------------------------------------------------------------------
test-amd64-amd64-win:
1 xen-build-check(1) pass
2 host-install(2) pass
3 xen-install pass
4 xen-boot pass
5 windows-install pass
6 guest-saverestore pass
7 guest-localmigrate pass
8 guest-stop pass
9 capture-logs(9) pass
-------------------------------------------------------------------------------
test-amd64-amd64-xl:
1 xen-build-check(1) pass
2 host-install(2) pass
3 xen-install pass
4 xen-boot pass
5 debian-install pass
6 debian-fixup pass
7 guest-start pass
8 guest-saverestore pass
9 guest-localmigrate pass
10 guest-stop fail
11 capture-logs(11) pass
-------------------------------------------------------------------------------
test-amd64-i386-pair:
1 xen-build-check(1) pass
2 host-install/src_host(2) pass
3 host-install/dst_host(3) pass
4 xen-install/src_host pass
5 xen-install/dst_host pass
6 xen-boot/src_host pass
7 xen-boot/dst_host pass
8 debian-install/dst_host pass
9 debian-fixup/dst_host pass
10 guests-nbd-mirror pass
11 guest-start pass
12 guest-migrate/src_host/dst_host fail
13 capture-logs/src_host(13) pass
14 capture-logs/dst_host(14) pass
-------------------------------------------------------------------------------
test-amd64-i386-pv:
1 xen-build-check(1) pass
2 host-install(2) pass
3 xen-install pass
4 xen-boot pass
5 debian-install pass
6 debian-fixup pass
7 guest-start pass
8 guest-saverestore fail
9 capture-logs(9) pass
-------------------------------------------------------------------------------
test-amd64-i386-win:
1 xen-build-check(1) pass
2 host-install(2) pass
3 xen-install pass
4 xen-boot pass
5 windows-install fail
6 capture-logs(6) pass
-------------------------------------------------------------------------------
test-amd64-i386-xl:
1 xen-build-check(1) pass
2 host-install(2) pass
3 xen-install pass
4 xen-boot pass
5 debian-install pass
6 debian-fixup pass
7 guest-start pass
8 guest-saverestore pass
9 guest-localmigrate fail
10 capture-logs(10) pass
-------------------------------------------------------------------------------
test-amd64-xcpkern-i386-pair:
1 xen-build-check(1) pass
2 host-install/src_host(2) pass
3 host-install/dst_host(3) pass
4 xen-install/src_host pass
5 xen-install/dst_host pass
6 xen-boot/src_host pass
7 xen-boot/dst_host pass
8 debian-install/dst_host pass
9 debian-fixup/dst_host pass
10 guests-nbd-mirror pass
11 guest-start pass
12 guest-migrate/src_host/dst_host pass
13 guest-migrate/dst_host/src_host pass
14 capture-logs/src_host(14) pass
15 capture-logs/dst_host(15) pass
-------------------------------------------------------------------------------
test-amd64-xcpkern-i386-pv:
1 xen-build-check(1) pass
2 host-install(2) pass
3 xen-install pass
4 xen-boot pass
5 debian-install pass
6 debian-fixup pass
7 guest-start pass
8 guest-saverestore pass
9 guest-localmigrate pass
10 guest-stop pass
11 capture-logs(11) pass
-------------------------------------------------------------------------------
test-amd64-xcpkern-i386-win:
1 xen-build-check(1) pass
2 host-install(2) pass
3 xen-install pass
4 xen-boot pass
5 windows-install pass
6 guest-saverestore pass
7 guest-localmigrate pass
8 guest-stop pass
9 capture-logs(9) pass
-------------------------------------------------------------------------------
test-amd64-xcpkern-i386-xl:
1 xen-build-check(1) pass
2 host-install(2) pass
3 xen-install pass
4 xen-boot pass
5 debian-install pass
6 debian-fixup pass
7 guest-start pass
8 guest-saverestore pass
9 guest-localmigrate pass
10 guest-stop fail
11 capture-logs(11) pass
-------------------------------------------------------------------------------
test-i386-i386-pair:
1 xen-build-check(1) pass
2 host-install/src_host(2) pass
3 host-install/dst_host(3) pass
4 xen-install/src_host pass
5 xen-install/dst_host pass
6 xen-boot/src_host pass
7 xen-boot/dst_host pass
8 debian-install/dst_host pass
9 debian-fixup/dst_host pass
10 guests-nbd-mirror pass
11 guest-start pass
12 guest-migrate/src_host/dst_host fail
13 capture-logs/src_host(13) pass
14 capture-logs/dst_host(14) pass
-------------------------------------------------------------------------------
test-i386-i386-pv:
1 xen-build-check(1) pass
2 host-install(2) pass
3 xen-install pass
4 xen-boot pass
5 debian-install pass
6 debian-fixup pass
7 guest-start pass
8 guest-saverestore pass
9 guest-localmigrate fail
10 capture-logs(10) pass
-------------------------------------------------------------------------------
test-i386-i386-win:
1 xen-build-check(1) pass
2 host-install(2) pass
3 xen-install pass
4 xen-boot pass
5 windows-install fail
6 capture-logs(6) pass
-------------------------------------------------------------------------------
test-i386-i386-xl:
1 xen-build-check(1) pass
2 host-install(2) pass
3 xen-install pass
4 xen-boot pass
5 debian-install pass
6 debian-fixup pass
7 guest-start pass
8 guest-saverestore fail
9 capture-logs(9) pass
-------------------------------------------------------------------------------
test-i386-xcpkern-i386-pair:
1 xen-build-check(1) pass
2 host-install/src_host(2) pass
3 host-install/dst_host(3) pass
4 xen-install/src_host pass
5 xen-install/dst_host pass
6 xen-boot/src_host pass
7 xen-boot/dst_host pass
8 debian-install/dst_host pass
9 debian-fixup/dst_host pass
10 guests-nbd-mirror pass
11 guest-start pass
12 guest-migrate/src_host/dst_host fail
13 capture-logs/src_host(13) pass
14 capture-logs/dst_host(14) pass
-------------------------------------------------------------------------------
test-i386-xcpkern-i386-pv:
1 xen-build-check(1) pass
2 host-install(2) pass
3 xen-install pass
4 xen-boot pass
5 debian-install pass
6 debian-fixup pass
7 guest-start pass
8 guest-saverestore pass
9 guest-localmigrate pass
10 guest-stop pass
11 capture-logs(11) pass
-------------------------------------------------------------------------------
test-i386-xcpkern-i386-win:
1 xen-build-check(1) pass
2 host-install(2) pass
3 xen-install pass
4 xen-boot pass
5 windows-install pass
6 guest-saverestore pass
7 guest-localmigrate pass
8 guest-stop pass
9 capture-logs(9) pass
-------------------------------------------------------------------------------
test-i386-xcpkern-i386-xl:
1 xen-build-check(1) pass
2 host-install(2) pass
3 xen-install pass
4 xen-boot pass
5 debian-install pass
6 debian-fixup pass
7 guest-start pass
8 guest-saverestore pass
9 guest-localmigrate pass
10 guest-stop fail
11 capture-logs(11) pass
------------------------------------------------------------
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.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Keir Fraser
2010-Aug-19 07:42 UTC
Re: [Xen-devel] [xen-4.0-testing test] 2032: regressions - FAIL
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? K. On 19/08/2010 06:19, "Ian Jackson" <Ian.Jackson@eu.citrix.com> wrote:> flight 2032 xen-4.0-testing real > http://www.chiark.greenend.org.uk/~xensrcts/logs/2032/ > > Regressions :-( > > tests which did not succeed: > test-amd64-amd64-pair 12 guest-migrate/src_host/dst_host fail never > pass > test-amd64-amd64-pv 9 guest-localmigrate fail REGR. vs. > 1993 > test-amd64-amd64-xl 10 guest-stop fail never > pass > test-amd64-i386-pair 12 guest-migrate/src_host/dst_host fail REGR. vs. > 1993 > test-amd64-i386-pv 8 guest-saverestore fail REGR. vs. > 1993 > test-amd64-i386-win 5 windows-install fail REGR. vs. > 1993 > test-amd64-i386-xl 9 guest-localmigrate fail REGR. vs. > 1993 > test-amd64-xcpkern-i386-xl 10 guest-stop fail never > pass > test-i386-i386-pair 12 guest-migrate/src_host/dst_host fail never > pass > test-i386-i386-pv 9 guest-localmigrate fail REGR. vs. > 1993 > test-i386-i386-win 5 windows-install fail REGR. vs. > 1993 > test-i386-i386-xl 8 guest-saverestore fail REGR. vs. > 1993 > test-i386-xcpkern-i386-pair 12 guest-migrate/src_host/dst_host fail like > 1993 > test-i386-xcpkern-i386-xl 10 guest-stop fail never > pass > > version targeted for testing: > xen 5e8df2d2ef6f > baseline version: > xen 8e8dd38374e9 > > jobs: > build-amd64 pass > build-amd64-oldkern pass > build-i386 pass > build-i386-oldkern pass > build-i386-xcpkern pass > test-amd64-amd64-pair fail > test-amd64-amd64-pv fail > test-amd64-amd64-win pass > test-amd64-amd64-xl fail > test-amd64-i386-pair fail > test-amd64-i386-pv fail > test-amd64-i386-win fail > test-amd64-i386-xl fail > test-amd64-xcpkern-i386-pair pass > test-amd64-xcpkern-i386-pv pass > test-amd64-xcpkern-i386-win pass > test-amd64-xcpkern-i386-xl fail > test-i386-i386-pair fail > test-i386-i386-pv fail > test-i386-i386-win fail > test-i386-i386-xl fail > test-i386-xcpkern-i386-pair fail > test-i386-xcpkern-i386-pv pass > test-i386-xcpkern-i386-win pass > test-i386-xcpkern-i386-xl fail > >------------------------------------------------------------------------------> -> build-amd64: > 1 host-install(1) pass > 2 host-build-prep pass > 3 xen-build pass > linux e73f4955a821f850f5b8 > qemu 0a940d892e90c820567c > xen 21321:5e8df2d2ef6f >------------------------------------------------------------------------------> -> build-amd64-oldkern: > 1 xen-build pass > linux 1025:042c8cd71081 > qemu 0a940d892e90c820567c > xen 21321:5e8df2d2ef6f >------------------------------------------------------------------------------> -> build-i386: > 1 host-install(1) pass > 2 host-build-prep pass > 3 xen-build pass > linux e73f4955a821f850f5b8 > qemu 0a940d892e90c820567c > xen 21321:5e8df2d2ef6f >------------------------------------------------------------------------------> -> build-i386-oldkern: > 1 xen-build pass > linux 1025:042c8cd71081 > qemu 0a940d892e90c820567c > xen 21321:5e8df2d2ef6f >------------------------------------------------------------------------------> -> build-i386-xcpkern: > 1 kernel-build pass > linux 110879:32fc6955a6a5 > pq_linux 154:61499f9e9a87 >------------------------------------------------------------------------------> -> test-amd64-amd64-pair: > 1 xen-build-check(1) pass > 2 host-install/src_host(2) pass > 3 host-install/dst_host(3) pass > 4 xen-install/src_host pass > 5 xen-install/dst_host pass > 6 xen-boot/src_host pass > 7 xen-boot/dst_host pass > 8 debian-install/dst_host pass > 9 debian-fixup/dst_host pass > 10 guests-nbd-mirror pass > 11 guest-start pass > 12 guest-migrate/src_host/dst_host fail > 13 capture-logs/src_host(13) pass > 14 capture-logs/dst_host(14) pass >------------------------------------------------------------------------------> -> test-amd64-amd64-pv: > 1 xen-build-check(1) pass > 2 host-install(2) pass > 3 xen-install pass > 4 xen-boot pass > 5 debian-install pass > 6 debian-fixup pass > 7 guest-start pass > 8 guest-saverestore pass > 9 guest-localmigrate fail > 10 capture-logs(10) pass >------------------------------------------------------------------------------> -> test-amd64-amd64-win: > 1 xen-build-check(1) pass > 2 host-install(2) pass > 3 xen-install pass > 4 xen-boot pass > 5 windows-install pass > 6 guest-saverestore pass > 7 guest-localmigrate pass > 8 guest-stop pass > 9 capture-logs(9) pass >------------------------------------------------------------------------------> -> test-amd64-amd64-xl: > 1 xen-build-check(1) pass > 2 host-install(2) pass > 3 xen-install pass > 4 xen-boot pass > 5 debian-install pass > 6 debian-fixup pass > 7 guest-start pass > 8 guest-saverestore pass > 9 guest-localmigrate pass > 10 guest-stop fail > 11 capture-logs(11) pass >------------------------------------------------------------------------------> -> test-amd64-i386-pair: > 1 xen-build-check(1) pass > 2 host-install/src_host(2) pass > 3 host-install/dst_host(3) pass > 4 xen-install/src_host pass > 5 xen-install/dst_host pass > 6 xen-boot/src_host pass > 7 xen-boot/dst_host pass > 8 debian-install/dst_host pass > 9 debian-fixup/dst_host pass > 10 guests-nbd-mirror pass > 11 guest-start pass > 12 guest-migrate/src_host/dst_host fail > 13 capture-logs/src_host(13) pass > 14 capture-logs/dst_host(14) pass >------------------------------------------------------------------------------> -> test-amd64-i386-pv: > 1 xen-build-check(1) pass > 2 host-install(2) pass > 3 xen-install pass > 4 xen-boot pass > 5 debian-install pass > 6 debian-fixup pass > 7 guest-start pass > 8 guest-saverestore fail > 9 capture-logs(9) pass >------------------------------------------------------------------------------> -> test-amd64-i386-win: > 1 xen-build-check(1) pass > 2 host-install(2) pass > 3 xen-install pass > 4 xen-boot pass > 5 windows-install fail > 6 capture-logs(6) pass >------------------------------------------------------------------------------> -> test-amd64-i386-xl: > 1 xen-build-check(1) pass > 2 host-install(2) pass > 3 xen-install pass > 4 xen-boot pass > 5 debian-install pass > 6 debian-fixup pass > 7 guest-start pass > 8 guest-saverestore pass > 9 guest-localmigrate fail > 10 capture-logs(10) pass >------------------------------------------------------------------------------> -> test-amd64-xcpkern-i386-pair: > 1 xen-build-check(1) pass > 2 host-install/src_host(2) pass > 3 host-install/dst_host(3) pass > 4 xen-install/src_host pass > 5 xen-install/dst_host pass > 6 xen-boot/src_host pass > 7 xen-boot/dst_host pass > 8 debian-install/dst_host pass > 9 debian-fixup/dst_host pass > 10 guests-nbd-mirror pass > 11 guest-start pass > 12 guest-migrate/src_host/dst_host pass > 13 guest-migrate/dst_host/src_host pass > 14 capture-logs/src_host(14) pass > 15 capture-logs/dst_host(15) pass >------------------------------------------------------------------------------> -> test-amd64-xcpkern-i386-pv: > 1 xen-build-check(1) pass > 2 host-install(2) pass > 3 xen-install pass > 4 xen-boot pass > 5 debian-install pass > 6 debian-fixup pass > 7 guest-start pass > 8 guest-saverestore pass > 9 guest-localmigrate pass > 10 guest-stop pass > 11 capture-logs(11) pass >------------------------------------------------------------------------------> -> test-amd64-xcpkern-i386-win: > 1 xen-build-check(1) pass > 2 host-install(2) pass > 3 xen-install pass > 4 xen-boot pass > 5 windows-install pass > 6 guest-saverestore pass > 7 guest-localmigrate pass > 8 guest-stop pass > 9 capture-logs(9) pass >------------------------------------------------------------------------------> -> test-amd64-xcpkern-i386-xl: > 1 xen-build-check(1) pass > 2 host-install(2) pass > 3 xen-install pass > 4 xen-boot pass > 5 debian-install pass > 6 debian-fixup pass > 7 guest-start pass > 8 guest-saverestore pass > 9 guest-localmigrate pass > 10 guest-stop fail > 11 capture-logs(11) pass >------------------------------------------------------------------------------> -> test-i386-i386-pair: > 1 xen-build-check(1) pass > 2 host-install/src_host(2) pass > 3 host-install/dst_host(3) pass > 4 xen-install/src_host pass > 5 xen-install/dst_host pass > 6 xen-boot/src_host pass > 7 xen-boot/dst_host pass > 8 debian-install/dst_host pass > 9 debian-fixup/dst_host pass > 10 guests-nbd-mirror pass > 11 guest-start pass > 12 guest-migrate/src_host/dst_host fail > 13 capture-logs/src_host(13) pass > 14 capture-logs/dst_host(14) pass >------------------------------------------------------------------------------> -> test-i386-i386-pv: > 1 xen-build-check(1) pass > 2 host-install(2) pass > 3 xen-install pass > 4 xen-boot pass > 5 debian-install pass > 6 debian-fixup pass > 7 guest-start pass > 8 guest-saverestore pass > 9 guest-localmigrate fail > 10 capture-logs(10) pass >------------------------------------------------------------------------------> -> test-i386-i386-win: > 1 xen-build-check(1) pass > 2 host-install(2) pass > 3 xen-install pass > 4 xen-boot pass > 5 windows-install fail > 6 capture-logs(6) pass >------------------------------------------------------------------------------> -> test-i386-i386-xl: > 1 xen-build-check(1) pass > 2 host-install(2) pass > 3 xen-install pass > 4 xen-boot pass > 5 debian-install pass > 6 debian-fixup pass > 7 guest-start pass > 8 guest-saverestore fail > 9 capture-logs(9) pass >------------------------------------------------------------------------------> -> test-i386-xcpkern-i386-pair: > 1 xen-build-check(1) pass > 2 host-install/src_host(2) pass > 3 host-install/dst_host(3) pass > 4 xen-install/src_host pass > 5 xen-install/dst_host pass > 6 xen-boot/src_host pass > 7 xen-boot/dst_host pass > 8 debian-install/dst_host pass > 9 debian-fixup/dst_host pass > 10 guests-nbd-mirror pass > 11 guest-start pass > 12 guest-migrate/src_host/dst_host fail > 13 capture-logs/src_host(13) pass > 14 capture-logs/dst_host(14) pass >------------------------------------------------------------------------------> -> test-i386-xcpkern-i386-pv: > 1 xen-build-check(1) pass > 2 host-install(2) pass > 3 xen-install pass > 4 xen-boot pass > 5 debian-install pass > 6 debian-fixup pass > 7 guest-start pass > 8 guest-saverestore pass > 9 guest-localmigrate pass > 10 guest-stop pass > 11 capture-logs(11) pass >------------------------------------------------------------------------------> -> test-i386-xcpkern-i386-win: > 1 xen-build-check(1) pass > 2 host-install(2) pass > 3 xen-install pass > 4 xen-boot pass > 5 windows-install pass > 6 guest-saverestore pass > 7 guest-localmigrate pass > 8 guest-stop pass > 9 capture-logs(9) pass >------------------------------------------------------------------------------> -> test-i386-xcpkern-i386-xl: > 1 xen-build-check(1) pass > 2 host-install(2) pass > 3 xen-install pass > 4 xen-boot pass > 5 debian-install pass > 6 debian-fixup pass > 7 guest-start pass > 8 guest-saverestore pass > 9 guest-localmigrate pass > 10 guest-stop fail > 11 capture-logs(11) pass > > ------------------------------------------------------------ > 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. > > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Campbell
2010-Aug-19 08:00 UTC
Re: [Xen-devel] [xen-4.0-testing test] 2032: regressions - FAIL
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@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Jackson
2010-Aug-19 10:08 UTC
Re: [Xen-devel] [xen-4.0-testing test] 2032: regressions - FAIL
Ian Campbell writes ("Re: [Xen-devel] [xen-4.0-testing test] 2032:
regressions - FAIL"):> IanJ: Are the guest consoles logged anywhere by your test suite?
I try to run "xl console" (or "xm console") at the end - you
can see
the output if any in the transcript of ts-logs-capture, but that''s not
as good as what you''re suggesting.
> -#XENCONSOLED_TRACE=[none|guest|hv|all]
> +XENCONSOLED_TRACE=guest
I didn''t know this was possible. Perhaps it should be the default ?
Certainly it should be for my testing, which I will sort out.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Ian Campbell
2010-Aug-19 10:35 UTC
Re: [Xen-devel] [xen-4.0-testing test] 2032: regressions - FAIL
On Thu, 2010-08-19 at 11:08 +0100, Ian Jackson wrote:> > -#XENCONSOLED_TRACE=[none|guest|hv|all] > > +XENCONSOLED_TRACE=guest > > I didn''t know this was possible. Perhaps it should be the default ?I think we''d need to arrange for rotation etc to take place before we could turn it on by default, which wouldn''t be a simple logrotate config snippet due to the somewhat unpredictable filenames. I''m not sure if xenconsoled handles reopening logs either (I didn''t check though). I think it''s best left as a developer/debug option which can be turned on when necessary for the time being.> Certainly it should be for my testing, which I will sort out.Thanks, Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Jackson
2010-Aug-19 10:48 UTC
Re: [Xen-devel] [xen-4.0-testing test] 2032: regressions - FAIL
Ian Campbell writes ("Re: [Xen-devel] [xen-4.0-testing test] 2032:
regressions - FAIL"):> I think we should try e6b9b2cbca5093e8e38d3e314e2f6415ad951c60. This is
> the commit before e73f4955a821f850f5b88c32d12a81714523a95f which was
> fingered as bad by the xen-unstable bisect yesterday.
Shall I try that with current xen-4.0-testing tip, or with the
changeset I tried last night (pre the netif header backport) ?
It''s likely to take all day so it would be nice to pick the right
combination.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Keir Fraser
2010-Aug-19 10:56 UTC
Re: [Xen-devel] [xen-4.0-testing test] 2032: regressions - FAIL
On 19/08/2010 11:48, "Ian Jackson" <Ian.Jackson@eu.citrix.com> wrote:> Ian Campbell writes ("Re: [Xen-devel] [xen-4.0-testing test] 2032: regressions > - FAIL"): >> I think we should try e6b9b2cbca5093e8e38d3e314e2f6415ad951c60. This is >> the commit before e73f4955a821f850f5b88c32d12a81714523a95f which was >> fingered as bad by the xen-unstable bisect yesterday. > > Shall I try that with current xen-4.0-testing tip, or with the > changeset I tried last night (pre the netif header backport) ? > > It''s likely to take all day so it would be nice to pick the right > combination.Does your testing use blktap vhds, or something else (e.g., LVM-backed phy)? If you don''t use blktap then it''s utterly immaterial whether you test tip or two chnagesets back (skipping the ring.h changes), as blktap is the only subsystem in the Xen tree to use the ring.h header. Linux kernel has its own copy of that ring.h file and will be unaffected either way. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Keir Fraser
2010-Aug-19 11:03 UTC
Re: [Xen-devel] [xen-4.0-testing test] 2032: regressions - FAIL
On 19/08/2010 11:56, "Keir Fraser" <keir.fraser@eu.citrix.com> wrote:>> Shall I try that with current xen-4.0-testing tip, or with the >> changeset I tried last night (pre the netif header backport) ? >> >> It''s likely to take all day so it would be nice to pick the right >> combination. > > Does your testing use blktap vhds, or something else (e.g., LVM-backed phy)? > If you don''t use blktap then it''s utterly immaterial whether you test tip or > two chnagesets back (skipping the ring.h changes), as blktap is the only > subsystem in the Xen tree to use the ring.h header. Linux kernel has its own > copy of that ring.h file and will be unaffected either way.Ah, looking at the logs I see everything is phy: or file: -- no tap:. Therefore you should test tip of xen-4.0-testing, as the ring.h changes are not to blame for any regression in testing. -- Keir _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Campbell
2010-Aug-19 11:04 UTC
Re: [Xen-devel] [xen-4.0-testing test] 2032: regressions - FAIL
On Thu, 2010-08-19 at 12:03 +0100, Keir Fraser wrote:> On 19/08/2010 11:56, "Keir Fraser" <keir.fraser@eu.citrix.com> wrote: > > >> Shall I try that with current xen-4.0-testing tip, or with the > >> changeset I tried last night (pre the netif header backport) ? > >> > >> It''s likely to take all day so it would be nice to pick the right > >> combination. > > > > Does your testing use blktap vhds, or something else (e.g., LVM-backed phy)? > > If you don''t use blktap then it''s utterly immaterial whether you test tip or > > two chnagesets back (skipping the ring.h changes), as blktap is the only > > subsystem in the Xen tree to use the ring.h header. Linux kernel has its own > > copy of that ring.h file and will be unaffected either way. > > Ah, looking at the logs I see everything is phy: or file: -- no tap:. > Therefore you should test tip of xen-4.0-testing, as the ring.h changes are > not to blame for any regression in testing.AIUI file: -> tap: for libxl (and -> phy:, via /dev/loop for xend). Whether that''s implicated in these failures I don''t know. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Jackson
2010-Aug-19 11:09 UTC
Re: [Xen-devel] [xen-4.0-testing test] 2032: regressions - FAIL
Keir Fraser writes ("Re: [Xen-devel] [xen-4.0-testing test] 2032:
regressions - FAIL"):> Does your testing use blktap vhds, or something else (e.g., LVM-backed
phy)?
It uses both "file:" and "phy:" and the former is AIUI
blktap.
"file:" is used for the cdrom only, and only during HVM installs, so
the corresponding PV disk won''t be heavily stressed. If I''m
not
mistaken with "file:" qemu-dm opens the file itself directly.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Keir Fraser
2010-Aug-19 11:24 UTC
Re: [Xen-devel] [xen-4.0-testing test] 2032: regressions - FAIL
On 19/08/2010 12:09, "Ian Jackson" <Ian.Jackson@eu.citrix.com> wrote:> Keir Fraser writes ("Re: [Xen-devel] [xen-4.0-testing test] 2032: regressions > - FAIL"): >> Does your testing use blktap vhds, or something else (e.g., LVM-backed phy)? > > It uses both "file:" and "phy:" and the former is AIUI blktap. > "file:" is used for the cdrom only, and only during HVM installs, so > the corresponding PV disk won''t be heavily stressed. If I''m not > mistaken with "file:" qemu-dm opens the file itself directly.Yes, if you''re only using file: for HVM, and then only for the install stage, then I don''t think blktap is involved. -- Keir> Ian._______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Pasi Kärkkäinen
2010-Aug-19 11:31 UTC
Re: [Xen-devel] [xen-4.0-testing test] 2032: regressions - FAIL
On Thu, Aug 19, 2010 at 12:03:06PM +0100, Keir Fraser wrote:> On 19/08/2010 11:56, "Keir Fraser" <keir.fraser@eu.citrix.com> wrote: > > >> Shall I try that with current xen-4.0-testing tip, or with the > >> changeset I tried last night (pre the netif header backport) ? > >> > >> It''s likely to take all day so it would be nice to pick the right > >> combination. > > > > Does your testing use blktap vhds, or something else (e.g., LVM-backed phy)? > > If you don''t use blktap then it''s utterly immaterial whether you test tip or > > two chnagesets back (skipping the ring.h changes), as blktap is the only > > subsystem in the Xen tree to use the ring.h header. Linux kernel has its own > > copy of that ring.h file and will be unaffected either way. > > Ah, looking at the logs I see everything is phy: or file: -- no tap:. > Therefore you should test tip of xen-4.0-testing, as the ring.h changes are > not to blame for any regression in testing. >Would be good to add automatic blktap2 testing aswell.. -- Pasi _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Jackson
2010-Aug-19 14:57 UTC
Re: [Xen-devel] [xen-4.0-testing test] 2032: regressions - FAIL
Pasi Kärkkäinen writes ("Re: [Xen-devel] [xen-4.0-testing test] 2032:
regressions - FAIL"):> Would be good to add automatic blktap2 testing aswell..
I think we should make xl use blktap2 automatically where it''s
available. I don''t want to further entrench the "tap2:"
syntax.
Doing some more complicated testing with various tapdisk based VMs
would indeed be a good idea.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Ian Jackson
2010-Aug-19 18:07 UTC
Re: [Xen-devel] [xen-4.0-testing test] 2032: regressions - FAIL
Ian Campbell writes ("Re: [Xen-devel] [xen-4.0-testing test] 2032:
regressions - FAIL"):> I think we should try e6b9b2cbca5093e8e38d3e314e2f6415ad951c60. This is
> the commit before e73f4955a821f850f5b88c32d12a81714523a95f which was
> fingered as bad by the xen-unstable bisect yesterday.
*sigh* I started this this morning and just went to look how it was
getting on. It had fallen over due to lack of disk space on the
archive volume where test output is stored. This is the first time
this has happened. I''ve made some space and started it again but it
won''t be with us for a while now ...
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Ian Campbell
2010-Aug-20 07:58 UTC
Re: [Xen-devel] [xen-4.0-testing test] 2032: regressions - FAIL
On Thu, 2010-08-19 at 09:00 +0100, Ian Campbell wrote:> > 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".2.6.32.19 has a known issue relating to the new stack guard page which has prompted a quick 2.6.32.20-rc1 with only a couple of patches. The issue is supposedly PAE and/or HIGHPTE specific but I wonder if it also has an impact under Xen in other configurations? The save/restore issue we are seeing seems to relate to an inability to lock memory for a hypercall and d7824370e26325c881b665350ce64fb0a4fde24a (the second fix in 2.6.32.20-rc) specifically mentions fixing up a user-visible mlock change relating to mlock. I''ll try and confirm that, if I can ever manage to get a consistent repro. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ian Campbell
2010-Aug-20 08:57 UTC
Re: [Xen-devel] [xen-4.0-testing test] 2032: regressions - FAIL
On Fri, 2010-08-20 at 08:58 +0100, Ian Campbell wrote:> On Thu, 2010-08-19 at 09:00 +0100, Ian Campbell wrote: > > > > 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". > > 2.6.32.19 has a known issue relating to the new stack guard page which > has prompted a quick 2.6.32.20-rc1 with only a couple of patches. > > The issue is supposedly PAE and/or HIGHPTE specific but I wonder if it > also has an impact under Xen in other configurations? > > The save/restore issue we are seeing seems to relate to an inability to > lock memory for a hypercall and d7824370e26325c881b665350ce64fb0a4fde24a > (the second fix in 2.6.32.20-rc) specifically mentions fixing up a > user-visible mlock change relating to mlock. > > I''ll try and confirm that, if I can ever manage to get a consistent > repro.Reverting ab832422673d1774c4ce3941f2ac87743d73bded mm: fix missing page table unmap for stack guard page failure case 7e281afe24330aeea86113ac241eabdac8ba2311 mm: keep a guard page below a grow-down stack segment resolves the save/restore issue for me. However cherry-picking the 2.6.32.20 fixes 11ac552477e32835cb6970bf0a70c210807f5673 mm: fix page table unmap for stack guard page properly d7824370e26325c881b665350ce64fb0a4fde24a mm: fix up some user-visible effects of the stack guard page does not do the trick. Ian. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel