This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] [xen-4.1-testing test] 6530: regressions - trouble: broken/f

To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] [xen-4.1-testing test] 6530: regressions - trouble: broken/fail/pass
From: xen.org <ian.jackson@xxxxxxxxxxxxx>
Date: Wed, 16 Mar 2011 12:31:19 +0000
Cc: ian.jackson@xxxxxxxxxxxxx
Delivery-date: Wed, 16 Mar 2011 05:32:08 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
flight 6530 xen-4.1-testing real [real]

Regressions :-(

Tests which did not succeed and are blocking:
 test-amd64-amd64-win          3 host-install(3)              broken
 test-amd64-i386-win           5 xen-boot                   fail REGR. vs. 6432
 test-amd64-xcpkern-i386-rhel6hvm-intel  7 redhat-install   fail REGR. vs. 6432
 test-amd64-xcpkern-i386-win   7 windows-install            fail REGR. vs. 6432
 test-amd64-xcpkern-i386-xl-credit2  8 debian-fixup         fail REGR. vs. 6432
 test-amd64-xcpkern-i386-xl-win  3 host-install(3)              broken
 test-i386-i386-win            3 host-install(3)              broken

Tests which did not succeed, but are not blocking,
including regressions (tests previously passed) regarded as allowable:
 test-amd64-amd64-xl-win      13 guest-stop                   fail   never pass
 test-amd64-i386-rhel6hvm-amd  7 redhat-install               fail    like 6432
 test-amd64-i386-rhel6hvm-intel  8 guest-saverestore            fail never pass
 test-amd64-i386-win-vcpus1   16 leak-check/check             fail   never pass
 test-amd64-i386-xl-win-vcpus1 13 guest-stop                   fail  never pass
 test-amd64-xcpkern-i386-rhel6hvm-amd  8 guest-saverestore      fail never pass
 test-i386-i386-xl-win        13 guest-stop                   fail   never pass
 test-i386-xcpkern-i386-win   16 leak-check/check             fail   never pass

version targeted for testing:
 xen                  762155e9debd
baseline version:
 xen                  d4352abf3450

People who touched revisions under test:
  Gianni Tedesco <gianni.tedesco@xxxxxxxxxx>
  Jan Beulich <jbeulich@xxxxxxxxxx>
  Keir Fraser <keir@xxxxxxx>
  Tim Deegan <Tim.Deegan@xxxxxxxxxx>
  Wei Gang <gang.wei@xxxxxxxxx>

 build-i386-xcpkern                                           pass     
 build-amd64                                                  pass     
 build-i386                                                   pass     
 build-amd64-oldkern                                          pass     
 build-i386-oldkern                                           pass     
 build-amd64-pvops                                            pass     
 build-i386-pvops                                             pass     
 test-amd64-amd64-xl                                          pass     
 test-amd64-i386-xl                                           pass     
 test-i386-i386-xl                                            pass     
 test-amd64-xcpkern-i386-xl                                   pass     
 test-i386-xcpkern-i386-xl                                    pass     
 test-amd64-i386-rhel6hvm-amd                                 fail     
 test-amd64-xcpkern-i386-rhel6hvm-amd                         fail     
 test-amd64-i386-xl-credit2                                   pass     
 test-amd64-xcpkern-i386-xl-credit2                           fail     
 test-amd64-i386-rhel6hvm-intel                               fail     
 test-amd64-xcpkern-i386-rhel6hvm-intel                       fail     
 test-amd64-i386-xl-multivcpu                                 pass     
 test-amd64-xcpkern-i386-xl-multivcpu                         pass     
 test-amd64-amd64-pair                                        pass     
 test-amd64-i386-pair                                         pass     
 test-i386-i386-pair                                          pass     
 test-amd64-xcpkern-i386-pair                                 pass     
 test-i386-xcpkern-i386-pair                                  pass     
 test-amd64-amd64-pv                                          pass     
 test-amd64-i386-pv                                           pass     
 test-i386-i386-pv                                            pass     
 test-amd64-xcpkern-i386-pv                                   pass     
 test-i386-xcpkern-i386-pv                                    pass     
 test-amd64-i386-win-vcpus1                                   fail     
 test-amd64-i386-xl-win-vcpus1                                fail     
 test-amd64-amd64-win                                         broken   
 test-amd64-i386-win                                          fail     
 test-i386-i386-win                                           broken   
 test-amd64-xcpkern-i386-win                                  fail     
 test-i386-xcpkern-i386-win                                   fail     
 test-amd64-amd64-xl-win                                      fail     
 test-i386-i386-xl-win                                        fail     
 test-amd64-xcpkern-i386-xl-win                               broken   

sg-report-flight on woking.cam.xci-test.com
logs: /home/xc_osstest/logs
images: /home/xc_osstest/images

Logs, config files, etc. are available at

Test harness code can be found at

Not pushing.

changeset:   22998:762155e9debd
tag:         tip
user:        Jan Beulich <jbeulich@xxxxxxxxxx>
date:        Tue Mar 15 13:55:40 2011 +0000
    x86: run-time callers of map_pages_to_xen() must check for errors
    Again, (out-of-memory) errors must not cause hypervisor crashes, and
    hence ought to be propagated.
    This also adjusts the cache attribute changing loop in
    get_page_from_l1e() to not go through an unnecessary iteration. While
    this could be considered mere cleanup, it is actually a requirement
    for the subsequent now necessary error recovery path.
    Also make a few functions static, easing the check for potential
    callers needing adjustment.
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>
    xen-unstable changeset:   22997:5f28dcea1355
    xen-unstable date:        Wed Mar 09 16:15:36 2011 +0000
    x86: don't BUG() post-boot in alloc_xen_pagetable()
    Instead, propagate the condition to the caller, all of which also get
    adjusted to check for that situation.
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>
    xen-unstable changeset:   22996:1eeccafe9042
    xen-unstable date:        Wed Mar 09 16:14:59 2011 +0000
changeset:   22997:cd4d0c5dfa27
user:        Jan Beulich <jbeulich@xxxxxxxxxx>
date:        Mon Mar 14 17:21:13 2011 +0000
    _csched_cpu_pick(): don't return CPUs outside vCPU's affinity mask
    This fixes a fairly blatant bug I introduced in c/s 20377:cff23354d026
    - I wonder how this went unnoticed for so long.
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>
    xen-unstable changeset:   23039:c40da47621d8
    xen-unstable date:        Mon Mar 14 17:19:22 2011 +0000
changeset:   22996:6ac812f16e13
user:        Gianni Tedesco <gianni.tedesco@xxxxxxxxxx>
date:        Mon Mar 14 17:14:16 2011 +0000
    Allow tools to map arbitrarily large machphys_mfn_list on 32bit dom0
    This permits suspend/resume to work with 32bit dom0/tools when system
    memory extends beyond 160GB (and up to 1TB).
    AFAICT the limit to MACH2PHYS_COMPAT_NR_ENTRIES is redundant since
    that refers to a limit in 32bit guest compat mappings under 64bit
    hypervisors, not userspace where there may be gigabytes of useful
    virtual space available for this.
    Suggested-by: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>
    Signed-off-by: Gianni Tedesco <gianni.tedesco@xxxxxxxxxx>
    xen-unstable changeset:   23038:39f5947b1576
    xen-unstable date:        Mon Mar 14 17:13:15 2011 +0000
changeset:   22995:9175944daf48
user:        Jan Beulich <jbeulich@xxxxxxxxxx>
date:        Mon Mar 14 17:08:00 2011 +0000
    x86: fix cpu_sibling_map initialization when topology CPUID leaf is present
    c/s 21811:12f0618400de broke this by not properly initializing struct
    cpuinfo_x86's x86_num_siblings member (other than Linux, where this is
    a global variable, it is being maintained per CPU by Xen).
    Hyper-threaded CPUs with CPUID leaf 0xb present had therefore all
    cpu_sibling_map-s with just a single bit set, thus improperly feeding
    the scheduler.
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>
    xen-unstable changeset:   23037:a29b35408950
    xen-unstable date:        Mon Mar 14 17:05:21 2011 +0000
