|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [xen-4.9-testing test] 122386: trouble: blocked/broken/fail/pass
flight 122386 xen-4.9-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/122386/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf <job status> broken test-amd64-i386-xl-qemuu-debianhvm-amd64 <job status> broken test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm <job status> broken build-armhf 4 host-install(4) broken REGR. vs. 121761 Tests which are failing intermittently (not blocking): test-amd64-i386-xl-qemuu-debianhvm-amd64 4 host-install(4) broken pass in 122355 test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm 4 host-install(4) broken pass in 122355 test-amd64-amd64-xl-qemut-ws16-amd64 16 guest-localmigrate/x10 fail in 122355 pass in 122386 test-amd64-i386-xl-qemut-win7-amd64 16 guest-localmigrate/x10 fail in 122355 pass in 122386 test-amd64-amd64-xl-qemuu-debianhvm-amd64 16 guest-localmigrate/x10 fail pass in 122355 test-amd64-i386-xl-qemut-ws16-amd64 14 guest-localmigrate fail pass in 122355 Tests which did not succeed, but are not blocking: test-armhf-armhf-libvirt-xsm 1 build-check(1) blocked n/a test-armhf-armhf-xl-vhd 1 build-check(1) blocked n/a test-armhf-armhf-xl-credit2 1 build-check(1) blocked n/a test-armhf-armhf-libvirt 1 build-check(1) blocked n/a build-armhf-libvirt 1 build-check(1) blocked n/a test-armhf-armhf-libvirt-raw 1 build-check(1) blocked n/a test-armhf-armhf-xl-multivcpu 1 build-check(1) blocked n/a test-armhf-armhf-xl-cubietruck 1 build-check(1) blocked n/a test-armhf-armhf-xl 1 build-check(1) blocked n/a test-armhf-armhf-xl-rtds 1 build-check(1) blocked n/a test-armhf-armhf-xl-arndale 1 build-check(1) blocked n/a test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-localmigrate/x10 fail in 122355 like 121728 test-armhf-armhf-xl-rtds 16 guest-start/debian.repeat fail in 122355 like 121761 test-amd64-amd64-xl-qemut-win7-amd64 16 guest-localmigrate/x10 fail in 122355 like 121761 test-amd64-i386-xl-qemut-ws16-amd64 17 guest-stop fail in 122355 like 121761 test-amd64-i386-xl-qemuu-ws16-amd64 16 guest-localmigrate/x10 fail in 122355 like 121761 test-armhf-armhf-xl-arndale 13 migrate-support-check fail in 122355 never pass test-armhf-armhf-xl-arndale 14 saverestore-support-check fail in 122355 never pass test-armhf-armhf-libvirt-xsm 13 migrate-support-check fail in 122355 never pass test-armhf-armhf-libvirt-xsm 14 saverestore-support-check fail in 122355 never pass test-armhf-armhf-xl-multivcpu 13 migrate-support-check fail in 122355 never pass test-armhf-armhf-xl-multivcpu 14 saverestore-support-check fail in 122355 never pass test-armhf-armhf-xl-rtds 13 migrate-support-check fail in 122355 never pass test-armhf-armhf-xl-rtds 14 saverestore-support-check fail in 122355 never pass test-armhf-armhf-xl-cubietruck 13 migrate-support-check fail in 122355 never pass test-armhf-armhf-xl-cubietruck 14 saverestore-support-check fail in 122355 never pass test-armhf-armhf-libvirt-raw 12 migrate-support-check fail in 122355 never pass test-armhf-armhf-xl-credit2 13 migrate-support-check fail in 122355 never pass test-armhf-armhf-libvirt-raw 13 saverestore-support-check fail in 122355 never pass test-armhf-armhf-xl-credit2 14 saverestore-support-check fail in 122355 never pass test-armhf-armhf-xl 13 migrate-support-check fail in 122355 never pass test-armhf-armhf-xl 14 saverestore-support-check fail in 122355 never pass test-armhf-armhf-libvirt 13 migrate-support-check fail in 122355 never pass test-armhf-armhf-libvirt 14 saverestore-support-check fail in 122355 never pass test-armhf-armhf-xl-vhd 12 migrate-support-check fail in 122355 never pass test-armhf-armhf-xl-vhd 13 saverestore-support-check fail in 122355 never pass test-amd64-amd64-xl-qemuu-ws16-amd64 16 guest-localmigrate/x10 fail like 121704 test-amd64-i386-xl-qemuu-ws16-amd64 17 guest-stop fail like 121704 test-amd64-amd64-xl-qemut-win7-amd64 17 guest-stop fail like 121728 test-amd64-i386-xl-qemuu-win7-amd64 17 guest-stop fail like 121761 test-amd64-amd64-xl-qemuu-win7-amd64 17 guest-stop fail like 121761 test-amd64-amd64-xl-qemut-ws16-amd64 17 guest-stop fail like 121761 test-amd64-i386-xl-qemut-win7-amd64 17 guest-stop fail like 121761 test-amd64-amd64-libvirt 13 migrate-support-check fail never pass test-amd64-i386-libvirt-xsm 13 migrate-support-check 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-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-xl 13 migrate-support-check fail never pass test-arm64-arm64-libvirt-xsm 13 migrate-support-check fail never pass test-arm64-arm64-xl 14 saverestore-support-check fail never pass test-arm64-arm64-libvirt-xsm 14 saverestore-support-check fail never pass test-arm64-arm64-xl-credit2 13 migrate-support-check fail never pass test-arm64-arm64-xl-credit2 14 saverestore-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-amd64-amd64-qemuu-nested-amd 17 debian-hvm-install/l1/l2 fail never pass test-armhf-armhf-xl-xsm 13 migrate-support-check fail never pass test-armhf-armhf-xl-xsm 14 saverestore-support-check fail never pass test-amd64-amd64-xl-qemut-win10-i386 10 windows-install fail never pass test-amd64-i386-xl-qemuu-win10-i386 10 windows-install fail never pass test-amd64-i386-xl-qemut-win10-i386 10 windows-install fail never pass test-amd64-amd64-xl-qemuu-win10-i386 10 windows-install fail never pass version targeted for testing: xen 921bff4ea79c5b0d76274c3bb53b08ac4f3cfd55 baseline version: xen ad4fefdd088e47dcc017efefc4857e1610c832af Last test of basis 121761 2018-04-04 03:55:43 Z 21 days Testing same since 122355 2018-04-23 11:06:18 Z 2 days 2 attempts ------------------------------------------------------------ People who touched revisions under test: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> Juergen Gross <jgross@xxxxxxxx> Kevin Tian <kevin.tian@xxxxxxxxx> Wei Liu <wei.liu2@xxxxxxxxxx> jobs: build-amd64-xsm pass build-arm64-xsm pass build-armhf-xsm pass build-i386-xsm pass build-amd64-xtf pass build-amd64 pass build-arm64 pass build-armhf broken build-i386 pass build-amd64-libvirt pass build-arm64-libvirt pass build-armhf-libvirt blocked 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 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-arm64-arm64-xl pass test-armhf-armhf-xl blocked 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 broken 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-arm64-arm64-libvirt-xsm pass test-armhf-armhf-libvirt-xsm blocked test-amd64-i386-libvirt-xsm pass test-amd64-amd64-xl-xsm pass test-arm64-arm64-xl-xsm pass test-armhf-armhf-xl-xsm pass test-amd64-i386-xl-xsm pass test-amd64-amd64-qemuu-nested-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 fail test-amd64-i386-xl-qemuu-debianhvm-amd64 broken 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-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-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 blocked test-amd64-amd64-xl-credit2 pass test-arm64-arm64-xl-credit2 pass test-armhf-armhf-xl-credit2 blocked test-armhf-armhf-xl-cubietruck blocked test-amd64-i386-freebsd10-i386 pass test-amd64-i386-rumprun-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-i386-qemut-rhel6hvm-intel pass test-amd64-i386-qemuu-rhel6hvm-intel pass test-amd64-amd64-libvirt pass test-armhf-armhf-libvirt blocked test-amd64-i386-libvirt pass test-amd64-amd64-livepatch pass test-amd64-i386-livepatch pass test-amd64-amd64-migrupgrade pass test-amd64-i386-migrupgrade pass test-amd64-amd64-xl-multivcpu pass test-armhf-armhf-xl-multivcpu blocked 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-amd64-amd64-xl-qcow2 pass test-armhf-armhf-libvirt-raw blocked test-amd64-i386-xl-raw pass test-amd64-amd64-xl-rtds pass test-armhf-armhf-xl-rtds blocked 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 blocked ------------------------------------------------------------ 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 broken-job build-armhf broken broken-job test-amd64-i386-xl-qemuu-debianhvm-amd64 broken broken-job test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm broken broken-step test-amd64-i386-xl-qemuu-debianhvm-amd64 host-install(4) broken-step test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm host-install(4) broken-step build-armhf host-install(4) Not pushing. ------------------------------------------------------------ commit 921bff4ea79c5b0d76274c3bb53b08ac4f3cfd55 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Wed Apr 18 16:43:23 2018 +0200 x86/msr: Correct the emulation behaviour of MSR_PRED_CMD Experimentally, the behaviour of reserved bits in MSR_PRED_CMD changed between beta and production microcode, and now raises a #GP fault for set reserved bits. The AMD spec for future hardware also specifies this behaviour, and it is the more sensible behaviour to implement. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> x86/msr: further correct the emulation behaviour of MSR_PRED_CMD Following commit a6aa678fa3 ("x86/msr: Correct the emulation behaviour of MSR_PRED_CMD") we may end up writing the low bit with the wrong value. While it's unlikely for a guest to want to write zero there, we should still permit (this without incurring the overhead of an actual barrier). Correcting this right away will also help whenever further bits in the MSR might become defined. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: a6aa678fa380e9369cc44701a181142322b3a4b0 master date: 2018-04-16 13:18:19 +0100 master commit: a996273d1fc10d14598985703227bfa35a91f681 master date: 2018-04-18 11:16:37 +0200 commit c147505114c03fe14afa9ba6a6b436d7ee4b6835 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Wed Apr 18 16:42:49 2018 +0200 x86/VT-x: Fix determination of EFER.LMA in vmcs_dump_vcpu() The LMA setting comes from the entry controls. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Acked-by: Kevin Tian <kevin.tian@xxxxxxxxx> master commit: 82540b66ceb9318aa185f2488cbbbe479694de8f master date: 2018-04-11 11:06:55 +0100 commit dc527ffb2b2a1ce129e1dccc3e5eb4921c03def5 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Wed Apr 18 16:42:17 2018 +0200 x86/HVM: suppress I/O completion for port output We don't break up port requests in case they cross emulation entity boundaries, and a write to an I/O port is necessarily the last operation of an instruction instance, so there's no need to re-invoke the full emulation path upon receiving the result from an external emulator. In case we want to properly split port accesses in the future, this change will need to be reverted, as it would prevent things working correctly when e.g. the first part needs to go to an external emulator, while the second part is to be handled internally. While this addresses the reported problem of Windows paging out the buffer underneath an in-process REP OUTS, it does not address the wider problem of the re-issued insn (to the insn emulator) being prone to raise an exception (#PF) during a replayed, previously successful memory access (we only record prior MMIO accesses). Leaving aside the problem tried to be worked around here, I think the performance aspect alone is a good reason to change the behavior. Also take the opportunity and change bool_t -> bool as hvm_vcpu_io_need_completion()'s return type. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Paul Durrant <paul.durrant@xxxxxxxxxx> master commit: 91afb8139f954a06e564d4915bc7d6a8575e2812 master date: 2018-04-11 10:42:24 +0200 commit 781e23a4fca4a56ab8034300c7e7fb3210cf0973 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Wed Apr 18 16:41:47 2018 +0200 x86/pv: Fix up erroneous segments for 32bit syscall entry The existing FLAT_KERNEL_SS expands to the correct value, 0xe02b, but is the wrong constant to use. Switch to FLAT_USER_SS32. For compat domains however, the reported values are entirely bogus. FLAT_USER_SS32 (value 0xe02b) is FLAT_RING3_CS in the 32bit ABI, while FLAT_USER_CS32 (value 0xe023) is FLAT_RING1_DS with an RPL of 3. The guests SYSCALL callback is invoked with a broken iret frame, and if left unmodified by the guest, will fail on the way back out when Xen's iret tries to load a code segment into %ss. In practice, this is only a problem for 32bit PV guests on AMD hardware, as Intel hardware doesn't permit the SYSCALL instruction outside of 64bit mode. This appears to have been broken ever since 64bit support was added to Xen, and has gone unnoticed because Linux doesn't use SYSCALL in 32bit builds. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Wei Liu <wei.liu2@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> master commit: dba899de14989b3dff78009404ed891da7fefdc1 master date: 2018-04-09 13:12:18 +0100 commit 72ca5804d0d3297d527116aa1dc2b4f47f7079ee Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Wed Apr 18 16:41:16 2018 +0200 x86/XPTI: reduce .text.entry This exposes less code pieces and at the same time reduces the range covered from slightly above 3 pages to a little below 2 of them. The code being moved is unchanged, except for the removal of trailing blanks, insertion of blanks between operands, and a pointless q suffix from "retq". A few more small pieces could be moved, but it seems better to me to leave them where they are to not make it overly hard to follow code paths. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: 454efb2a31b64b98e3dd55c083ce41b87375faa6 master date: 2018-04-05 15:48:23 +0100 commit 47d41f6885a83fae09545146c97d5243f1b99c7a Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Wed Apr 18 16:40:50 2018 +0200 x86: log XPTI enabled status At the same time also report the state of the two defined ARCH_CAPABILITIES MSR bits. To avoid further complicating the conditional around that printk(), drop it (it's a debug level one only anyway). Issue the main message without any XENLOG_*, and also drop XENLOG_INFO from the respective BTI message, to make sure they're visible at default log level also in release builds. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Tested-by: Juergen Gross <jgross@xxxxxxxx> Reviewed-by: Juergen Gross <jgross@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Wei Liu <wei.liu2@xxxxxxxxxx> master commit: 442b303cdaf7d774c0be8096fe5dbab68701abd3 master date: 2018-04-05 15:48:23 +0100 commit 7a590155c572c9a10b1ec5a5c1cad662286eb3b2 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Wed Apr 18 16:40:14 2018 +0200 x86: disable XPTI when RDCL_NO Use the respective ARCH_CAPABILITIES MSR bit, but don't expose the MSR to guests yet. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Tested-by: Juergen Gross <jgross@xxxxxxxx> Reviewed-by: Juergen Gross <jgross@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx> master commit: bee0732d2066691d8204e418d10110930ee4d4f8 master date: 2018-04-05 15:48:23 +0100 commit 259bee90d11c17354501f91e1484494c8f31be86 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Wed Apr 18 16:39:38 2018 +0200 x86/pv: Fix the handing of writes to %dr7 c/s 65e35549 "x86/PV: support data breakpoint extension registers" accidentally broke the handing of writes. The call to activate_debugregs() doesn't write %dr7 as v->arch.debugreg[7] hasn't been updated yet, and the break skips the intended write to %dr7. Remove the break, causing execution to hit the write_debugreg(7, value); in context at the bottom of the hunk, which in turn causes hardware to be updated appropriately. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> master commit: adf8feba1afa040f3a84a82953e18af02060884a master date: 2018-03-29 15:12:21 +0100 commit 6d4c4f06467e3d126ca45c2e6b09a66a2a60a1ae Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Wed Apr 18 16:38:50 2018 +0200 x86/spec_ctrl: Fix several bugs in SPEC_CTRL_ENTRY_FROM_INTR_IST DO_OVERWRITE_RSB clobbers %rax, meaning in practice that the bti_ist_info field gets zeroed. Older versions of this code had the DO_OVERWRITE_RSB register selectable, so reintroduce this ability and use it to cause the INTR_IST path to use %rdx instead. The use of %dl for the %cs.rpl check means that when an IST interrupt hits Xen, we try to load 1 into the high 32 bits of MSR_SPEC_CTRL, suffering a #GP fault instead. Also, drop an unused label which was a copy/paste mistake. Reported-by: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx> Reported-by: Zhenzhong Duan <zhenzhong.duan@xxxxxxxxxx> Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Wei Liu <wei.liu2@xxxxxxxxxx> Reviewed-by: Roger Pau Monné <roger.pau@xxxxxxxxxx> master commit: a2b08fbed388f18235fda5ba1655c1483ef3e215 master date: 2018-02-14 13:22:15 +0000 commit 3e010f58748fb96202cc6c926688649ccff3321c Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Wed Apr 18 16:38:01 2018 +0200 update Xen version to 4.9.3-pre (qemu changes not included) _______________________________________________ osstest-output mailing list osstest-output@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/mailman/listinfo/osstest-output
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |