flight 5689 xen-unstable real [real]
http://www.chiark.greenend.org.uk/~xensrcts/logs/5689/
Regressions :-(
Tests which did not succeed and are blocking:
 test-amd64-amd64-xl-win       9 guest-localmigrate         fail REGR. vs. 5685
 test-amd64-i386-rhel6hvm-amd  7 redhat-install             fail REGR. vs. 5685
 test-amd64-xcpkern-i386-xl-win 12 guest-localmigrate/x10   fail REGR. vs. 5685
 test-i386-i386-xl-win        11 guest-localmigrate.2       fail REGR. vs. 5685
Tests which did not succeed, but are not blocking,
including regressions (tests previously passed) regarded as allowable:
 test-amd64-amd64-win         16 leak-check/check             fail   never pass
 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-win          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-amd64-xcpkern-i386-rhel6hvm-intel  8 guest-saverestore    fail never pass
 test-amd64-xcpkern-i386-win  16 leak-check/check             fail   never pass
 test-i386-i386-win           16 leak-check/check             fail   never pass
 test-i386-xcpkern-i386-win   16 leak-check/check             fail   never pass
version targeted for testing:
 xen                  a0ef80c99264
baseline version:
 xen                  1967c7c290eb
------------------------------------------------------------
People who touched revisions under test:
  Ian Jackson <Ian.Jackson@eu.citrix.com>
  Jan Beulich <jbeulich@novell.com>
  Juergen Gross <juergen.gross@ts.fujitsu.com>
  Keir Fraser <keir@xen.org>
  Tim Deegan <Tim.Deegan@citrix.com>
------------------------------------------------------------
jobs:
 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                           pass     
 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                                         fail     
 test-amd64-i386-win                                          fail     
 test-i386-i386-win                                           fail     
 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                               fail     
------------------------------------------------------------
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
    http://www.chiark.greenend.org.uk/~xensrcts/logs
Test harness code can be found at
    http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary
Not pushing.
------------------------------------------------------------
changeset:   22900:a0ef80c99264
tag:         tip
user:        Keir Fraser <keir@xen.org>
date:        Thu Feb 10 14:19:54 2011 +0000
    
    x86: suppress HPET broadcast initialization in the presence of ARAT
    
    This follows Linux commit 39fe05e58c5e448601ce46e6b03900d5bf31c4b0,
    noticing that all this setup is pointless when ARAT support is there,
    and knowing that on SLED11''s native kernel it has actually caused
S3
    resume issues.
    
    A question would be whether HPET legacy interrupts should be forced
    off in this case (rather than leaving whatever came from firmware).
    
    Signed-off-by: Jan Beulich <jbeulich@novell.com>
    
    
changeset:   22899:5b18a72d292a
user:        Keir Fraser <keir@xen.org>
date:        Thu Feb 10 14:19:23 2011 +0000
    
    x86: tighten conditions under which writing certain MSRs is permitted
    
    MSRs that control physical CPU aspects generally are pointless (and
    possibly dangerous) to be written when the writer isn''t
sufficiently
    aware that it''s running virtualized.
    
    Signed-off-by: Jan Beulich <jbeulich@novell.com>
    
    
changeset:   22898:332c1f73a594
user:        Keir Fraser <keir@xen.org>
date:        Thu Feb 10 14:14:24 2011 +0000
    
    ix86: re-do permanent disabling of x2apic
    
    Move logic into check_x2apic_preenabled() (to make sure
    generic_apic_probe() doesn''t see genapic already set).
    
    Signed-off-by: Jan Beulich <jbeulich@novell.com>
    Signed-off-by: Keir Fraser <keir@xen.org>
    
    
changeset:   22897:21df67ee7040
user:        Tim Deegan <Tim.Deegan@citrix.com>
date:        Thu Feb 10 11:27:52 2011 +0000
    
    x86/mm: make log-dirty code do all its allocations outside the lock
    to avoid taking the shadow/EPT lock with the lgd lock held.
    
    Signed-off-by: Tim Deegan <Tim.Deegan@citrix.com>
    
    
changeset:   22896:0df1b42910b1
user:        Tim Deegan <Tim.Deegan@citrix.com>
date:        Thu Feb 10 11:27:51 2011 +0000
    
    x86/mm: shuffle log-dirty code so only one path allocates memory
    
    Signed-off-by: Tim Deegan <Tim.Deegan@citrix.com>
    
    
changeset:   22895:19b2424be183
user:        Juergen Gross <juergen.gross@ts.fujitsu.com>
date:        Thu Feb 10 09:02:50 2011 +0000
    
    Cpupools: vcpu affinity handling
    
    If a vcpu is pinned to multiple physical cpus, the pinning is not
    removed if all those physical cpus are removed from the cpupool. When
    disabling the scheduler on a cpu, the affinity mask must be checked
    against the cpumask of the cpupool.
    
    Signed-off-by: Juergen Gross <juergen.gross@ts.fujitsu.com>
    
    
changeset:   22894:1967c7c290eb
user:        Tim Deegan <Tim.Deegan@citrix.com>
date:        Wed Feb 09 12:03:09 2011 +0000
    
    x86/mm/shadow: fix unlocking on error path in p2m allocator
    One unlock path wasn''t gated to match the lock.
    
    Signed-off-by: Tim Deegan <Tim.Deegan@citrix.com>
    
    
=======================================commit
ad7d28519de7cdc604efefac5c22fe9f88040586
Author: Ian Jackson <ian.jackson@eu.citrix.com>
Date:   Tue Feb 1 17:32:38 2011 +0000
    vnc, xen: write vnc address and password to xenstore
    
    The xend protocol as actually implemented is:
      * xend writes:
         /vm/UUID/vncpasswd = "PASS"   (n0,rDOMID)
         /local/domain/0/backend/vfb/DOMID/0/vncunused = "0"  
(n0,rDOMID)
         /local/domain/0/backend/vfb/DOMID/0/vnc = "1"   (n0,rDOMID)
         /local/domain/0/backend/vfb/DOMID/0/vnclisten = "ADDR"  
(n0,rDOMID)
         /local/domain/0/backend/vfb/DOMID/0/vncdisplay = "PORT"  
(n0,rDOMID)
         /local/domain/0/backend/vfb/DOMID/0/vncpasswd = "PASS"  
(n0,rDOMID)
      * qemu reads /vm/UUID/vncpasswd and overwrites it with "\0"
      * qemu writes
         /local/domain/DOMID/console/vnc-port = "PORT"   (n0,rDOMID)
      * xm vncviewer reads entries from backend/vfb,
        as well as console/vnc-port.
    Much of this is insane.
    
    xl quite properly does not create anything in backend/vfb for an HVM
    domain with no vfb.  But xl vncviewer needs to know the port number
    and the address and the password.
    
    So, for now, have qemu write these nodes too:
         /local/domain/DOMID/console/vnc-listen = "ADDR"   (n0,rDOMID)
         /local/domain/DOMID/console/vnc-pass = "PASS"   (n0,rDOMID)
    This corresponds to the protocol actually currently implemented in
    libxl.
    
    We will revisit this after the 4.1 release and invent a non-insane
    protocol.
    
    Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com>
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Ian Jackson
2011-Feb-11  16:21 UTC
Re: [Xen-devel] [xen-unstable test] 5689: regressions - FAIL
xen.org writes ("[Xen-devel] [xen-unstable test] 5689: regressions -
FAIL"):>  test-i386-i386-xl-win    11 guest-localmigrate.2       fail REGR. vs. 5685
Xen crash - failed assertion.
http://www.chiark.greenend.org.uk/~xensrcts/logs/5689/test-amd64-xcpkern-i386-xl-win/info.html
Feb 10 20:47:09.620498 (XEN) Assertion ''page_get_owner(pg) ==
d'' failed at hap.c:334
Feb 10 20:47:09.628483 (XEN) ----[ Xen-4.1.0-rc4-pre  x86_32p  debug=y  Not
tainted ]----
Feb 10 20:47:09.628521 (XEN) CPU:    0
Feb 10 20:47:09.628574 (XEN) EIP:    e008:[<ff1d33c6>]
hap_free_p2m_page+0xdc/0x1b0
Feb 10 20:47:09.640489 (XEN) EFLAGS: 00010207   CONTEXT: hypervisor
Feb 10 20:47:09.640545 (XEN) eax: 00000000   ebx: ffb62000   ecx: 00000000  
edx: 00000000
Feb 10 20:47:09.648495 (XEN) esi: f9def368   edi: 00000001   ebp: ff247c98  
esp: ff247c70
Feb 10 20:47:09.648551 (XEN) cr0: 8005003b   cr4: 000026f0   cr3: 00b7eca0  
cr2: b66a3e77
Feb 10 20:47:09.660504 (XEN) ds: e010   es: e010   fs: 00d8   gs: 0033   ss:
e010   cs: e008
Feb 10 20:47:09.660552 (XEN) Xen stack trace from esp=ff247c70:
Feb 10 20:47:09.668507 (XEN)    ffb62a98 ff29c000 ff247ca8 00000287 ff29c10c
00000400 00000079 fec79000
Feb 10 20:47:09.680522 (XEN)    fec79800 00000000 ff247ca8 ff1b2504 ffb62000
f9def368 ff247ce8 ff1b3663
Feb 10 20:47:09.688486 (XEN)    0023f4d0 00000002 fec76000 fec76000 fec78000
fec78000 fec76000 fec78000
Feb 10 20:47:09.688546 (XEN)    fec79000 fec78000 fec76000 ffb62000 ffb62abc
00000000 ff247d08 ff1b3df3
Feb 10 20:47:09.696742 (XEN)    ffb62000 00000000 ff247dd8 ffb62000 ff247ef8
08475004 ff247d38 ff1b3fc5
Feb 10 20:47:09.709002 (XEN)    ffb62000 ff1585b5 f9c653f0 ff1d6135 fed63000
80000001 00000000 ffb62000
Feb 10 20:47:09.709076 (XEN)    08475004 08475004 ff247e58 ff146247 ffb62000
ff247ef8 08475004 ff247fb0
Feb 10 20:47:09.720904 (XEN)    00000004 00000001 ff2cee78 00000000 70000000
00000000 30000000 f9c6ad90
Feb 10 20:47:09.728500 (XEN)    f9d1b6c4 3c000002 f9c6ad9c ff247d9c ff11f591
0022f1e6 f9c6ad90 30000000
Feb 10 20:47:09.736592 (XEN)    ff247dd0 ff1585b5 f9c6ad90 ff247dec ff1158a5
00000001 00000000 00000000
Feb 10 20:47:09.736652 (XEN)    0023679d 00000001 0022f1e6 00000246 ffb7ecc8
ff247dd0 ff11f919 0022f1e6
Feb 10 20:47:09.748507 (XEN)    ff247e00 ff157fc3 ff247fb0 ff247fb0 ff247e10
ff15a1ee 00000000 f9c6ac58
Feb 10 20:47:09.756530 (XEN)    f9c6ac64 00000000 50000000 f9b084c0 ff247e10
08475004 f9b084cc ffb7e000
Feb 10 20:47:09.756590 (XEN)    ff247e40 ff15bba8 f9c6ac58 00000000 80000002
3679d067 00000002 00013bcd
Feb 10 20:47:09.768515 (XEN)    00000000 00000202 ff2130b4 ff247e48 ff11fb17
fffffff3 ff247e58 fffffff3
Feb 10 20:47:09.776504 (XEN)    00000024 08475004 ff247f88 ff1038ec ff247ee8
08475004 00000090 00000002
Feb 10 20:47:09.788494 (XEN)    ff247e80 ff15a02f 00000000 f9b084c0 ff247f00
ff15c519 f9b084c0 00220588
Feb 10 20:47:09.788552 (XEN)    00000001 ffb7e000 ff29c000 ff29c000 00000000
00000000 00000000 00000000
Feb 10 20:47:09.796510 (XEN)    00000001 00000000 fedfc040 ff29c000 fedfc000
f9b084c0 00000000 ff29c000
Feb 10 20:47:09.808500 (XEN)    00000092 ff213720 00000001 ff247ee4 ff1319d2
00000001 0000000a 00000007
Feb 10 20:47:09.808541 (XEN) Xen call trace:
Feb 10 20:47:09.808591 (XEN)    [<ff1d33c6>] hap_free_p2m_page+0xdc/0x1b0
Feb 10 20:47:09.816510 (XEN)    [<ff1b2504>]
paging_free_log_dirty_page+0x24/0x26
Feb 10 20:47:09.816565 (XEN)    [<ff1b3663>]
paging_free_log_dirty_bitmap+0xe6/0x19c
Feb 10 20:47:09.828512 (XEN)    [<ff1b3df3>]
paging_log_dirty_disable+0xb8/0x114
Feb 10 20:47:09.828562 (XEN)    [<ff1b3fc5>] paging_domctl+0x132/0x18d
Feb 10 20:47:09.836507 (XEN)    [<ff146247>] arch_do_domctl+0x2dd/0x2c66
Feb 10 20:47:09.836556 (XEN)    [<ff1038ec>] do_domctl+0x16eb/0x175f
Feb 10 20:47:09.848499 (XEN)    [<ff1d973f>] hypercall+0xaf/0xcf
Feb 10 20:47:09.848535 (XEN)
Feb 10 20:47:09.848569 (XEN)
Feb 10 20:47:09.848615 (XEN) ****************************************
Feb 10 20:47:09.848654 (XEN) Panic on CPU 0:
Feb 10 20:47:09.856513 (XEN) Assertion ''page_get_owner(pg) ==
d'' failed at hap.c:334
Feb 10 20:47:09.856559 (XEN) ****************************************
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Ian Jackson
2011-Feb-11  16:25 UTC
Re: [Xen-devel] [xen-unstable test] 5689: regressions - FAIL [and 1 more messages]
I wrote ("Re: [Xen-devel] [xen-unstable test] 5689: regressions -
FAIL"):> xen.org writes ("[Xen-devel] [xen-unstable test] 5689: regressions -
FAIL"):
> >  test-i386-i386-xl-win    11 guest-localmigrate.2       fail REGR. vs.
5685
> 
> Xen crash - failed assertion.
These two look identical:
>  test-amd64-amd64-xl-win       9 guest-localmigrate      fail REGR. vs.
5685
>  test-amd64-xcpkern-i386-xl-win 12 guest-localmigrate/x10 fail REGR. vs.
5685
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Tim Deegan
2011-Feb-11  16:55 UTC
Re: [Xen-devel] [xen-unstable test] 5689: regressions - FAIL
At 16:21 +0000 on 11 Feb (1297441276), Ian Jackson wrote:> xen.org writes ("[Xen-devel] [xen-unstable test] 5689: regressions - FAIL"): > > test-i386-i386-xl-win 11 guest-localmigrate.2 fail REGR. vs. 5685 > > Xen crash - failed assertion.Stupid typo in my deadlock fix. Fixed as cset 22905:6c22ae0f6540 of the staging tree. Tim. -- Tim Deegan <Tim.Deegan@citrix.com> Principal Software Engineer, Xen Platform Team Citrix Systems UK Ltd. (Company #02937203, SL9 0BG) _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel