|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [Xen-devel] [xen-4.4-testing baseline-only test] 38534: regressions - FAIL
This run is configured for baseline tests only. flight 38534 xen-4.4-testing real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/38534/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-win7-amd64 15 guest-localmigrate/x10 fail REGR. vs. 38504 test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 15 guest-localmigrate/x10 fail REGR. vs. 38504 Regressions which are regarded as allowable (not blocking): test-amd64-i386-xl-qemuu-win7-amd64 13 guest-localmigrate fail REGR. vs. 38504 test-amd64-amd64-xl 19 guest-start/debian.repeat fail like 38504 Tests which did not succeed, but are not blocking: test-amd64-amd64-rumpuserxen-amd64 1 build-check(1) blocked n/a test-amd64-i386-rumpuserxen-i386 1 build-check(1) blocked n/a build-i386-rumpuserxen 6 xen-build fail never pass test-armhf-armhf-xl-vhd 9 debian-di-install fail never pass test-armhf-armhf-libvirt-qcow2 9 debian-di-install fail never pass test-armhf-armhf-libvirt-raw 9 debian-di-install fail never pass test-armhf-armhf-libvirt 11 guest-start fail never pass build-amd64-rumpuserxen 6 xen-build 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-armhf-armhf-xl-midway 12 migrate-support-check fail never pass test-armhf-armhf-xl-midway 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-xl 13 saverestore-support-check fail never pass test-armhf-armhf-xl 12 migrate-support-check fail never pass test-amd64-amd64-qemuu-nested-intel 16 debian-hvm-install/l1/l2 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-i386-xl-qemut-win7-amd64 16 guest-stop fail never pass test-amd64-amd64-xl-qemut-win7-amd64 16 guest-stop fail never pass test-amd64-amd64-libvirt-vhd 11 migrate-support-check fail never pass test-armhf-armhf-xl-multivcpu 13 saverestore-support-check fail never pass test-armhf-armhf-xl-multivcpu 12 migrate-support-check fail never pass test-amd64-i386-xend-qemut-winxpsp3 20 leak-check/check fail never pass version targeted for testing: xen d0b73c9bf21f9199401a36eeda7ba0a4412aad6d baseline version: xen 8fc45c1ce8ee883a9422ac471256c7c6125cef25 Last test of basis 38504 2015-12-12 05:24:44 Z 6 days Testing same since 38534 2015-12-18 10:53:38 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Daniel Kiper <daniel.kiper@xxxxxxxxxx> Dario Faggioli <dario.faggioli@xxxxxxxxxx> David Vrabel <david.vrabel@xxxxxxxxxx> Haozhong Zhang <haozhong.zhang@xxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> Kevin Tian <kevin.tian@xxxxxxxxx> 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-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-rumpuserxen fail build-i386-rumpuserxen fail test-amd64-amd64-xl fail test-armhf-armhf-xl pass test-amd64-i386-xl 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 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-rumpuserxen-amd64 blocked 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-credit2 pass test-armhf-armhf-xl-credit2 pass test-amd64-i386-freebsd10-i386 pass test-amd64-i386-rumpuserxen-i386 blocked test-amd64-amd64-qemuu-nested-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 fail test-amd64-i386-libvirt pass test-armhf-armhf-xl-midway 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-pv pass test-amd64-i386-pv pass test-amd64-amd64-amd64-pvgrub pass test-amd64-amd64-i386-pvgrub pass test-amd64-amd64-pygrub pass test-armhf-armhf-libvirt-qcow2 fail test-amd64-amd64-xl-qcow2 pass test-armhf-armhf-libvirt-raw fail test-amd64-i386-xl-raw pass test-amd64-i386-xl-qemut-winxpsp3-vcpus1 pass test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 fail test-amd64-amd64-libvirt-vhd pass test-armhf-armhf-xl-vhd fail test-amd64-i386-xend-qemut-winxpsp3 fail test-amd64-amd64-xl-qemut-winxpsp3 pass test-amd64-amd64-xl-qemuu-winxpsp3 pass ------------------------------------------------------------ sg-report-flight on osstest.xs.citrite.net logs: /home/osstest/logs images: /home/osstest/images Logs, config files, etc. are available at http://osstest.xs.citrite.net/~osstest/testlogs/logs Test harness code can be found at http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary Push not applicable. ------------------------------------------------------------ commit d0b73c9bf21f9199401a36eeda7ba0a4412aad6d Author: Haozhong Zhang <haozhong.zhang@xxxxxxxxx> Date: Tue Dec 15 15:56:02 2015 +0100 x86/time: fix domain type check in tsc_set_info() Replace is_hvm_domain() in tsc_set_info() by has_hvm_container_domain() to keep consistent with other domain type checks in tsc_set_info(). Signed-off-by: Haozhong Zhang <haozhong.zhang@xxxxxxxxx> Reviewed-by: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx> master commit: 3c80d6f3c61eb0f8072f70b0a9a8c8c7adf17572 master date: 2015-12-08 09:46:30 +0100 commit c3049fad2b01e85e944d928763f2b012eebf080e Author: David Vrabel <david.vrabel@xxxxxxxxxx> Date: Tue Dec 15 15:55:23 2015 +0100 evtchn: don't reuse ports that are still "busy" When using the FIFO ABI a guest may close an event channel that is still LINKED. If this port is reused, subsequent events may be lost because they may become pending on the wrong queue. This could be fixed by requiring guests to only close event channels that are not linked. This is difficult since: a) irq cleanup in the guest may be done in a context that cannot wait for the event to be unlinked; b) the guest may attempt to rebind a PIRQ whose previous close is still pending; and c) existing guests already have the problematic behaviour. Instead, simply check a port is not "busy" (i.e., it's not linked) before reusing it. Guests should still drain any queues for VCPUs that are being offlined, or the port will become unusable until the VCPU is onlined and starts processing events again. Signed-off-by: David Vrabel <david.vrabel@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> master commit: 78e24c269b0a4a8b864ece725e6d4209ed95dfa7 master date: 2015-12-02 15:21:46 +0100 commit 2f287a78df9192a4194b8146ed0e4661fdb92092 Author: Daniel Kiper <daniel.kiper@xxxxxxxxxx> Date: Tue Dec 15 15:55:00 2015 +0100 x86/boot: check for not allowed sections before linking Currently check for not allowed sections is performed just after compilation. However, if compilation succeeds and check fails then second build will create xen.gz/xen.efi without any visible error. This happens because %.o: %.c recipe created object file during first run and make do not execute this recipe during second run. So, look for not allowed sections before linking. This way check will be executed every time. Signed-off-by: Daniel Kiper <daniel.kiper@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> master commit: d380b3559734739ae009cd3c0e9aabb5602863e2 master date: 2015-11-25 17:24:36 +0100 commit f089991f9f1f580493d1bb72fb46a3b31a97d5f4 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Dec 15 15:53:49 2015 +0100 x86/vPMU: document as unsupported This is XSA-163. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> master commit: c03480cf5c4e96fb4afb2237ad0a3cac7162564a master date: 2015-11-24 18:32:20 +0100 commit f70eaf9f0784297831bea168d416b9c834d667db Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Dec 15 15:53:12 2015 +0100 VMX: fix/adjust trap injection In the course of investigating the 4.1.6 backport issue of the XSA-156 patch I realized that #DB injection has always been broken, but with it now getting always intercepted the problem has got worse: Documentation clearly states that neither DR7.GD nor DebugCtl.LBR get cleared before the intercept, so this is something we need to do before reflecting the intercepted exception. While adjusting this (and also with 4.1.6's strange use of X86_EVENTTYPE_SW_EXCEPTION for #DB in mind) I further realized that the special casing of individual vectors shouldn't be done for software interrupts (resulting from INT $nn). And then some code movement: Setting of CR2 for #PF can be done in the same switch() statement (no need for a separate if()), and reading of intr_info is better done close the the consumption of the variable (allowing the compiler to generate better code / use fewer registers for variables). Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Kevin Tian <kevin.tian@xxxxxxxxx> master commit: 81a28f14009f4d8577a81b28dd06f6828112054b master date: 2015-11-24 12:30:31 +0100 commit 52f7217a10ffb692ae0e320830c17dcfeb7f6810 Author: Dario Faggioli <dario.faggioli@xxxxxxxxxx> Date: Tue Dec 15 15:52:51 2015 +0100 sched: fix locking for insert_vcpu() in credit1 and RTDS The insert_vcpu() hook is handled with inconsistent locking. In fact, schedule_cpu_switch() calls the hook with runqueue lock held, while sched_move_domain() relies on the hook implementations to take the lock themselves (and, since that is not done in Credit1 and RTDS, such operation is not safe in those cases). This is fixed as follows: - take the lock in the hook implementations, in specific schedulers' code; - avoid calling insert_vcpu(), for the idle vCPU, in schedule_cpu_switch(). In fact, idle vCPUs are set to run immediately, and the various schedulers won't insert them in their runqueues anyway, even when explicitly asked to. While there, still in schedule_cpu_switch(), locking with _irq() is enough (there's no need to do *_irqsave()). Signed-off-by: Dario Faggioli <dario.faggioli@xxxxxxxxxx> Reviewed-by: Meng Xu <mengxu@xxxxxxxxxxxxx> Reviewed-by: George Dunlap <george.dunlap@xxxxxxxxxx> master commit: ae2f41e3d7e7798537b7ea6dbb9a0c6aeb1179e3 master date: 2015-11-24 14:48:34 +0100 commit 6e2cca296faf56dd76cd1fbac045dfcbe9d2e808 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Dec 15 15:51:44 2015 +0100 x86/HVM: don't inject #DB with error code Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper@xxxxxxxxxx> master commit: 057e0e72d2a5d598087c5f167ec6a13203a3cf65 master date: 2015-11-12 16:59:18 +0100 commit 1b6738ad7832f8dbf44a76039c9fc8c44384bbbd Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Tue Dec 15 15:50:47 2015 +0100 x86/vmx: improvements to vmentry failure handling Combine the almost identical vm_launch_fail() and vm_resume_fail() into a single vmx_vmentry_failure(). Re-save all GPRs so that domain_crash() prints the real register values, rather than the stack frame of the vmx_vmentry_failure() call. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Acked-by: Kevin Tian <kevin.tian@xxxxxxxxx> master commit: bbcf0b218f64b1e3e2b66b0fbb623f51d9014e81 master date: 2015-11-03 18:14:02 +0100 commit ee4d57324786bbda7f7622c9bded9925ef150d6a Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Tue Dec 15 15:50:21 2015 +0100 x86/PoD: Make p2m_pod_empty_cache() restartable This avoids a long running operation when destroying a domain with a large PoD cache. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: George Dunlap <george.dunlap@xxxxxxxxxx> master commit: 59a5061723ba47c0028cf48487e5de551c42a378 master date: 2015-11-02 15:33:38 +0100 commit dff1010b09627784c959a5ae97e10472dbe7d097 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Dec 15 15:48:44 2015 +0100 x86/NUMA: fix SRAT table processor entry parsing and consumption - don't overrun apicid_to_node[] (possible in the x2APIC case) - don't limit number of processor related SRAT entries we can consume - make acpi_numa_{processor,x2apic}_affinity_init() as similar to one another as possible - print APIC IDs in hex (to ease matching with other log messages), at once making legacy and x2APIC ones distinguishable (by width) Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: 83281fc9b31396e94c0bfb6550b75c165037a0ad master date: 2015-10-14 12:46:27 +0200 commit cc285166ed4f8ed4caee53a98cba9fa1c5536af2 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Dec 15 15:47:59 2015 +0100 x86: hide MWAITX from PV domains Since MWAIT is hidden too. (Linux starting with 4.3 is making use of that feature, and is checking for it without looking at the MWAIT one.) Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: 941cd44324db7eddc46cba4596fa13d505066ccf master date: 2015-10-13 17:17:52 +0200 commit 1db34a40ea860d11f5dec030851f3808cfd6d7ea Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Dec 15 15:47:26 2015 +0100 VT-d: don't suppress invalidation address write when it is zero GFN zero is a valid address, and hence may need invalidation done for it just like for any other GFN. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Acked-by: Yang Zhang <yang.z.zhang@xxxxxxxxx> master commit: 710942e57fb42ff8f344ca82f6b678f67e38ae63 master date: 2015-10-12 15:58:35 +0200 ======================================== _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxx http://lists.xen.org/xen-devel
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |