|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [xen-unstable test] 104175: regressions - FAIL
flight 104175 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/104175/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-xl 15 guest-start/debian.repeat fail REGR. vs. 104170 Regressions which are regarded as allowable (not blocking): test-armhf-armhf-xl-rtds 15 guest-start/debian.repeat fail like 104162 test-armhf-armhf-libvirt 13 saverestore-support-check fail like 104170 test-armhf-armhf-libvirt-xsm 13 saverestore-support-check fail like 104170 test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop fail like 104170 test-amd64-i386-xl-qemut-win7-amd64 16 guest-stop fail like 104170 test-amd64-amd64-xl-qemut-win7-amd64 16 guest-stop fail like 104170 test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail like 104170 test-armhf-armhf-libvirt-qcow2 12 saverestore-support-check fail like 104170 test-armhf-armhf-libvirt-raw 12 saverestore-support-check fail like 104170 test-amd64-amd64-xl-rtds 9 debian-install fail like 104170 Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-pvh-amd 11 guest-start fail never pass test-amd64-amd64-xl-pvh-intel 11 guest-start fail never pass test-amd64-i386-libvirt 12 migrate-support-check fail never pass test-amd64-i386-libvirt-xsm 12 migrate-support-check fail never pass test-amd64-amd64-libvirt-xsm 12 migrate-support-check fail never pass test-amd64-amd64-libvirt 12 migrate-support-check fail never pass test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check fail never pass test-amd64-amd64-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-amd64-amd64-libvirt-vhd 11 migrate-support-check fail never pass test-amd64-amd64-qemuu-nested-amd 16 debian-hvm-install/l1/l2 fail never pass test-armhf-armhf-xl-xsm 12 migrate-support-check fail never pass test-armhf-armhf-xl-credit2 12 migrate-support-check fail never pass test-armhf-armhf-xl-xsm 13 saverestore-support-check fail never pass test-armhf-armhf-xl-cubietruck 12 migrate-support-check fail never pass test-armhf-armhf-xl-credit2 13 saverestore-support-check fail never pass test-armhf-armhf-xl-cubietruck 13 saverestore-support-check fail never pass test-armhf-armhf-libvirt 12 migrate-support-check fail never pass test-armhf-armhf-libvirt-xsm 12 migrate-support-check fail never pass test-armhf-armhf-libvirt-qcow2 11 migrate-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-xl-multivcpu 12 migrate-support-check fail never pass test-armhf-armhf-xl-multivcpu 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-rtds 12 migrate-support-check fail never pass test-armhf-armhf-xl-rtds 13 saverestore-support-check fail never pass test-armhf-armhf-libvirt-raw 11 migrate-support-check fail never pass version targeted for testing: xen 98be5ffc05e689e2131f175ed95b011a7270db67 baseline version: xen 904f9314540bcfbcfa60245e8f41ff1b671cdd9a Last test of basis 104170 2017-01-13 14:14:44 Z 0 days Testing same since 104175 2017-01-13 22:46:14 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> Juergen Gross <jgross@xxxxxxxx> Wei Liu <wei.liu2@xxxxxxxxxx> 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-oldkern pass build-i386-oldkern 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 fail 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 pass 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 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-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 98be5ffc05e689e2131f175ed95b011a7270db67 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Fri Jan 13 15:28:31 2017 +0100 x86emul: improve CR/DR access handling - don't accept LOCK for DR accesses (it's undefined in the manuals) - only accept LOCK for CR accesses when the respective feature flag is set (which would not normally be the case for Intel) - add (rather than or) 8 when LOCK is present; real hardware #UDs when both REX.W and LOCK are present, implying that these would rather access hypothetical CR16...23 - eliminate explicit decode_register() calls - streamline remaining read/write code No further functional change, i.e. not addressing the missing exception generation (#UD for invalid CR/DR encodings, #GP(0) for invalid write values, #DB for DR accesses with DR7.GD set). Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> commit 199b1eaa79c0f828dab8598c5ba164efa7edac1a Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Fri Jan 13 15:27:53 2017 +0100 x86emul: use switch()-wide local variable 'cr4' ... rather than various smaller scope ones. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> commit c437fa17290934ddf347f65d09b83d7fc0eaef84 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Fri Jan 13 15:25:52 2017 +0100 x86emul: support VME and PVI ... affecting PUSHF, POPF, CLI, and STI. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> commit cb2626c75813be4267b5bc1515e34145ce55f2d5 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Fri Jan 13 15:24:45 2017 +0100 x86emul: conditionally clear BNDn for branches Considering that we surface MPX to HVM guests, instructions we emulate should also correctly deal with MPX state. While for now BND* instructions don't get emulated, the effect of branches (which we do emulate) without BND prefix should be taken care of. No need to alter XABORT behavior: While not mentioned in the SDM so far, this restores BNDn as they were at the XBEGIN, and since we make XBEGIN abort right away, XABORT in the emulator is only a no-op. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> commit 37814513bc9dcd46d084d5713eee7f8d6f7f870f Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Wed Jan 4 13:31:53 2017 +0000 x86/cpuid: Move the legacy cpuids array into struct cpuid_policy This hides the legacy details inside the cpuid subsystem, where they will eventually be dropped entirely. While altering the line containing paging_initialised, change its type to bool to match its use. No functional change. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit d1bc8380e508a0dc4d5d30de05e4e7c082e39893 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Wed Jan 4 12:46:09 2017 +0000 x86/cpuid: Effectively remove domain_cpuid() The only callers of domain_cpuid() are the legacy cpuid path via {pv,hvm}_cpuid(). Move domain_cpuid() to being private in cpuid.c, with an adjusted API to use struct cpuid_leaf rather than individual pointers. The ITSC clobbering logic is dropped. It is no longer necessary now that the logic has moved into recalculate_cpuid_policy() Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit 9db5d75c91dba258a6e834b730d6e13263dcc271 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Wed Jan 4 12:20:51 2017 +0000 x86/cpuid: Store the toolstacks choice of hypervisor max leaf This removes all dependencies on the legacy cpuids[] array from cpuid_hypervisor_leaves(). Swap a BUG() to an ASSERT_UNREACHABLE(), because in the unlikely case that we hit it, returning all zeros to the guest is fine. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit 07097cc0c6bdb08873ae627ca0f36e593be1d7c0 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Wed Jan 4 12:43:57 2017 +0000 x86/domctl: Move all CPUID update logic into update_domain_cpuid_info() This simplifies the XEN_DOMCTL_set_cpuid handling, splitting the safety logic away from the internals of how an update is completed. The legacy cpuids[] logic is left in alone in a fuction, as it wont survive very long. update_domain_cpuid_info() gains a small performance optimisation to skip all update activites for leaves which won't have any impact on the guest. This is temporary until the new hypercall API is completed. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit 38b1c3a5affbe3451f366576aef9c7149d62de04 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Thu Jan 12 16:14:56 2017 +0000 x86/cpuid: Fix feature flags reported to dom0 c/s a11e8c9 "x86/pv: Use per-domain policy information in pv_cpuid()" switched PV domains from using a (hardware for dom0, toolstack-chosen from domU) value masked against pv_featureset[], to actually using the value calculated by recalculate_cpuid_policy(). For domU, this is no practical change as the content is still chosen by the toolstack. For dom0 however, we no longer have two sources of information potentially clearing bits. Modern Linux seems to care about having CMP_LEGACY set in its view of CPUID on an Intel box. The deliberate setting of HTT, X2APIC and CMP_LEGACY in {pv,hvm}_featureset[] is necessary for domUs, as the toolstack may have (tried to) set up topology information in a different representation than the hardware uses. The bits therefore needed to be set in the masks used in the older logic, to avoid clobbering the toolstacks information. Move the HTT/X2APIC/CMP_LEGACY logic from calculate_{pv,hvm}_max_policy() (where the meaning of {pv,hvm}_featureset[] has changed subtly) to recalculate_cpuid_policy() where the masking logic now lives. This will cause {pv,hvm}_max_policy to actually contain real hardware values (so dom0 sees real hardware values), but still allows the toolstack to set bits not present in real hardware for domUs. Reported-by: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx> Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Tested-by: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit 2704c78aaa156e6843681ee344dd0ce75dbc63b2 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Wed Jan 11 17:51:44 2017 +0000 x86/sysctl: Fix NULL pointer dereference in error path This was introduced by c/s c38869e711 "x86/cpuid: Drop the temporary linear feature bitmap from struct cpuid_policy", and caught by Coverity. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> commit 2ef6ace428dec4795b8b0a67fff6949e817013de Author: Juergen Gross <jgross@xxxxxxxx> Date: Tue Jan 10 17:13:39 2017 +0100 tools: don't remove tdb data base file before starting xenstored As xenstored now is always starting with an empty tdb data base there is no need any longer to remove the file before starting xenstored. Signed-off-by: Juergen Gross <jgross@xxxxxxxx> Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx> commit 388d3011d1bbc926df61aabd101208d6134d3eb5 Author: Juergen Gross <jgross@xxxxxxxx> Date: Tue Jan 10 17:13:38 2017 +0100 tools/xenstore: start with empty data base Today xenstored tries to open a tdb data base file on disk when it is started. As this is problematic in most cases the scripts used to start xenstored ensure xenstored won't find such a file in order to start with an empty xenstore. A tdb data base file can't be used to restore all Xenstore state as e.g. Xenstore watches are not kept in the tdb data base. The file is meant to be used for debugging purposes after a xenstored crash only. Instead of opening a Xenstore data base file found on disk always start with an empty data base. This will avoid problems in case someone is testing multiple xenstored versions without rebooting (which is not supported but helps debugging in some cases). Signed-off-by: Juergen Gross <jgross@xxxxxxxx> Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx> (qemu changes not included) _______________________________________________ osstest-output mailing list osstest-output@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/cgi-bin/mailman/listinfo/osstest-output
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |