|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [xen-unstable test] 24916: regressions - trouble: broken/fail/pass
flight 24916 xen-unstable real [real] http://www.chiark.greenend.org.uk/~xensrcts/logs/24916/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-i386-oldkern 2 host-install(2) broken REGR. vs. 24862 build-amd64-oldkern 4 xen-build fail REGR. vs. 24862 build-i386-oldkern 4 xen-build fail in 24901 REGR. vs. 24862 Tests which are failing intermittently (not blocking): test-amd64-i386-xl-multivcpu 3 host-install(3) broken pass in 24901 test-amd64-i386-rhel6hvm-intel 3 host-install(3) broken pass in 24901 test-amd64-i386-qemuu-rhel6hvm-intel 3 host-install(3) broken pass in 24901 test-amd64-amd64-xl-win7-amd64 3 host-install(3) broken pass in 24901 test-amd64-i386-xl-qemuu-win7-amd64 7 windows-install fail in 24901 pass in 24916 test-amd64-amd64-xl-win7-amd64 7 windows-install fail in 24901 pass in 24882 test-amd64-amd64-xl-sedf 10 guest-saverestore fail in 24882 pass in 24916 Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-pcipt-intel 9 guest-start fail never pass test-armhf-armhf-xl 9 guest-start fail never pass test-amd64-i386-xend-qemut-winxpsp3 16 leak-check/check fail never pass test-amd64-i386-xend-winxpsp3 16 leak-check/check fail never pass test-amd64-i386-xl-winxpsp3-vcpus1 13 guest-stop fail never pass test-amd64-amd64-xl-qemuu-winxpsp3 13 guest-stop fail never pass test-amd64-amd64-xl-qemuu-win7-amd64 13 guest-stop fail never pass test-amd64-i386-xl-qemut-win7-amd64 13 guest-stop fail never pass test-amd64-amd64-xl-qemut-winxpsp3 13 guest-stop fail never pass test-amd64-amd64-xl-winxpsp3 13 guest-stop fail never pass test-amd64-i386-xl-qemut-winxpsp3-vcpus1 13 guest-stop fail never pass test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 13 guest-stop fail never pass test-amd64-i386-xl-qemuu-win7-amd64 13 guest-stop fail never pass test-amd64-amd64-xl-qemut-win7-amd64 13 guest-stop fail never pass test-amd64-i386-xl-win7-amd64 13 guest-stop fail never pass test-amd64-amd64-xl-win7-amd64 13 guest-stop fail in 24882 never pass version targeted for testing: xen 4e8d89bc1445f91c4c6c7bf0ad8d51b0c809841e baseline version: xen d883c179a74111a6804baf8cb8224235242a88fc ------------------------------------------------------------ People who touched revisions under test: "Zhang, Yang Z" <yang.z.zhang@xxxxxxxxx> Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx> Daniel De Graaf <dgdegra@xxxxxxxxxxxxx> George Dunlap <george.dunlap@xxxxxxxxxxxxx> Ian Campbell <ian.campbell@xxxxxxxxxx> Ian Jackson <ian.jackson@xxxxxxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> Julien Grall <julien.grall@xxxxxxxxxx> Keir Fraser <keir@xxxxxxx> Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> Mukesh Rathor <mukesh.rathor@xxxxxxxxxx> Olaf Hering <olaf@xxxxxxxxx> Roger Pau Monné <roger.pau@xxxxxxxxxx> Tim Deegan <tim@xxxxxxx> Yang Zhang <yang.z.zhang@xxxxxxxxx> ------------------------------------------------------------ jobs: build-amd64-xend pass build-i386-xend pass build-amd64 pass build-armhf pass build-i386 pass build-amd64-oldkern fail build-i386-oldkern broken build-amd64-pvops pass build-armhf-pvops pass build-i386-pvops pass test-amd64-amd64-xl pass test-armhf-armhf-xl fail test-amd64-i386-xl pass test-amd64-i386-rhel6hvm-amd pass test-amd64-i386-qemut-rhel6hvm-amd pass test-amd64-i386-qemuu-rhel6hvm-amd pass test-amd64-i386-freebsd10-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 broken test-amd64-i386-xl-win7-amd64 fail test-amd64-i386-xl-credit2 pass test-amd64-i386-freebsd10-i386 pass test-amd64-amd64-xl-pcipt-intel fail test-amd64-i386-rhel6hvm-intel broken test-amd64-i386-qemut-rhel6hvm-intel pass test-amd64-i386-qemuu-rhel6hvm-intel broken test-amd64-i386-xl-multivcpu broken test-amd64-amd64-pair pass test-amd64-i386-pair pass test-amd64-amd64-xl-sedf-pin pass test-amd64-amd64-pv pass test-amd64-i386-pv pass test-amd64-amd64-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-i386-xend-qemut-winxpsp3 fail test-amd64-amd64-xl-qemut-winxpsp3 fail test-amd64-amd64-xl-qemuu-winxpsp3 fail test-amd64-i386-xend-winxpsp3 fail test-amd64-amd64-xl-winxpsp3 fail ------------------------------------------------------------ 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. ------------------------------------------------------------ commit 4e8d89bc1445f91c4c6c7bf0ad8d51b0c809841e Author: Mukesh Rathor <mukesh.rathor@xxxxxxxxxx> Date: Thu Feb 13 17:56:39 2014 +0100 pvh: Fix regression due to assumption that HVM paths MUST use io-backend device The commit 09bb434748af9bfe3f7fca4b6eef721a7d5042a4 "Nested VMX: prohibit virtual vmentry/vmexit during IO emulation" assumes that the HVM paths are only taken by HVM guests. With the PVH enabled that is no longer the case - which means that we do not have to have the IO-backend device (QEMU) enabled. As such, that patch can crash the hypervisor: Xen call trace: [<ffff82d0801ddd9a>] nvmx_switch_guest+0x4d/0x903 [<ffff82d0801de95b>] vmx_asm_vmexit_handler+0x4b/0xc0 Pagetable walk from 000000000000001e: L4[0x000] = 0000000000000000 ffffffffffffffff **************************************** Panic on CPU 7: FATAL PAGE FAULT [error_code=0000] Faulting linear address: 000000000000001e **************************************** as we do not have an io based backend. In the case that the PVH guest does run an HVM guest inside it - we need to do further work to suport this - and for now the check will bail us out. We also fix spelling mistakes and the sentence structure. Suggested-by: Jan Beulich <jbeulich@xxxxxxxx> Signed-off-by: Mukesh Rathor <mukesh.rathor@xxxxxxxxxx> Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> Acked-by: George Dunlap <george.dunlap@xxxxxxxxxxxxx> Release-acked-by: George Dunlap <george.dunlap@xxxxxxxxxxxxx> Acked-by: "Zhang, Yang Z" <yang.z.zhang@xxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit 077fc1c04d70ef1748ac2daa6622b3320a1a004c Author: Yang Zhang <yang.z.zhang@xxxxxxxxx> Date: Thu Feb 13 15:50:22 2014 +0000 When enabling log dirty mode, it sets all guest's memory to readonly. And in HAP enabled domain, it modifies all EPT entries to clear write bit to make sure it is readonly. This will cause problem if VT-d shares page table with EPT: the device may issue a DMA write request, then VT-d engine tells it the target memory is readonly and result in VT-d fault. Currnetly, there are two places will enable log dirty mode: migration and vram tracking. Migration with device assigned is not allowed, so it is ok. For vram, it doesn't need to set all memory to readonly. Only track the vram range is enough. Signed-off-by: Yang Zhang <yang.z.zhang@xxxxxxxxx> Acked-by: Tim Deegan <tim@xxxxxxx> commit 0e251a8371574b905d37d7650d1d625caf0f1181 Author: Tim Deegan <tim@xxxxxxx> Date: Thu Feb 13 15:13:07 2014 +0000 xen: Don't use __builtin_stdarg_start(). Cset fca49a00 ("netbsd: build fix with gcc 4.5") changed the definition of va_start() to use __builtin_va_start() rather than __builtin_stdarg_start() for GCCs >= 4.5, but in fact GCC dropped __builtin_stdarg_start() before v3.3. Signed-off-by: Tim Deegan <tim@xxxxxxx> Tested-by: Roger Pau Monné <roger.pau@xxxxxxxxxx> commit d2985386925fab3abe075852db46df29b56c95bb Author: Olaf Hering <olaf@xxxxxxxxx> Date: Thu Feb 13 15:43:24 2014 +0100 docs: mention whitespace handling diskspec target= parsing disk=[ ' target=/dev/loop0 ' ] will fail to parse because '/dev/loop ' does not exist. Signed-off-by: Olaf Hering <olaf@xxxxxxxxx> Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx> commit 0873829a70daa3c23d03b9841ccd529f05889f21 Author: Tim Deegan <tim@xxxxxxx> Date: Thu Feb 13 12:13:58 2014 +0000 xen: stop trying to use the system <stdarg.h> and <stdbool.h> We already have our own versions of the stdarg/stdbool definitions, for systems where those headers are installed in /usr/include. On linux, they're typically installed in compiler-specific paths, but finding them has proved unreliable. Drop that and use our own versions everywhere. Signed-off-by: Tim Deegan <tim@xxxxxxx> Tested-by: Julien Grall <julien.grall@xxxxxxxxxx> Acked-by: Keir Fraser <keir@xxxxxxx> commit 42788ddd24a06bf05f0f2b5da1880ed89736bd7b Author: Jan Beulich <JBeulich@xxxxxxxx> Date: Thu Feb 13 12:57:43 2014 +0000 tools/configure: correct --enable-blktap1 help text Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx> commit 1278b09cc5a38da4efbe0de37a7f9fab9d19f913 Author: Daniel De Graaf <dgdegra@xxxxxxxxxxxxx> Date: Tue Feb 11 10:25:17 2014 -0500 docs/vtpm: fix auto-shutdown reference The automatic shutdown feature of the vTPM was removed because it interfered with pv-grub measurement support and was also not triggered if the guest did not use the vTPM. Virtual TPM domains will need to be shut down or destroyed on guest shutdown via a script or other user action. This also fixes an incorrect reference to the vTPM being PV-only. Signed-off-by: Daniel De Graaf <dgdegra@xxxxxxxxxxxxx> Acked-by: Ian Campbell <ian.campbell@xxxxxxxxxx> commit 001bdcee7bc19be3e047d227b4d940c04972eb02 Author: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx> Date: Thu Feb 13 10:49:55 2014 +0100 x86/pci: Store VF's memory space displacement in a 64-bit value VF's memory space offset can be greater than 4GB and therefore needs to be stored in a 64-bit variable. Signed-off-by: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx> commit 3ac3817762d1a8b39fa45998ec8c40cabfcfc802 Author: Ian Campbell <ian.campbell@xxxxxxxxxx> Date: Wed Feb 12 14:27:37 2014 +0000 xl: suppress suspend/resume functions on platforms which do not support it. ARM does not (currently) support migration, so stop offering tasty looking treats like "xl migrate". Apart from the UI improvement my intention is to use this in osstest to detect whether to attempt the save/restore/migrate tests. Other than the additions of the #define/#ifdef there is a tiny bit of code motion ("dump-core" in the command list and core_dump_domain in the implementations) which serves to put ifdeffable bits next to each other. Signed-off-by: Ian Campbell <ian.campbell@xxxxxxxxxx> Acked-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx> (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 |