|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [xen-4.8-testing test] 104247: regressions - FAIL
flight 104247 xen-4.8-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/104247/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-freebsd10-amd64 10 guest-start fail REGR. vs. 104031 test-armhf-armhf-libvirt-xsm 6 xen-boot fail REGR. vs. 104031 Regressions which are regarded as allowable (not blocking): test-armhf-armhf-xl-rtds 15 guest-start/debian.repeat fail REGR. vs. 104031 test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop fail like 104031 test-amd64-amd64-xl-qemut-win7-amd64 16 guest-stop fail like 104031 test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail like 104031 test-amd64-i386-xl-qemut-win7-amd64 16 guest-stop fail like 104031 test-amd64-amd64-xl-rtds 9 debian-install fail like 104031 Tests which did not succeed, but are not blocking: test-amd64-i386-libvirt-xsm 12 migrate-support-check fail never pass test-amd64-amd64-xl-pvh-intel 11 guest-start fail never pass test-amd64-amd64-libvirt 12 migrate-support-check fail never pass test-amd64-i386-libvirt 12 migrate-support-check fail never pass test-amd64-amd64-libvirt-xsm 12 migrate-support-check fail never pass test-amd64-amd64-xl-pvh-amd 11 guest-start 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-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 12 migrate-support-check fail never pass test-armhf-armhf-xl-credit2 13 saverestore-support-check fail never pass test-amd64-amd64-libvirt-vhd 11 migrate-support-check fail never pass test-armhf-armhf-xl-multivcpu 12 migrate-support-check fail never pass test-armhf-armhf-xl-multivcpu 13 saverestore-support-check fail never pass test-amd64-amd64-qemuu-nested-amd 16 debian-hvm-install/l1/l2 fail never pass test-armhf-armhf-libvirt-raw 11 migrate-support-check fail never pass test-armhf-armhf-libvirt-raw 12 saverestore-support-check fail never pass test-armhf-armhf-xl-xsm 12 migrate-support-check fail never pass test-armhf-armhf-xl-xsm 13 saverestore-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-armhf-armhf-xl-cubietruck 12 migrate-support-check fail never pass test-armhf-armhf-xl-cubietruck 13 saverestore-support-check fail never pass test-armhf-armhf-libvirt-qcow2 11 migrate-support-check fail never pass test-armhf-armhf-libvirt-qcow2 12 saverestore-support-check fail never pass test-armhf-armhf-xl-rtds 12 migrate-support-check fail never pass test-armhf-armhf-xl-rtds 13 saverestore-support-check 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 test-armhf-armhf-libvirt 12 migrate-support-check fail never pass test-armhf-armhf-libvirt 13 saverestore-support-check fail never pass version targeted for testing: xen daf491dc1e87fe32b35f2ae75b4add0fa96c0d7f baseline version: xen c5efe958ca4b86779dc7564bf2682f3df71202e7 Last test of basis 104031 2017-01-04 17:44:27 Z 13 days Testing same since 104247 2017-01-18 09:07:15 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> Kevin Tian <kevin.tian@xxxxxxxxx> Luwei Kang <luwei.kang@xxxxxxxxx> Paul Durrant <paul.durrant@xxxxxxxxxx> Zhang Chen <zhangchen.fnst@xxxxxxxxxxxxxx> jobs: build-amd64-xsm pass build-armhf-xsm pass build-i386-xsm pass build-amd64-xtf 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-rumprun pass build-i386-rumprun 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-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 pass 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 fail test-amd64-amd64-xl-qemuu-ovmf-amd64 pass test-amd64-i386-xl-qemuu-ovmf-amd64 pass test-amd64-amd64-rumprun-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-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-rumprun-i386 pass 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 pass 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 pass test-amd64-amd64-xl-qcow2 pass test-armhf-armhf-libvirt-raw pass test-amd64-i386-xl-raw pass test-amd64-amd64-xl-rtds fail 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 daf491dc1e87fe32b35f2ae75b4add0fa96c0d7f Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Wed Jan 18 09:52:19 2017 +0100 x86/cpu: Don't update this_cpu for get_cpu_vendor(, gcv_guest) Otherwise booting a cross-vendor guest would cause PCPU hotplug to malfunction, because of trying to use the wrong CPU driver. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> master commit: 291dcb4dd0140fac0e439760b4d51b2892ff9264 master date: 2017-01-03 13:33:16 +0000 commit a6542288d3a3803dfe683c62e7692b7dcd679402 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Wed Jan 18 09:51:53 2017 +0100 x86/emul: Correct the return value handling of VMFUNC The bracketing of x86_emulate() calling the ops->vmfunc() hook is wrong with respect to the assignment to rc, which can trip the new assertions in x86_emulate_wrapper(). The hvmemul_vmfunc() hook should only raise #UD if X86EMUL_EXCEPTION is returned. This is only a latent bug at the moment. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> master commit: 3ab1876504d409689824e161a8b04e57e1e5dd46 master date: 2016-12-22 13:32:46 +0000 commit c581eadec6cdaebb139993390bb9d1e22b2f77d9 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Wed Jan 18 09:49:55 2017 +0100 x86/boot: fix build with certain older gcc versions Despite all attempts so far (ending in commit fecf584294 ["Config.mk: fix comment for debug option"] adjusting the respective comment), Config.mk's debug= setting still affects the hypervisor build: CFLAGS gets -g added there. xen/arch/x86/boot/build32.mk includes that file, and hence inherits the setting too. Some gcc versions take -g to create an .eh_frame section despite -fno-asynchronous-unwind-tables (which instead one would expect to produce .debug_frame). In turn, commit 93c0c0287a ("x86/boot: create *.lnk files with linker script") was - in my understanding - supposed to make sure .text is first, but apparently it did also not really achieve that effect: Both reloc.lnk and reloc.bin in the case here ended up with .eh_frame first, which obviously rendered the whole final binary unusable. Explicitly suppress generation of any kind of debug info when building reloc.o. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: 620b3c7eee78e90167f591877177c922ae619b92 master date: 2016-12-16 14:37:35 +0100 commit 67e96796f438484cbe0e5829a42b107bdcabd5b9 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Wed Jan 18 09:49:26 2017 +0100 x86emul: CMPXCHG16B requires an aligned operand This distinguishes it from CMPXCHG8B. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: d7d3a82c28a1102ee6c9707071a946164bae0d57 master date: 2016-12-16 14:37:11 +0100 commit 080a31b6f95e17e3624b8f716653a6e9009912d6 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Wed Jan 18 09:48:57 2017 +0100 VT-d: correct dma_msi_set_affinity() Commit 83cd2038fe ("VT-d: use msi_compose_msg()) together with 15aa6c6748 ("amd iommu: use base platform MSI implementation"), introducing the use of a per-CPU scratch CPU mask, went too far: dma_msi_set_affinity() may, at least in theory, be called in interrupt context, and hence the use of that scratch variable is not correct. Since the function overwrites the destination information anyway, allow msi_compose_msg() to be called with a NULL CPU mask, avoiding the use of that scratch variable. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Kevin Tian <kevin.tian@xxxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: 7f885a1f49a75c770360b030666a5c1545156e5c master date: 2016-12-16 14:33:43 +0100 commit 1febe8da7709dbb30e0818b2f523ebc2c57e27b9 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Wed Jan 18 09:48:23 2017 +0100 x86emul: ignore most segment bases for 64-bit mode in is_aligned() ops->read_segment() will report whatever is actually there in the register, so we need to actively distinguish ES/CS/SS/DS from FS/GS. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: 6e616a3cef4d782253787904bf3d641112eafa14 master date: 2016-12-15 11:13:32 +0100 commit 7713ee2ad78800df484cb0434f59f134c5303d7a Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Wed Jan 18 09:47:31 2017 +0100 x86emul: MOVNTI does not allow REP prefixes Just like 66, prefixes F3 and F2 cause #UD. Also adjust a related comment, which in its previous wording was misleading (as in 16-bit mode there would nothing be undone when adjusting operand size from 2 to 4). Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: 96a7cb37b921d2b320183d194d143262e1dd5b53 master date: 2016-12-14 10:11:08 +0100 commit b76a79657cc00ee53db836bab241ebead7bbde55 Author: Luwei Kang <luwei.kang@xxxxxxxxx> Date: Wed Jan 18 09:46:54 2017 +0100 x86/VPMU: clear the overflow status of which counter happened to overflow Just set the corresponding bits of counters which happened to overflow, rather than setting all the available bits of IA32_PERF_GLOBAL_OVF_CTRL when pmu interrupt happened. Signed-off-by: Luwei Kang <luwei.kang@xxxxxxxxx> Acked-by: Kevin Tian <kevin.tian@xxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> master commit: 7a0c70482580234868fcc53b8d72e31966dc7c52 master date: 2016-12-13 14:21:26 +0100 commit e298344e4a43ce72999cb7efaa0132d0077da08d Author: Paul Durrant <paul.durrant@xxxxxxxxxx> Date: Wed Jan 18 09:46:26 2017 +0100 x86/hvm: don't unconditionally create a default ioreq server Avoid doing so if the domain is not under construction. If upstream QEMU is in use then it will explicitly create an ioreq server rather than implicitly creating the default ioreq server, which is a side-effect of reading HVM_PARAM_IOREQ_PFN, HVM_PARAM_BUFIOREQ_PFN, or HVM_PARAM_BUFIOREQ_EVTCHN (as is done by legacy QEMUs). However, if the domain is subsequently saved/migrated then those parameters are read and hence the default server will be unnecessarily instantiated. This patch adds an extra check of the 'creation_finished' flag when those HVM params are read and will only instantiate the server if the domain is under construction, which will always be the case when QEMU is invoked. Signed-off-by: Paul Durrant <paul.durrant@xxxxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Tested-by: Zhang Chen <zhangchen.fnst@xxxxxxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> x86/hvm: Fix HVMOP_get_param when skipping creating the default ioreq server c/s e7dabe5 "x86/hvm: don't unconditionally create a default ioreq server" added a break statement, but the logic previously depended on falling through into the default case to fill in the value the caller asked for. This causes the sending migration code to put a junk PARAM into the stream, and the receiving side to fail to zero the IOREQ pages, causing QEMU to object when it finds stale requests while starting up. Reorder the code so it more clearly falls through into the default case. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Paul Durrant <paul.durrant@xxxxxxxxxx> master commit: e7dabe59c3239dc9ef9edbc49ed54f754616ebf7 master date: 2016-12-12 09:49:10 +0100 master commit: 451c9938c68ccb77ff94765f7ac47e8de51d3f43 master date: 2016-12-13 09:58:33 +0000 commit 6933092cbd6a338e0675b667bc4ed862ffdb8722 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Wed Jan 18 09:45:54 2017 +0100 libelf: section index 0 is special When iterating over sections, table entry zero needs to be ignored. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx> Reviewed-by: Roger Pau Monné <roger.pau@xxxxxxxxxx> master commit: 41fe9cabf29ea15c1f8edee49326dfde705013d3 master date: 2016-12-07 13:52:35 +0100 commit af6534e8d40308cd52d46e84169c4563808a8958 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Wed Jan 18 09:44:49 2017 +0100 x86emul: CMPXCHG{8,16}B ignore prefixes This removes 0F C7 from the list of two-byte opcodes treating prefixes 66, F3, and F2 as opcode extensions. We better manually handle this in the opcode specific code: - CMPXCHG8B ignores all these prefixes (its handling is being adjusted accordingly, with a respective test case added as well, to avoid re-introducing the subject of XSA-200), - RDRAND/RDSEED (support to be added subsequently) honor 66, but treat F3 and F2 as opcode extensions (resolving to RDPID in the RDSEED case, which in turn ignores 66). Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: 54abe826c8297e12f805be2bcf318ef75cc7f58d master date: 2016-12-14 10:08:22 +0100 commit 297cf3d1cf998d2fbc8e63e92034ce08f60c3b60 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Wed Jan 18 09:43:47 2017 +0100 xen: Fix determining when domain creation is complete d->creation_finished is used in several places alter behaviour depending on whether the domain is being created, or is already running. However, there is a latent bug if a toolstack component makes a pair of pause/unpause calls, where creation will be considered finished prematurely. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> Tested-by: Paul Durrant <paul.durrant@xxxxxxxxxx> master commit: 9d71e02e8420b5d4a48d92446a1edbff498ee1c6 master date: 2016-12-13 09:58:33 +0000 commit 3e902dd55eba8f2668502b88f1220c25dcc5fb40 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Wed Jan 18 09:43:00 2017 +0100 x86emul: correct PUSHF/POPF Both need to raise #GP(0) when in VM86 mode with IOPL < 3. Additionally PUSHF is documented to clear VM and RF from the value placed onto the stack. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: e5c1b8145bccb7fc587ee5b0c95ace6c5e0c7ffd master date: 2016-12-07 13:55:42 +0100 (qemu changes not included) _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx https://lists.xen.org/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |