|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [xen-4.10-testing test] 135675: regressions - FAIL
flight 135675 xen-4.10-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/135675/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-migrupgrade 24 leak-check/check/src_host fail REGR. vs. 135478 test-amd64-amd64-migrupgrade 25 leak-check/check/dst_host fail REGR. vs. 135478 test-amd64-amd64-pair 26 leak-check/check/src_host fail REGR. vs. 135478 test-amd64-amd64-pair 27 leak-check/check/dst_host fail REGR. vs. 135478 test-amd64-amd64-libvirt-pair 26 leak-check/check/src_host fail REGR. vs. 135478 test-amd64-amd64-libvirt-pair 27 leak-check/check/dst_host fail REGR. vs. 135478 Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-qcow2 17 guest-localmigrate/x10 fail like 135478 test-amd64-amd64-qemuu-nested-amd 17 debian-hvm-install/l1/l2 fail like 135478 test-amd64-i386-xl-qemut-ws16-amd64 17 guest-stop fail like 135478 test-amd64-amd64-xl-qemuu-dmrestrict-amd64-dmrestrict 10 debian-hvm-install fail never pass test-amd64-i386-xl-qemuu-dmrestrict-amd64-dmrestrict 10 debian-hvm-install fail never pass test-amd64-i386-libvirt 13 migrate-support-check fail never pass test-amd64-amd64-libvirt-xsm 13 migrate-support-check fail never pass test-amd64-amd64-libvirt 13 migrate-support-check fail never pass test-arm64-arm64-xl-credit2 13 migrate-support-check fail never pass test-arm64-arm64-xl-credit1 13 migrate-support-check fail never pass test-arm64-arm64-xl 13 migrate-support-check fail never pass test-arm64-arm64-xl-credit1 14 saverestore-support-check fail never pass test-arm64-arm64-xl-credit2 14 saverestore-support-check fail never pass test-arm64-arm64-xl 14 saverestore-support-check fail never pass test-arm64-arm64-xl-xsm 13 migrate-support-check fail never pass test-arm64-arm64-xl-xsm 14 saverestore-support-check fail never pass test-arm64-arm64-libvirt-xsm 13 migrate-support-check fail never pass test-arm64-arm64-libvirt-xsm 14 saverestore-support-check fail never pass test-amd64-i386-libvirt-xsm 13 migrate-support-check fail never pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check fail never pass test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check fail never pass test-amd64-amd64-libvirt-vhd 12 migrate-support-check fail never pass test-armhf-armhf-xl 13 migrate-support-check fail never pass test-armhf-armhf-xl 14 saverestore-support-check fail never pass test-armhf-armhf-xl-arndale 13 migrate-support-check fail never pass test-armhf-armhf-xl-arndale 14 saverestore-support-check fail never pass test-armhf-armhf-libvirt 13 migrate-support-check fail never pass test-armhf-armhf-libvirt 14 saverestore-support-check fail never pass test-armhf-armhf-xl-multivcpu 13 migrate-support-check fail never pass test-armhf-armhf-xl-multivcpu 14 saverestore-support-check fail never pass test-armhf-armhf-xl-rtds 13 migrate-support-check fail never pass test-armhf-armhf-xl-rtds 14 saverestore-support-check fail never pass test-armhf-armhf-libvirt-raw 12 migrate-support-check fail never pass test-armhf-armhf-libvirt-raw 13 saverestore-support-check fail never pass test-amd64-amd64-xl-qemut-win7-amd64 17 guest-stop fail never pass test-armhf-armhf-xl-credit1 13 migrate-support-check fail never pass test-armhf-armhf-xl-credit1 14 saverestore-support-check fail never pass test-amd64-i386-xl-qemut-win7-amd64 17 guest-stop fail never pass test-armhf-armhf-xl-cubietruck 13 migrate-support-check fail never pass test-armhf-armhf-xl-cubietruck 14 saverestore-support-check fail never pass test-armhf-armhf-xl-credit2 13 migrate-support-check fail never pass test-armhf-armhf-xl-credit2 14 saverestore-support-check fail never pass test-amd64-i386-xl-qemuu-win7-amd64 17 guest-stop fail never pass test-amd64-amd64-xl-qemuu-win7-amd64 17 guest-stop fail never pass test-armhf-armhf-xl-vhd 12 migrate-support-check fail never pass test-armhf-armhf-xl-vhd 13 saverestore-support-check fail never pass test-amd64-i386-xl-qemuu-ws16-amd64 17 guest-stop fail never pass test-amd64-amd64-xl-qemut-ws16-amd64 17 guest-stop fail never pass test-amd64-amd64-xl-qemuu-ws16-amd64 17 guest-stop fail never pass test-amd64-i386-xl-qemut-win10-i386 10 windows-install fail never pass test-amd64-amd64-xl-qemut-win10-i386 10 windows-install fail never pass test-amd64-amd64-xl-qemuu-win10-i386 10 windows-install fail never pass test-amd64-i386-xl-qemuu-win10-i386 10 windows-install fail never pass version targeted for testing: xen aa6978c2688f28e5fc55c960bbfe5e64f9105f84 baseline version: xen 5a81de4c6b6036974f29e2330a493f23a8f0c1f0 Last test of basis 135478 2019-05-01 16:06:37 Z 4 days Testing same since 135675 2019-05-04 02:43:13 Z 2 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Igor Druzhinin <igor.druzhinin@xxxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> Kevin Tian <kevin.tian@xxxxxxxxx> Wei Liu <wei.liu2@xxxxxxxxxx> jobs: build-amd64-xsm pass build-arm64-xsm pass build-i386-xsm pass build-amd64-xtf pass build-amd64 pass build-arm64 pass build-armhf pass build-i386 pass build-amd64-libvirt pass build-arm64-libvirt pass build-armhf-libvirt pass build-i386-libvirt pass build-amd64-prev pass build-i386-prev pass build-amd64-pvops pass build-arm64-pvops pass build-armhf-pvops pass build-i386-pvops pass test-xtf-amd64-amd64-1 pass test-xtf-amd64-amd64-2 pass test-xtf-amd64-amd64-3 pass test-xtf-amd64-amd64-4 pass test-xtf-amd64-amd64-5 pass test-amd64-amd64-xl pass test-arm64-arm64-xl pass test-armhf-armhf-xl pass test-amd64-i386-xl pass test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm pass test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm pass test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm pass test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm pass test-amd64-amd64-xl-qemut-debianhvm-i386-xsm pass test-amd64-i386-xl-qemut-debianhvm-i386-xsm pass test-amd64-amd64-xl-qemuu-debianhvm-i386-xsm pass test-amd64-i386-xl-qemuu-debianhvm-i386-xsm pass test-amd64-amd64-libvirt-xsm pass test-arm64-arm64-libvirt-xsm pass test-amd64-i386-libvirt-xsm pass test-amd64-amd64-xl-xsm pass test-arm64-arm64-xl-xsm pass test-amd64-i386-xl-xsm pass test-amd64-amd64-qemuu-nested-amd fail test-amd64-amd64-xl-pvhv2-amd pass 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 pass test-amd64-i386-xl-qemuu-ovmf-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-qemut-ws16-amd64 fail test-amd64-i386-xl-qemut-ws16-amd64 fail test-amd64-amd64-xl-qemuu-ws16-amd64 fail test-amd64-i386-xl-qemuu-ws16-amd64 fail test-armhf-armhf-xl-arndale pass test-amd64-amd64-xl-credit1 pass test-arm64-arm64-xl-credit1 pass test-armhf-armhf-xl-credit1 pass test-amd64-amd64-xl-credit2 pass test-arm64-arm64-xl-credit2 pass test-armhf-armhf-xl-credit2 pass test-armhf-armhf-xl-cubietruck pass test-amd64-amd64-xl-qemuu-dmrestrict-amd64-dmrestrict fail test-amd64-i386-xl-qemuu-dmrestrict-amd64-dmrestrict fail test-amd64-i386-freebsd10-i386 pass test-amd64-amd64-xl-qemut-win10-i386 fail test-amd64-i386-xl-qemut-win10-i386 fail test-amd64-amd64-xl-qemuu-win10-i386 fail test-amd64-i386-xl-qemuu-win10-i386 fail test-amd64-amd64-qemuu-nested-intel pass test-amd64-amd64-xl-pvhv2-intel pass test-amd64-i386-qemut-rhel6hvm-intel pass test-amd64-i386-qemuu-rhel6hvm-intel pass test-amd64-amd64-libvirt pass test-armhf-armhf-libvirt pass test-amd64-i386-libvirt pass test-amd64-amd64-livepatch pass test-amd64-i386-livepatch pass test-amd64-amd64-migrupgrade fail test-amd64-i386-migrupgrade pass test-amd64-amd64-xl-multivcpu pass test-armhf-armhf-xl-multivcpu pass test-amd64-amd64-pair fail test-amd64-i386-pair pass test-amd64-amd64-libvirt-pair fail test-amd64-i386-libvirt-pair pass test-amd64-amd64-amd64-pvgrub pass test-amd64-amd64-i386-pvgrub pass test-amd64-amd64-pygrub pass test-amd64-amd64-xl-qcow2 fail test-armhf-armhf-libvirt-raw pass test-amd64-i386-xl-raw pass test-amd64-amd64-xl-rtds pass test-armhf-armhf-xl-rtds pass test-amd64-amd64-xl-qemuu-debianhvm-amd64-shadow pass test-amd64-i386-xl-qemuu-debianhvm-amd64-shadow pass test-amd64-amd64-xl-shadow pass test-amd64-i386-xl-shadow pass test-amd64-amd64-libvirt-vhd pass test-armhf-armhf-xl-vhd 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 aa6978c2688f28e5fc55c960bbfe5e64f9105f84 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Fri May 3 11:09:12 2019 +0200 x86/spec-ctrl: Extend repoline safey calcuations for eIBRS and Atom parts All currently-released Atom processors are in practice retpoline-safe, because they don't fall back to a BTB prediction on RSB underflow. However, an additional meaning of Enhanced IRBS is that the processor may not be retpoline-safe. The Gemini Lake platform, based on the Goldmont Plus microarchitecture is the first Atom processor to support eIBRS. Until Xen gets full eIBRS support, Gemini Lake will still be safe using regular IBRS. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Acked-by: Jan Beulich <jbeulich@xxxxxxxx> master commit: 17f74242ccf0ce6e51c03a5860947865c0ef0dc2 master date: 2019-03-18 16:26:40 +0000 commit 923d4e8736ec60b6e0da9f496b71bc68e7783756 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Fri May 3 11:08:26 2019 +0200 x86/msr: Shorten ARCH_CAPABILITIES_* constants They are unnecesserily verbose, and ARCH_CAPS_* is already the more common version. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Acked-by: Jan Beulich <jbeulich@xxxxxxxx> master commit: ba27aaa88548c824a47dcf5609288ee1c05d2946 master date: 2019-03-18 16:26:40 +0000 commit 7ddfc2af158ff4c96792cf7d072908b232f0c8fb Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Fri May 3 11:07:35 2019 +0200 x86/e820: fix build with gcc9 e820.c: In function ‘clip_to_limit’: .../xen/include/asm/string.h:10:26: error: ‘__builtin_memmove’ offset [-16, -36] is out of the bounds [0, 20484] of object ‘e820’ with type ‘struct e820map’ [-Werror=array-bounds] 10 | #define memmove(d, s, n) __builtin_memmove(d, s, n) | ^~~~~~~~~~~~~~~~~~~~~~~~~~ e820.c:404:13: note: in expansion of macro ‘memmove’ 404 | memmove(&e820.map[i], &e820.map[i+1], | ^~~~~~~ e820.c:36:16: note: ‘e820’ declared here 36 | struct e820map e820; | ^~~~ While I can't see where the negative offsets would come from, converting the loop index to unsigned type helps. Take the opportunity and also convert several other local variables and copy_e820_map()'s second parameter to unsigned int (and bool in one case). Reported-by: Charles Arnold <carnold@xxxxxxxx> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Roger Pau Monné <roger.pau@xxxxxxxxxx> Reviewed-by: Wei Liu <wei.liu2@xxxxxxxxxx> Acked-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: 22e2f8dddf5fbed885b5e4db3ffc9e1101be9ec0 master date: 2019-03-18 11:38:36 +0100 commit f72572115b58b824b5e081681a2fde66e0bc5b21 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Fri May 3 11:06:38 2019 +0200 x86/pv: Fix construction of 32bit dom0's dom0_construct_pv() has logic to transition dom0 into a compat domain when booting an ELF32 image. One aspect which is missing is the CPUID policy recalculation, meaning that a 32bit dom0 sees a 64bit policy, which differ by the Long Mode feature flag in particular. Another missing item is the x87_fip_width initialisation. Update dom0_construct_pv() to use switch_compat(), rather than retaining the opencoding. Position the call to switch_compat() such that the compat32 local variable can disappear entirely. The 32bit monitor table is now created by setup_compat_l4(), avoiding the need to for manual creation later. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Signed-off-by: Wei Liu <wei.liu2@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> master commit: 356f437171c5bb90701ac9dd7ba4dbbd05988e38 master date: 2019-03-15 14:59:27 +0000 commit 7dfea782b83684d4b69d88b36a83bed0c34478cf Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Fri May 3 11:05:56 2019 +0200 x86/tsx: Implement controls for RTM force-abort mode The CPUID bit and MSR are deliberately not exposed to guests, because they won't exist on newer processors. As vPMU isn't security supported, the misbehaviour of PCR3 isn't expected to impact production deployments. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> master commit: 6be613f29b4205349275d24367bd4c82fb2960dd master date: 2019-03-12 17:05:21 +0000 commit f0c5805b64767563abb558ff7e7640ced1114a0d Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Fri May 3 11:05:05 2019 +0200 x86/vtd: Don't include control register state in the table pointers iremap_maddr and qinval_maddr point to the base of a block of contiguous RAM, allocated by the driver, holding the Interrupt Remapping table, and the Queued Invalidation ring. Despite their name, they are actually the values of the hardware register, including control metadata in the lower 12 bits. While uses of these fields do appear to correctly shift out the metadata, this is very subtle behaviour and confusing to follow. Nothing uses the metadata, so make the fields actually point at the base of the relevant tables. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Kevin Tian <kevin.tian@xxxxxxxxx> master commit: a9a05aeee10a5a3763a41305a9f38112dd1fcc82 master date: 2019-03-12 13:57:13 +0000 commit 3f5490d7e442db3dc65d784ee3c087f7e41f5a06 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Fri May 3 11:04:32 2019 +0200 x86/HVM: don't crash guest in hvmemul_find_mmio_cache() Commit 35a61c05ea ("x86emul: adjust handling of AVX2 gathers") builds upon the fact that the domain will actually survive running out of MMIO result buffer space. Drop the domain_crash() invocation. Also delay incrementing of the usage counter, such that the function can't possibly use/return an out-of-bounds slot/pointer in case execution subsequently makes it into the function again without a prior reset of state. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Paul Durrant <paul.durrant@xxxxxxxxxx> master commit: a43c1dec246bdee484e6a3de001cc6850a107abe master date: 2019-03-12 14:39:46 +0100 commit d06f5613e5df529f3e6aea94d648a3c62e65a403 Author: Igor Druzhinin <igor.druzhinin@xxxxxxxxxx> Date: Fri May 3 11:03:52 2019 +0200 iommu: leave IOMMU enabled by default during kexec crash transition It's unsafe to disable IOMMU on a live system which is the case if we're crashing since remapping hardware doesn't usually know what to do with ongoing bus transactions and frequently raises NMI/MCE/SMI, etc. (depends on the firmware configuration) to signal these abnormalities. This, in turn, doesn't play well with kexec transition process as there is no handling available at the moment for this kind of events resulting in failures to enter the kernel. Modern Linux kernels taught to copy all the necessary DMAR/IR tables following kexec from the previous kernel (Xen in our case) - so it's currently normal to keep IOMMU enabled. It might require minor changes to kdump command line that enables IOMMU drivers (e.g. intel_iommu=on / intremap=on) but recent kernels don't require any additional changes for the transition to be transparent. A fallback option is still left for compatibility with ancient crash kernels which didn't like to have IOMMU active under their feet on boot. Signed-off-by: Igor Druzhinin <igor.druzhinin@xxxxxxxxxx> Acked-by: Jan Beulich <jbeulich@xxxxxxxx> master commit: 12c36f577d454996c882ecdc5da8113ca2613646 master date: 2019-03-12 14:38:12 +0100 commit 92fc0b635ca87459ef4582bb8f1663b14a097be4 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Fri May 3 11:03:01 2019 +0200 x86/vmx: Properly flush the TLB when an altp2m is modified Modifications to an altp2m mark the p2m as needing flushing, but this was never wired up in the return-to-guest path. As a result, stale TLB entries can remain after resuming the guest. In practice, this manifests as a missing EPT_VIOLATION or #VE exception when the guest subsequently accesses a page which has had its permissions reduced. vmx_vmenter_helper() now has 11 p2ms to potentially invalidate, but issuing 11 INVEPT instructions isn't clever. Instead, count how many contexts need invalidating, and use INVEPT_ALL_CONTEXT if two or more are in need of flushing. This doesn't have an XSA because altp2m is not yet a security-supported feature. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Kevin Tian <kevin.tian@xxxxxxxxx> master commit: 69f7643df68ef8e994221a996e336a47cbb7bbc8 master date: 2019-02-28 11:16:27 +0000 commit b8071f348bf49df976aeede158fa6a8618b9540f Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Fri May 3 11:02:17 2019 +0200 x86/cpuid: add missing PCLMULQDQ dependency Since we can't seem to be able to settle our discussion for the wider adjustment previously posted, let's at least add the missing dependency for 4.12. I'm not convinced though that attaching it to SSE is correct. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: eeb31ee522c7bb8541eb4c037be2c42bfcf0a3c3 master date: 2019-03-05 18:04:23 +0100 commit 5200791dfbe0af2f49a9c0226520c2aef0413d5a Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Fri May 3 11:01:24 2019 +0200 x86/mm: fix #GP(0) in switch_cr3_cr4() With "pcid=no-xpti" and opposite XPTI settings in two 64-bit PV domains (achievable with one of "xpti=no-dom0" or "xpti=no-domu"), switching from a PCID-disabled to a PCID-enabled 64-bit PV domain fails to set CR4.PCIDE in time, as CR4.PGE would not be set in either (see pv_fixup_guest_cr4(), in particular as used by write_ptbase()), and hence the early CR4 write would be skipped. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: fdc2056767ba74346dfd8bbe868bb22521ba1418 master date: 2019-03-05 17:02:36 +0100 commit 3b0eebb1ca6e158d7b9a5e57d68ddb4093882822 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Fri May 3 10:59:18 2019 +0200 xen: Fix backport of "xen/cmdline: Fix buggy strncmp(s, LITERAL, ss - s) construct" These were missed as a consequence of being rebased over other cmdline cleanup. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> (qemu changes not included) _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |