|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [xen-4.6-testing test] 77259: regressions - FAIL
flight 77259 xen-4.6-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/77259/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf-libvirt 3 host-install(3) broken in 77154 REGR. vs. 65639 test-amd64-i386-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 65639 test-amd64-amd64-xl-qemuu-ovmf-amd64 9 debian-hvm-install fail REGR. vs. 65639 Tests which are failing intermittently (not blocking): test-amd64-i386-rumpuserxen-i386 15 rumpuserxen-demo-xenstorels/xenstorels.repeat fail pass in 77154 test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 9 debian-hvm-install fail pass in 77154 Regressions which are regarded as allowable (not blocking): test-armhf-armhf-xl-rtds 9 debian-install fail REGR. vs. 65639 test-amd64-amd64-rumpuserxen-amd64 15 rumpuserxen-demo-xenstorels/xenstorels.repeat fail in 77154 like 65639 test-amd64-amd64-xl-qemut-win7-amd64 16 guest-stop fail like 65639 test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail like 65639 Tests which did not succeed, but are not blocking: test-armhf-armhf-libvirt 1 build-check(1) blocked in 77154 n/a test-armhf-armhf-libvirt-qcow2 1 build-check(1) blocked in 77154 n/a test-armhf-armhf-libvirt-raw 1 build-check(1) blocked in 77154 n/a test-armhf-armhf-libvirt-xsm 1 build-check(1) blocked in 77154 n/a 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-libvirt 14 guest-saverestore fail never pass test-armhf-armhf-libvirt 12 migrate-support-check fail never pass test-amd64-amd64-qemuu-nested-amd 16 debian-hvm-install/l1/l2 fail never pass test-amd64-i386-libvirt-xsm 12 migrate-support-check fail never pass test-amd64-amd64-libvirt 12 migrate-support-check fail never pass test-amd64-amd64-libvirt-xsm 12 migrate-support-check fail never pass test-armhf-armhf-xl 12 migrate-support-check fail never pass test-armhf-armhf-xl 13 saverestore-support-check fail never pass test-amd64-i386-libvirt 12 migrate-support-check fail never pass test-armhf-armhf-libvirt-qcow2 11 migrate-support-check fail never pass test-armhf-armhf-libvirt-qcow2 13 guest-saverestore fail never pass test-armhf-armhf-xl-arndale 12 migrate-support-check fail never pass test-armhf-armhf-xl-arndale 13 saverestore-support-check fail never pass test-armhf-armhf-xl-credit2 13 saverestore-support-check fail never pass test-armhf-armhf-xl-credit2 12 migrate-support-check fail never pass test-armhf-armhf-libvirt-raw 13 guest-saverestore fail never pass test-armhf-armhf-libvirt-raw 11 migrate-support-check fail never pass test-armhf-armhf-xl-xsm 13 saverestore-support-check fail never pass test-armhf-armhf-xl-xsm 12 migrate-support-check fail never pass test-armhf-armhf-xl-multivcpu 13 saverestore-support-check fail never pass test-armhf-armhf-xl-multivcpu 12 migrate-support-check fail never pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass test-armhf-armhf-xl-cubietruck 12 migrate-support-check fail never pass test-armhf-armhf-xl-cubietruck 13 saverestore-support-check fail never pass test-amd64-amd64-libvirt-vhd 11 migrate-support-check fail never pass test-armhf-armhf-libvirt-xsm 12 migrate-support-check fail never pass test-armhf-armhf-libvirt-xsm 14 guest-saverestore fail never pass test-armhf-armhf-xl-vhd 11 migrate-support-check fail never pass test-armhf-armhf-xl-vhd 12 saverestore-support-check fail never pass version targeted for testing: xen 828ac175e5f8f616b14e49f5353bca4dc2d0efd1 baseline version: xen 850bcd0f42e4912b6605a2caa42d5c466ed58bd1 Last test of basis 65639 2015-12-09 21:22:40 Z 29 days Failing since 66394 2015-12-15 18:17:32 Z 23 days 11 attempts Testing same since 77154 2016-01-05 17:23:57 Z 2 days 2 attempts ------------------------------------------------------------ People who touched revisions under test: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx> Brendan Gregg <bgregg@xxxxxxxxxxx> Daniel Kiper <daniel.kiper@xxxxxxxxxx> Dario Faggioli <dario.faggioli@xxxxxxxxxx> David Vrabel <david.vrabel@xxxxxxxxxx> Ed Swierk <eswierk@xxxxxxxxxxxxxxxxxx> Haozhong Zhang <haozhong.zhang@xxxxxxxxx> Ian Campbell <ian.campbell@xxxxxxxxxx> Ian Jackson <ian.jackson@xxxxxxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> Kevin Tian <kevin.tian@xxxxxxxxx> Malcolm Crossley <malcolm.crossley@xxxxxxxxxx> jobs: build-amd64-xsm pass build-armhf-xsm pass build-i386-xsm pass build-amd64 pass build-armhf pass build-i386 pass build-amd64-libvirt pass build-armhf-libvirt pass build-i386-libvirt pass build-amd64-prev pass build-i386-prev 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-qemut-debianhvm-amd64-xsm pass test-amd64-i386-xl-qemut-debianhvm-amd64-xsm pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm pass test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm pass test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm pass test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm pass test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm pass test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm fail test-amd64-amd64-libvirt-xsm pass test-armhf-armhf-libvirt-xsm fail test-amd64-i386-libvirt-xsm pass test-amd64-amd64-xl-xsm pass test-armhf-armhf-xl-xsm pass test-amd64-i386-xl-xsm pass test-amd64-amd64-qemuu-nested-amd fail test-amd64-amd64-xl-pvh-amd fail test-amd64-i386-qemut-rhel6hvm-amd pass test-amd64-i386-qemuu-rhel6hvm-amd pass test-amd64-amd64-xl-qemut-debianhvm-amd64 pass test-amd64-i386-xl-qemut-debianhvm-amd64 pass test-amd64-amd64-xl-qemuu-debianhvm-amd64 pass test-amd64-i386-xl-qemuu-debianhvm-amd64 pass test-amd64-i386-freebsd10-amd64 pass 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 pass test-amd64-amd64-xl-qemuu-win7-amd64 fail test-amd64-i386-xl-qemuu-win7-amd64 pass test-armhf-armhf-xl-arndale pass test-amd64-amd64-xl-credit2 pass test-armhf-armhf-xl-credit2 pass test-armhf-armhf-xl-cubietruck pass test-amd64-i386-freebsd10-i386 pass test-amd64-i386-rumpuserxen-i386 fail test-amd64-amd64-qemuu-nested-intel pass test-amd64-amd64-xl-pvh-intel fail test-amd64-i386-qemut-rhel6hvm-intel pass test-amd64-i386-qemuu-rhel6hvm-intel pass test-amd64-amd64-libvirt pass test-armhf-armhf-libvirt fail test-amd64-i386-libvirt pass test-amd64-amd64-migrupgrade pass test-amd64-i386-migrupgrade 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-libvirt-pair pass test-amd64-i386-libvirt-pair pass test-amd64-amd64-amd64-pvgrub pass test-amd64-amd64-i386-pvgrub pass test-amd64-amd64-pygrub pass test-armhf-armhf-libvirt-qcow2 fail test-amd64-amd64-xl-qcow2 pass test-armhf-armhf-libvirt-raw fail test-amd64-i386-xl-raw pass test-amd64-amd64-xl-rtds pass test-armhf-armhf-xl-rtds fail test-amd64-i386-xl-qemut-winxpsp3-vcpus1 pass test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 pass test-amd64-amd64-libvirt-vhd pass test-armhf-armhf-xl-vhd pass test-amd64-amd64-xl-qemut-winxpsp3 pass test-amd64-i386-xl-qemut-winxpsp3 pass test-amd64-amd64-xl-qemuu-winxpsp3 pass test-amd64-i386-xl-qemuu-winxpsp3 pass ------------------------------------------------------------ sg-report-flight on osstest.test-lab.xenproject.org logs: /home/logs/logs images: /home/logs/images Logs, config files, etc. are available at http://logs.test-lab.xenproject.org/osstest/logs Explanation of these reports, and of osstest in general, is at http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master Test harness code can be found at http://xenbits.xen.org/gitweb?p=osstest.git;a=summary Not pushing. ------------------------------------------------------------ commit 828ac175e5f8f616b14e49f5353bca4dc2d0efd1 Author: Ian Jackson <ian.jackson@xxxxxxxxxxxxx> Date: Mon Jan 4 15:35:54 2016 +0000 QEMU_TAG update commit eb32a519f5945dc7465f1f4f555e2dd9654250b7 Author: Malcolm Crossley <malcolm.crossley@xxxxxxxxxx> Date: Mon Dec 21 14:07:36 2015 +0100 x86: make debug output consistent in hvm_set_callback_via The unconditional printks in the switch statement of the hvm_set_callback_via function results in Xen log spam in non debug versions of Xen. The printks are for debug output only so conditionally compile the entire switch statement on debug versions of Xen only. This is XSA-169. Signed-off-by: Malcolm Crossley <malcolm.crossley@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx> master commit: 5c1048565ba5b240f47203bdb67572bee73d639e master date: 2015-12-21 13:40:48 +0100 commit cdd96b9be5a57ae7795750c3ae83ea6783030688 Author: Ian Jackson <ian.jackson@xxxxxxxxxxxxx> Date: Fri Dec 18 14:57:01 2015 +0000 QEMU_TAG update commit 33708eee8f6a1ac4f4f92317e5d0c412761d2fbb Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Thu Dec 17 14:27:25 2015 +0100 x86/HVM: avoid reading ioreq state more than once Otherwise, especially when the compiler chooses to translate the switch() to a jump table, unpredictable behavior (and in the jump table case arbitrary code execution) can result. This is XSA-166. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx> master commit: b452430a4cdfc801fa4bc391aed7522365e1deb6 master date: 2015-12-17 14:22:46 +0100 commit 82c5c64eaa813b8ec19b1d0016b062413dc12692 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Thu Dec 17 14:25:50 2015 +0100 x86: don't leak ST(n)/XMMn values to domains first using them FNINIT doesn't alter these registers, and hence using it is insufficient to initialize a guest's initial state. This is CVE-2015-8555 / XSA-165. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: 81818b3f277544535974204f8d840da86fa8a44f master date: 2015-12-17 14:22:13 +0100 commit fea8dbb3c31c89cf65320f8ce66f47f85f3c293c Author: Haozhong Zhang <haozhong.zhang@xxxxxxxxx> Date: Tue Dec 15 15:27:32 2015 +0100 x86/time: fix domain type check in tsc_set_info() Replace is_hvm_domain() in tsc_set_info() by has_hvm_container_domain() to keep consistent with other domain type checks in tsc_set_info(). Signed-off-by: Haozhong Zhang <haozhong.zhang@xxxxxxxxx> Reviewed-by: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx> master commit: 3c80d6f3c61eb0f8072f70b0a9a8c8c7adf17572 master date: 2015-12-08 09:46:30 +0100 commit 3d2d3d86a8e130ca1b708244bc2e16ef1975ca99 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Dec 15 15:26:56 2015 +0100 x86: refine nr_sockets calculation The previous variant didn't work for non-contiguous socket numbers. Reported-by: Ed Swierk <eswierk@xxxxxxxxxxxxxxxxxx> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Tested-by: Ed Swierk <eswierk@xxxxxxxxxxxxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: 4217080693f9a4831e290c7a31bc6b886be5ca12 master date: 2015-12-08 09:45:29 +0100 commit 1a448f836e1b9d26a91e7ea7e94a95a2dee58c9e Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Dec 15 15:26:07 2015 +0100 VT-d: drop unneeded Ivybridge quirk workaround We've been told by Intel that server chipsets don't need the workaround anymore starting with Ivybridge (Xeon E5/E7 v2); the second half of the workaround was missing anyway. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Kevin Tian <kevin.tian@xxxxxxxxx> master commit: a10307b3912e65bbdd9184ba5fe849d252b75f92 master date: 2015-12-03 15:33:10 +0100 commit 8e07a0dc588e5e0cc1fd56c0e76c3b29f6c82927 Author: David Vrabel <david.vrabel@xxxxxxxxxx> Date: Tue Dec 15 15:25:39 2015 +0100 evtchn: don't reuse ports that are still "busy" When using the FIFO ABI a guest may close an event channel that is still LINKED. If this port is reused, subsequent events may be lost because they may become pending on the wrong queue. This could be fixed by requiring guests to only close event channels that are not linked. This is difficult since: a) irq cleanup in the guest may be done in a context that cannot wait for the event to be unlinked; b) the guest may attempt to rebind a PIRQ whose previous close is still pending; and c) existing guests already have the problematic behaviour. Instead, simply check a port is not "busy" (i.e., it's not linked) before reusing it. Guests should still drain any queues for VCPUs that are being offlined, or the port will become unusable until the VCPU is onlined and starts processing events again. Signed-off-by: David Vrabel <david.vrabel@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> master commit: 78e24c269b0a4a8b864ece725e6d4209ed95dfa7 master date: 2015-12-02 15:21:46 +0100 commit 6e59151b50b8981a37b015ad1b10e4876eb20926 Author: David Vrabel <david.vrabel@xxxxxxxxxx> Date: Tue Dec 15 15:25:00 2015 +0100 x86/ept: remove unnecessary sync after resolving misconfigured entries When using EPT, type changes are done with the following steps: 1. Set entry as invalid (misconfigured) by settings a reserved memory type. 2. Flush all EPT and combined translations (ept_sync_domain()). 3. Fixup misconfigured entries as required (on EPT_MISCONFIG vmexits or when explicitly setting an entry. Since resolve_misconfig() only updates entries that were misconfigured, there is no need to invalidate any translations since the hardware does not cache misconfigured translations (vol 3, section 28.3.2). Remove the unnecessary (and very expensive) ept_sync_domain() calls). Signed-off-by: David Vrabel <david.vrabel@xxxxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Acked-by: Kevin Tian <kevin.tian@xxxxxxxxx> master commit: cea357ba4b3335ca5279ee9c00838f85575d5842 master date: 2015-12-02 15:19:53 +0100 commit d60b3a5d6ce50c7a3371a49cbc8c6cb0e2ce6cac Author: Daniel Kiper <daniel.kiper@xxxxxxxxxx> Date: Tue Dec 15 15:24:29 2015 +0100 x86/boot: check for not allowed sections before linking Currently check for not allowed sections is performed just after compilation. However, if compilation succeeds and check fails then second build will create xen.gz/xen.efi without any visible error. This happens because %.o: %.c recipe created object file during first run and make do not execute this recipe during second run. So, look for not allowed sections before linking. This way check will be executed every time. Signed-off-by: Daniel Kiper <daniel.kiper@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> master commit: d380b3559734739ae009cd3c0e9aabb5602863e2 master date: 2015-11-25 17:24:36 +0100 commit 57817d09bf6a55604a317b746c0177183ce50c66 Author: Brendan Gregg <bgregg@xxxxxxxxxxx> Date: Tue Dec 15 15:23:54 2015 +0100 x86/VPMU: return correct fixed PMC count Fixes a register typo. Signed-off-by: Brendan Gregg <bgregg@xxxxxxxxxxx> Reviewed-by: Dietmar Hahn <dietmar.hahn@xxxxxxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> master commit: 7d596f5ad70969d8171e1eb5b7a39d0dc6c11dc2 master date: 2015-11-25 11:12:55 +0100 commit 7dcd82d1aa68e793be05dd11cc587c909463a5c1 Author: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx> Date: Tue Dec 15 15:23:20 2015 +0100 x86/VPMU: Initialize VPMU's lvtpc vector If a guest sets up performance counters so that they can generate a PMC interrupt but does not initilaize APIC LVTPC register the resulting interrupt will cause an APIC error. Note that a guest deciding to clear LVTPC in order to unduce the error will not be successful in achieving its goal: emulation code only looks at the mask bit and always sets the vector to PMU_APIC_VECTOR. Only the initial value of LVTPC (which is zero) that gets loaded into APIC as result of PMC initialization is the problem. Signed-off-by: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx> master commit: 0c3f24645b07b875bc1294fb4627f01e030690fe master date: 2015-11-24 18:33:08 +0100 commit 499886c800ef88263f17a6b861e7cef2c707a221 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Dec 15 15:22:58 2015 +0100 x86/vPMU: document as unsupported This is XSA-163. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> master commit: c03480cf5c4e96fb4afb2237ad0a3cac7162564a master date: 2015-11-24 18:32:20 +0100 commit 880b5f3012893ded410a05522cc50ad94b02d890 Author: Dario Faggioli <dario.faggioli@xxxxxxxxxx> Date: Tue Dec 15 15:22:29 2015 +0100 sched: fix locking for insert_vcpu() in credit1 and RTDS The insert_vcpu() hook is handled with inconsistent locking. In fact, schedule_cpu_switch() calls the hook with runqueue lock held, while sched_move_domain() relies on the hook implementations to take the lock themselves (and, since that is not done in Credit1 and RTDS, such operation is not safe in those cases). This is fixed as follows: - take the lock in the hook implementations, in specific schedulers' code; - avoid calling insert_vcpu(), for the idle vCPU, in schedule_cpu_switch(). In fact, idle vCPUs are set to run immediately, and the various schedulers won't insert them in their runqueues anyway, even when explicitly asked to. While there, still in schedule_cpu_switch(), locking with _irq() is enough (there's no need to do *_irqsave()). Signed-off-by: Dario Faggioli <dario.faggioli@xxxxxxxxxx> Reviewed-by: Meng Xu <mengxu@xxxxxxxxxxxxx> Reviewed-by: George Dunlap <george.dunlap@xxxxxxxxxx> master commit: ae2f41e3d7e7798537b7ea6dbb9a0c6aeb1179e3 master date: 2015-11-24 14:48:34 +0100 commit b56ae5b48c3890b0c52f5676d0c29e3b4a5545e9 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Dec 15 15:21:41 2015 +0100 VMX: fix/adjust trap injection In the course of investigating the 4.1.6 backport issue of the XSA-156 patch I realized that #DB injection has always been broken, but with it now getting always intercepted the problem has got worse: Documentation clearly states that neither DR7.GD nor DebugCtl.LBR get cleared before the intercept, so this is something we need to do before reflecting the intercepted exception. While adjusting this (and also with 4.1.6's strange use of X86_EVENTTYPE_SW_EXCEPTION for #DB in mind) I further realized that the special casing of individual vectors shouldn't be done for software interrupts (resulting from INT $nn). And then some code movement: Setting of CR2 for #PF can be done in the same switch() statement (no need for a separate if()), and reading of intr_info is better done close the the consumption of the variable (allowing the compiler to generate better code / use fewer registers for variables). Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Kevin Tian <kevin.tian@xxxxxxxxx> master commit: 81a28f14009f4d8577a81b28dd06f6828112054b master date: 2015-11-24 12:30:31 +0100 (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 |