|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [xen-4.5-testing test] 52649: regressions - FAIL
flight 52649 xen-4.5-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/52649/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-xl-credit2 6 xen-boot fail REGR. vs. 50408 test-amd64-amd64-xl-credit2 16 guest-localmigrate.2 fail REGR. vs. 50408 test-amd64-i386-qemut-rhel6hvm-amd 9 redhat-install fail REGR. vs. 50408 test-amd64-i386-xl-qemut-debianhvm-amd64 15 guest-localmigrate/x10 fail REGR. vs. 50408 test-amd64-amd64-xl-qemuu-debianhvm-amd64 15 guest-localmigrate/x10 fail REGR. vs. 50408 test-amd64-i386-xl-qemuu-ovmf-amd64 15 guest-localmigrate/x10 fail REGR. vs. 50408 test-amd64-i386-rhel6hvm-amd 9 redhat-install fail REGR. vs. 50408 test-amd64-i386-qemut-rhel6hvm-intel 12 guest-start/redhat.repeat fail REGR. vs. 50408 test-amd64-amd64-xl-win7-amd64 15 guest-localmigrate/x10 fail REGR. vs. 50408 test-amd64-amd64-xl-qemut-debianhvm-amd64 18 guest-start/debianhvm.repeat fail REGR. vs. 50408 Regressions which are regarded as allowable (not blocking): test-amd64-amd64-xl-qemuu-ovmf-amd64 12 guest-localmigrate fail REGR. vs. 50408 test-amd64-amd64-xl-sedf 20 guest-start/debian.repeat fail REGR. vs. 50408 test-amd64-amd64-libvirt 15 guest-start/debian.repeat fail REGR. vs. 50408 test-amd64-i386-freebsd10-amd64 13 guest-localmigrate fail like 50373 test-amd64-amd64-xl-qemuu-win7-amd64 15 guest-localmigrate/x10 fail like 50393 test-amd64-i386-freebsd10-i386 13 guest-localmigrate fail like 50408 Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-pvh-intel 11 guest-start fail never pass test-amd64-amd64-xl-pvh-amd 11 guest-start fail never pass test-armhf-armhf-xl-arndale 12 migrate-support-check fail never pass test-amd64-i386-libvirt 12 migrate-support-check fail never pass test-amd64-i386-xl-qemut-win7-amd64 16 guest-stop fail never pass test-armhf-armhf-xl-multivcpu 12 migrate-support-check fail never pass test-armhf-armhf-xl-sedf-pin 12 migrate-support-check fail never pass test-armhf-armhf-xl 12 migrate-support-check fail never pass test-amd64-amd64-libvirt 12 migrate-support-check fail never pass test-armhf-armhf-libvirt 12 migrate-support-check fail never pass test-amd64-i386-xl-win7-amd64 16 guest-stop fail never pass test-armhf-armhf-xl-cubietruck 12 migrate-support-check fail never pass test-armhf-armhf-xl-sedf 12 migrate-support-check fail never pass test-amd64-amd64-xl-qemut-win7-amd64 16 guest-stop fail never pass test-amd64-amd64-xl-qemuu-winxpsp3 16 guest-stop fail never pass test-amd64-i386-xl-qemut-winxpsp3-vcpus1 16 guest-stop fail never pass test-amd64-i386-xl-qemut-winxpsp3 16 guest-stop fail never pass test-amd64-i386-xl-winxpsp3 16 guest-stop fail never pass test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop fail never pass test-amd64-i386-xl-winxpsp3-vcpus1 16 guest-stop fail never pass test-amd64-i386-xl-qemuu-winxpsp3 16 guest-stop fail never pass test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 16 guest-stop fail never pass test-amd64-amd64-xl-qemut-winxpsp3 16 guest-stop fail never pass test-amd64-amd64-xl-winxpsp3 16 guest-stop fail never pass version targeted for testing: xen d41906197d9a89355f43d4359d795b1d0257a53a baseline version: xen 0b754fb3ed6b7b6d0f2e1f7c1877d3c0a7da2168 ------------------------------------------------------------ People who touched revisions under test: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Ian Campbell <ian.campbell@xxxxxxxxxx> Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> JeHyeon Yeon <tom.yeon@xxxxxxxxxxxxx> Kevin Tian <kevin.tian@xxxxxxxxx> Liang Li <liang.z.li@xxxxxxxxx> Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> Tim Deegan <tim@xxxxxxx> Yang Zhang <yang.z.zhang@xxxxxxxxx> ------------------------------------------------------------ jobs: build-amd64 pass build-armhf pass build-i386 pass build-amd64-libvirt pass build-armhf-libvirt pass build-i386-libvirt pass build-amd64-pvops pass build-armhf-pvops pass build-i386-pvops pass build-amd64-rumpuserxen pass build-i386-rumpuserxen pass test-amd64-amd64-xl pass test-armhf-armhf-xl pass test-amd64-i386-xl pass test-amd64-amd64-xl-pvh-amd fail test-amd64-i386-rhel6hvm-amd fail test-amd64-i386-qemut-rhel6hvm-amd fail test-amd64-i386-qemuu-rhel6hvm-amd pass test-amd64-amd64-xl-qemut-debianhvm-amd64 fail test-amd64-i386-xl-qemut-debianhvm-amd64 fail test-amd64-amd64-xl-qemuu-debianhvm-amd64 fail test-amd64-i386-xl-qemuu-debianhvm-amd64 pass test-amd64-i386-freebsd10-amd64 fail test-amd64-amd64-xl-qemuu-ovmf-amd64 fail test-amd64-i386-xl-qemuu-ovmf-amd64 fail test-amd64-amd64-rumpuserxen-amd64 pass test-amd64-amd64-xl-qemut-win7-amd64 fail test-amd64-i386-xl-qemut-win7-amd64 fail test-amd64-amd64-xl-qemuu-win7-amd64 fail test-amd64-i386-xl-qemuu-win7-amd64 fail test-amd64-amd64-xl-win7-amd64 fail test-amd64-i386-xl-win7-amd64 fail test-armhf-armhf-xl-arndale pass test-amd64-amd64-xl-credit2 fail test-armhf-armhf-xl-credit2 fail test-armhf-armhf-xl-cubietruck pass test-amd64-i386-freebsd10-i386 fail test-amd64-i386-rumpuserxen-i386 pass test-amd64-amd64-xl-pvh-intel fail test-amd64-i386-rhel6hvm-intel pass test-amd64-i386-qemut-rhel6hvm-intel fail test-amd64-i386-qemuu-rhel6hvm-intel pass test-amd64-amd64-libvirt fail test-armhf-armhf-libvirt pass test-amd64-i386-libvirt pass test-amd64-amd64-xl-multivcpu pass test-armhf-armhf-xl-multivcpu pass test-amd64-amd64-pair pass test-amd64-i386-pair pass test-amd64-amd64-xl-sedf-pin pass test-armhf-armhf-xl-sedf-pin pass test-amd64-amd64-xl-sedf fail test-armhf-armhf-xl-sedf pass test-amd64-i386-xl-qemut-winxpsp3-vcpus1 fail test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 fail test-amd64-i386-xl-winxpsp3-vcpus1 fail test-amd64-amd64-xl-qemut-winxpsp3 fail test-amd64-i386-xl-qemut-winxpsp3 fail test-amd64-amd64-xl-qemuu-winxpsp3 fail test-amd64-i386-xl-qemuu-winxpsp3 fail test-amd64-amd64-xl-winxpsp3 fail test-amd64-i386-xl-winxpsp3 fail ------------------------------------------------------------ sg-report-flight on osstest.test-lab.xenproject.org logs: /home/osstest/pub/logs images: /home/osstest/pub/images Logs, config files, etc. are available at http://logs.test-lab.xenproject.org/osstest/logs Test harness code can be found at http://xenbits.xen.org/gitweb?p=osstest.git;a=summary Not pushing. ------------------------------------------------------------ commit d41906197d9a89355f43d4359d795b1d0257a53a Author: Ian Jackson <ian.jackson@xxxxxxxxxxxxx> Date: Tue Apr 21 14:47:38 2015 +0100 Config.mk: Fix QEMU_TAG and QEMU_TRADITIONAL_REVISION handling In 2417e243 "QEMU_TAG update" my tag update script mangled the machinery which sets QEMU_TRADITIONAL_REVISION, by replacing the first assignment to QEMU_TRADITIONAL_REVISION it found rather than the one which ought to have been replaced. The result was that from that commit on, QEMU_TAG was no longer honoured although QEMU_TRADITIONAL_REVISION still was. Fix this by restoring the transfer from QEMU_TAG. This fix is analogous to 5d4c0952 "Config.mk: Fix (and, effectively, update) QEMU_TAG" from xen.git#staging, but in 4.5 there has not been a subsequent attempt to update the qemu revision, so both settings of QEMU_TRADITIONAL_REVISION are the same, and restoring the proper behaviour will not have the side effect of making a previous qemu tag update effective. Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> CC: Wei Liu <wei.liu2@xxxxxxxxxx> CC: Ian Campbell <ian.campbell@xxxxxxxxxx> CC: George Dunlap <george.dunlap@xxxxxxxxxxxxx> CC: Jan Beulich <jbeulich@xxxxxxxx> Reported-by: Jan Beulich <jbeulich@xxxxxxxx> commit 56fe488893759c7a134c4a69a63840095ac3552d Author: Liang Li <liang.z.li@xxxxxxxxx> Date: Tue Apr 21 09:16:06 2015 +0200 x86/hvm: fix the unknown nested vmexit reason 80000021 bug This bug will be trigged when NMI happen in the L2 guest. The current code handles the NMI incorrectly. According to Intel SDM 31.7.1.2 (Resuming Guest Software after Handling an Exception), If bit 31 of the IDT-vectoring information fields is set, and the virtual NMIs VM-execution control is 1, while bits 10:8 in the IDT-vectoring information field is 2, bit 3 in the interruptibility-state field should be cleared to avoid the next VM entry fail. Signed-off-by: Liang Li <liang.z.li@xxxxxxxxx> Acked-by: Kevin Tian <kevin.tian@xxxxxxxxx> Acked-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: f7708796db463410a97b5fa3dd5902f6e8a1d102 master date: 2015-04-10 11:35:46 -0400 commit 4a69292bc4b70e9a664031349ec611fb34beb1ed Author: Tim Deegan <tim@xxxxxxx> Date: Tue Apr 21 09:15:07 2015 +0200 x86_emulate: split the {reg,mem} union in struct operand In the hopes of making any future errors along the lines of XSA-123 into clean crashes instead of memory corruption bugs. Signed-off-by: Tim Deegan <tim@xxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: dd766684e7c97641bbaf16ee2b0e9add388199b7 master date: 2015-03-27 16:13:07 +0100 commit 4a521010b143cf10e99891bca9869307ed7428b7 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Apr 21 09:14:34 2015 +0200 VT-d: improve fault info logging I got repeatedly annoyed by there not getting anything logged by default on VT-d faults (and hence having to tell people to add extra command line options), and hence I think it is time to redo this code: Log basic fault information at guest-warning level (rate limited by default), and show the page walk in verbose rather than only in debug mode. Break up multi-line message so that each gets a proper log level attached, at once splitting out the common part. Also don't log "unknown" faults as interrupt-remapping ones. As a minor cleanup fix the type of the involved "fault_type" variables. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Acked-by: Yang Zhang <yang.z.zhang@xxxxxxxxx> master commit: f0250f4b4818f5f4230995407ea2501de3485934 master date: 2015-03-27 15:23:25 +0100 commit 5a7c04221c47c3196326e669f55beb4524d0de56 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Apr 21 09:13:51 2015 +0200 x86/MSI: fix error handling __setup_msi_irq() needs to undo what it did before calling write_msi_msg() in case that returned an error. map_domain_pirq() needs to get rid of the MSI descriptor it (implicitly) allocated. The case of a setup_msi_irq() failure on a non-initial multi-vector-MSI interrupt needs special handling: While the initial IRQ will get freed by the caller (who also passed it to us), we need to undo the effect setup_msi_irq() had on it. (As a benefit from the added call to msi_free_irq() we no longer need to explicitly call destroy_irq() on the non-initial slots.) Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: 29c1b7886c36d4e6aa03a779b2251b829d9689c3 master date: 2015-03-26 11:19:57 +0100 commit 51d8325b256ed8930a9d2700c5bbf73d0f3c3e8d Author: JeHyeon Yeon <tom.yeon@xxxxxxxxxxxxx> Date: Tue Apr 21 09:13:14 2015 +0200 LZ4 : fix the data abort issue If the part of the compression data are corrupted, or the compression data is totally fake, the memory access over the limit is possible. This is the log from my system usning lz4 decompression. [6502]data abort, halting [6503]r0 0x00000000 r1 0x00000000 r2 0xdcea0ffc r3 0xdcea0ffc [6509]r4 0xb9ab0bfd r5 0xdcea0ffc r6 0xdcea0ff8 r7 0xdce80000 [6515]r8 0x00000000 r9 0x00000000 r10 0x00000000 r11 0xb9a98000 [6522]r12 0xdcea1000 usp 0x00000000 ulr 0x00000000 pc 0x820149bc [6528]spsr 0x400001f3 and the memory addresses of some variables at the moment are ref:0xdcea0ffc, op:0xdcea0ffc, oend:0xdcea1000 As you can see, COPYLENGH is 8bytes, so @ref and @op can access the momory over @oend. Signed-off-by: JeHyeon Yeon <tom.yeon@xxxxxxxxxxxxx> Reviewed-by: David Sterba <dsterba@xxxxxxx> [Linux commit d5e7cafd69da24e6d6cc988fab6ea313a2577efc] Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx> master commit: fcc17f96c2776eb220e3dee79fd0ad6a624ffcd9 master date: 2015-03-26 11:19:10 +0100 commit 0327c934e4a2029fd3a1d922936eec4ad82fc3e4 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Apr 21 09:12:50 2015 +0200 hvmloader: don't treat ROM BAR like other BARs Its low 11 bits have different meaning. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: 73aa7fc2926c5ae30d8ebd049beadbb48e24d6c6 master date: 2015-03-26 11:17:51 +0100 commit 63c3eb26b7dc13bff20ec33a9ba872fc08bc0ab0 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Apr 21 09:11:43 2015 +0200 QEMU_UPSTREAM_REVISION = master again Acked-by: Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx> commit f2e08aa5b1bb470b2847d71490e28dfd96bcc2af Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Tue Apr 21 09:10:16 2015 +0200 domctl/sysctl: don't leak hypervisor stack to toolstacks This is CVE-2015-3340 / XSA-132. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx> master commit: 4ff3449f0e9d175ceb9551d3f2aecb59273f639d master date: 2015-04-21 09:03:15 +0200 (qemu changes not included) _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |