[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [xen-unstable-smoke test] 65083: regressions - FAIL
flight 65083 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/65083/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-xl 16 guest-start/debian.repeat fail REGR. vs. 65076 Tests which did not succeed, but are not blocking: test-amd64-amd64-libvirt 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 version targeted for testing: xen 0c3f24645b07b875bc1294fb4627f01e030690fe baseline version: xen 9b436680f081ae397e8c25ce2c23d3cd1359ce86 Last test of basis 65076 2015-11-24 17:02:33 Z 0 days Testing same since 65083 2015-11-24 20:02:22 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> jobs: build-amd64 pass build-armhf pass build-amd64-libvirt pass test-armhf-armhf-xl fail test-amd64-amd64-xl-qemuu-debianhvm-i386 pass test-amd64-amd64-libvirt 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 0c3f24645b07b875bc1294fb4627f01e030690fe Author: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx> Date: Tue Nov 24 18:33:08 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> commit c03480cf5c4e96fb4afb2237ad0a3cac7162564a Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Nov 24 18:32:20 2015 +0100 x86/vPMU: document as unsupported This is XSA-163. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> (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 |