|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [xen-4.5-testing test] 34907: regressions - trouble: broken/fail/pass
flight 34907 xen-4.5-testing real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/34907/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-pvh-intel 5 xen-boot fail REGR. vs. 34731 test-armhf-armhf-libvirt 12 guest-start.2 fail REGR. vs. 34731 test-amd64-amd64-xl-pvh-amd 5 xen-boot fail REGR. vs. 34731 test-amd64-i386-libvirt 3 host-install(3) broken REGR. vs. 34731 test-amd64-amd64-rumpuserxen-amd64 3 host-install(3) broken REGR. vs. 34731 test-amd64-i386-xl 5 xen-boot fail REGR. vs. 34731 test-amd64-i386-qemut-rhel6hvm-intel 5 xen-boot fail REGR. vs. 34731 test-amd64-i386-rhel6hvm-intel 5 xen-boot fail REGR. vs. 34731 test-amd64-i386-qemut-rhel6hvm-amd 5 xen-boot fail REGR. vs. 34731 test-amd64-i386-qemuu-rhel6hvm-intel 5 xen-boot fail REGR. vs. 34731 test-amd64-i386-qemuu-rhel6hvm-amd 5 xen-boot fail REGR. vs. 34731 test-amd64-i386-rhel6hvm-amd 5 xen-boot fail REGR. vs. 34731 test-amd64-i386-freebsd10-i386 3 host-install(3) broken REGR. vs. 34731 test-amd64-amd64-xl-multivcpu 5 xen-boot fail REGR. vs. 34731 test-amd64-amd64-xl 5 xen-boot fail REGR. vs. 34731 test-amd64-amd64-xl-credit2 5 xen-boot fail REGR. vs. 34731 test-amd64-i386-freebsd10-amd64 5 xen-boot fail REGR. vs. 34731 test-amd64-i386-xl-qemuu-ovmf-amd64 5 xen-boot fail REGR. vs. 34731 test-amd64-i386-rumpuserxen-i386 5 xen-boot fail REGR. vs. 34731 test-amd64-i386-xl-qemut-debianhvm-amd64 5 xen-boot fail REGR. vs. 34731 test-amd64-amd64-xl-qemuu-win7-amd64 5 xen-boot fail REGR. vs. 34731 test-amd64-i386-xl-winxpsp3 5 xen-boot fail REGR. vs. 34731 test-amd64-i386-xl-qemuu-debianhvm-amd64 5 xen-boot fail REGR. vs. 34731 test-amd64-i386-xl-qemut-winxpsp3-vcpus1 5 xen-boot fail REGR. vs. 34731 test-amd64-i386-xl-winxpsp3-vcpus1 5 xen-boot fail REGR. vs. 34731 test-amd64-amd64-pair 8 xen-boot/dst_host fail REGR. vs. 34731 test-amd64-amd64-pair 7 xen-boot/src_host fail REGR. vs. 34731 test-amd64-i386-xl-qemuu-winxpsp3 5 xen-boot fail REGR. vs. 34731 test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 5 xen-boot fail REGR. vs. 34731 test-amd64-i386-xl-qemuu-win7-amd64 5 xen-boot fail REGR. vs. 34731 test-amd64-amd64-xl-qemut-win7-amd64 5 xen-boot fail REGR. vs. 34731 test-amd64-i386-xl-win7-amd64 5 xen-boot fail REGR. vs. 34731 test-amd64-amd64-xl-win7-amd64 5 xen-boot fail REGR. vs. 34731 test-amd64-amd64-xl-qemut-winxpsp3 5 xen-boot fail REGR. vs. 34731 test-amd64-amd64-xl-qemuu-debianhvm-amd64 5 xen-boot fail REGR. vs. 34731 test-amd64-amd64-xl-qemut-debianhvm-amd64 5 xen-boot fail REGR. vs. 34731 test-amd64-i386-xl-qemut-win7-amd64 5 xen-boot fail REGR. vs. 34731 test-amd64-amd64-xl-qemuu-ovmf-amd64 3 host-install(3) broken REGR. vs. 34731 test-amd64-i386-pair 8 xen-boot/dst_host fail REGR. vs. 34731 test-amd64-i386-pair 7 xen-boot/src_host fail REGR. vs. 34731 test-amd64-i386-xl-qemut-winxpsp3 5 xen-boot fail REGR. vs. 34731 test-amd64-amd64-xl-qemuu-winxpsp3 5 xen-boot fail REGR. vs. 34731 test-amd64-amd64-xl-winxpsp3 5 xen-boot fail REGR. vs. 34731 Regressions which are regarded as allowable (not blocking): test-amd64-amd64-libvirt 5 xen-boot fail like 34638 test-amd64-amd64-xl-pcipt-intel 5 xen-boot fail REGR. vs. 34731 test-amd64-amd64-xl-sedf 5 xen-boot fail REGR. vs. 34731 test-amd64-amd64-xl-sedf-pin 5 xen-boot fail REGR. vs. 34731 Tests which did not succeed, but are not blocking: test-armhf-armhf-xl-sedf 10 migrate-support-check fail never pass test-armhf-armhf-xl-multivcpu 10 migrate-support-check fail never pass test-armhf-armhf-libvirt 10 migrate-support-check fail never pass test-armhf-armhf-xl 10 migrate-support-check fail never pass test-armhf-armhf-xl-midway 10 migrate-support-check fail never pass test-armhf-armhf-xl-sedf-pin 10 migrate-support-check fail never pass test-armhf-armhf-xl-credit2 5 xen-boot fail never pass version targeted for testing: xen 75ac8cf17a6f7a4ef6dd598295e8d186c010b440 baseline version: xen 2417e243bb510dafdbd589a5aeedb29095e62c10 ------------------------------------------------------------ People who touched revisions under test: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx> Ian Campbell <ian.campbell@xxxxxxxxxx> Julien Grall <julien.grall@xxxxxxxxxx> Paul Durrant <paul.durrant@xxxxxxxxxx> ------------------------------------------------------------ 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 fail test-armhf-armhf-xl pass test-amd64-i386-xl fail 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 fail 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 fail test-amd64-i386-freebsd10-amd64 fail test-amd64-amd64-xl-qemuu-ovmf-amd64 broken test-amd64-i386-xl-qemuu-ovmf-amd64 fail test-amd64-amd64-rumpuserxen-amd64 broken 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-amd64-amd64-xl-credit2 fail test-armhf-armhf-xl-credit2 fail test-amd64-i386-freebsd10-i386 broken test-amd64-i386-rumpuserxen-i386 fail test-amd64-amd64-xl-pcipt-intel fail test-amd64-amd64-xl-pvh-intel fail test-amd64-i386-rhel6hvm-intel fail test-amd64-i386-qemut-rhel6hvm-intel fail test-amd64-i386-qemuu-rhel6hvm-intel fail test-amd64-amd64-libvirt fail test-armhf-armhf-libvirt fail test-amd64-i386-libvirt broken test-armhf-armhf-xl-midway pass test-amd64-amd64-xl-multivcpu fail test-armhf-armhf-xl-multivcpu pass test-amd64-amd64-pair fail test-amd64-i386-pair fail test-amd64-amd64-xl-sedf-pin fail 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.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 broken-step test-amd64-i386-libvirt host-install(3) broken-step test-amd64-amd64-rumpuserxen-amd64 host-install(3) broken-step test-amd64-i386-freebsd10-i386 host-install(3) broken-step test-amd64-amd64-xl-qemuu-ovmf-amd64 host-install(3) Not pushing. ------------------------------------------------------------ commit 75ac8cf17a6f7a4ef6dd598295e8d186c010b440 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Wed Feb 18 16:42:11 2015 +0100 x86/nmi: fix shootdown of pcpus running in VMX non-root mode c/s 7dd3b06ff "vmx: fix handling of NMI VMEXIT" fixed one issue but inadvertently introduced a regression when it came to the NMI shootdown. The shootdown code worked by patching vector 2 in each IDT, but the introduced direct call to do_nmi() bypassed this. Instead of patching each IDT, take a different approach by updating the existing dispatch table. This allows for the removal of the remote IDT patching and the removal of the nmi_crash() entry point. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> master commit: cbeeaa7da01bfa37c1fcdfe79e8f4f1400262ccb master date: 2015-02-11 17:18:27 +0100 commit ad6b254f10559c68c4882ab1bb3fe6259240981c Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Wed Feb 18 16:41:20 2015 +0100 x86/traps: export the exception_table[] function pointer table to C and use it in preference to the direct call to do_nmi() in vmx.c The value 'TRAP_last_reserved' was only used where 'TRAP_nr' would be more appropriate, so is replaced. No functional change Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> master commit: d3eb16b8a7c06f0d2a2110948a8477a62b541bbf master date: 2015-02-11 17:16:18 +0100 commit 1e44c921c6adc0400ac71fb86667618ec407ba45 Author: Paul Durrant <paul.durrant@xxxxxxxxxx> Date: Wed Feb 18 16:40:30 2015 +0100 x86/hvm: explicitly mark ioreq server pages dirty ...when they are added back into the guest physmap, when an ioreq server is disabled. If this is not done then the pages are missed during migration, causing ioreq server creation to fail on the remote end. This problem only manifests if the ioreq server is non-default because in the default case the pages are never removed from the guest physmap. Signed-off-by: Paul Durrant <paul.durrant@xxxxxxxxxx> master commit: 70f691130081324a8efb97b23c504d8abc5421db master date: 2015-02-10 13:29:51 +0100 commit 2bfef90c47de6ff89c01cafe3e0c413ee223700b Author: Paul Durrant <paul.durrant@xxxxxxxxxx> Date: Wed Feb 18 16:39:46 2015 +0100 x86/hvm: wait for at least one ioreq server to be enabled In the case where a stub domain is providing emulation for an HVM guest, there is no interlock in the toolstack to make sure that the stub domain is up and running before the guest is unpaused. Prior to the introduction of ioreq servers this was not a problem, since there was only ever one emulator so ioreqs were simply created anyway and the vcpu remained blocked until the stub domain started and picked up the ioreq. Since ioreq servers allow for multiple emulators for a single guest it's not possible to know a priori which emulator will handle a particular ioreq, so emulators must attach to a guest before the guest runs. This patch works around the lack of interlock in the toolstack for stub domains by keeping the domain paused until at least one ioreq server is created and enabled, which in practice means the stub domain is indeed up and running. Signed-off-by: Paul Durrant <paul.durrant@xxxxxxxxxx> master commit: dd748d128d86996592afafea02e578cc7d4e6d42 master date: 2015-02-10 13:28:40 +0100 commit d976397ffd3c9a16c29a3df3b9b0cdf9065938e1 Author: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx> Date: Wed Feb 18 16:38:19 2015 +0100 x86/VPMU: disable when NMI watchdog is on NMI watchdog sets APIC_LVTPC register to generate an NMI when PMU counter overflow occurs. This may be overwritten by VPMU code later, effectively turning off the watchdog. We should disable VPMU when NMI watchdog is running. Signed-off-by: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: e5e09b5c46444b0ab8450c6d6ee8316d4016ac18 master date: 2015-02-03 11:30:09 +0100 commit 1e753b62a178afbd48a23dc4cb451c59bb0caf34 Author: Julien Grall <julien.grall@xxxxxxxxxx> Date: Fri Jan 23 14:15:07 2015 +0000 xen/arm: vgic-v2: Don't crash the hypervisor if the SGI target mode is invalid The GICv2 spec reserved the value 0b11 for GICD_SGIR.TargetListFilter. Even if it's an invalid value, a malicious guest could write this value and threfore crash the hypervisor. Replace the BUG() by logging the error and inject a data abort to the guest. This was introduced by commit ea37fd21110b6fbcf9257f814076a243d3873cb7 "xen/arm: split vgic driver into generic and vgic-v2 driver". This is CVE-2015-0268 / XSA-117. Signed-off-by: Julien Grall <julien.grall@xxxxxxxxxx> Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx> (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 |