changeset:   22994:5dda35f1f32f
user:        Wei Gang <gang.wei@xxxxxxxxx>
date:        Mon Mar 14 17:07:29 2011 +0000
    x86: add volatile prefix for cpuid asm clauses
    cpuid results are possible to be changed now. For example, changing
    CR4.OSXSAVE bit or setting MSR XCR_XFEATURE_ENABLED_MASK may change
    XSAVE related cpuid leave return values.
    The volatile prefix is required to avoid the second cpuid calls
    following some possible changing operations being optimized in
    incorrect way by compiler.
    The sample bug is in xsave_init while debug=3Dn. The second call to
    cpuid_count() may be optimized and lead to a BUG_ON case while compare
    xsave_cntxt_size with ebx.
    Signed-off-by: Wei Gang <gang.wei@xxxxxxxxx>
    xen-unstable changeset:   23036:9a15ff175e00
    xen-unstable date:        Mon Mar 14 17:04:42 2011 +0000
changeset:   22993:842aed720b84
user:        Tim Deegan <Tim.Deegan@xxxxxxxxxx>
date:        Mon Mar 14 17:00:34 2011 +0000
    x86_64: fix error checking in arch_set_info_guest()
    Cannot specify user mode execution without specifying user-mode
    Signed-off-by: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
    Acked-by: Keir Fraser <keir@xxxxxxx>
    xen-unstable changeset:   23034:c79aae866ad8
    xen-unstable date:        Mon Mar 14 16:59:49 2011 +0000
changeset:   22992:d4352abf3450
user:        Jan Beulich <jbeulich@xxxxxxxxxx>
date:        Sat Mar 12 13:25:44 2011 +0000
    x86/HPET: fix initialization order
    At least the legacy path can enter its interrupt handler callout while
    initialization is still in progress - that handler checks whether
    ->event_handler is non-NULL, and hence all other initialization must
    happen before setting this field.
    Do the same to the MSI initialization just in case (and to keep the
    code in sync).
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxxxx>
    Acked-by: Wei Gang <gang.wei@xxxxxxxxx>
    xen-unstable changeset:   23030:87aa1277eae0
    xen-unstable date:        Sat Mar 12 13:19:02 2011 +0000
(qemu changes not included)

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] [xen-4.1-testing test] 6530: regressions - trouble: broken/fail/pass, xen . org <=