[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [xen-unstable test] 5124: regressions - FAIL


  • To: "xen.org" <ian.jackson@xxxxxxxxxxxxx>
  • From: George Dunlap <George.Dunlap@xxxxxxxxxxxxx>
  • Date: Thu, 20 Jan 2011 10:24:57 +0000
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 20 Jan 2011 02:25:35 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; b=CMA03Fe6uaO9mzV+swRJwDGvbq+Q+RE6mQmM5zJx4kpBQtP9uP0nWY4rZgRlOFzgtR qr+TuGRpEr0tPXbuU9+JtJnLC9nZ3Fnt0rFY63DeAa+c0fE2Axt9BWvK6wi1N+uIW8Jm esXHStYsiwv7v1lEO+/NNZ/6kacK21d324jMc=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

Looking at the logs, it looks like both of these failures are probably
due to the intermittent "failure to find the guest's IP address",
which could be because:
* networking is not coming up (bug in Xen system)
* Networking came up but it failed to get an IP address (bug in network system)
* Guest got an IP, but test harness failed to find out what it was
(algorithm for finding IP not robust)

According to this log, in the RH case the guest did receive an IP address:

http://www.chiark.greenend.org.uk/~xensrcts/logs/5124/test-amd64-xcpkern-i386-rhel6hvm-intel/earwig---var-log-xen-qemu-dm-redhat.guest.osstest.log

It doesn't look like stale output from a previous run
(...osstest.log.1 looks like the console output from the install
process), so I think it's reasonable to blame the test harness' IP
detection code.

The XenServer test harness, XenRT, has code to sniff packets and grok
dhcp requests and replies.  Would it make sense to steal that, and see
if it's more robust?

 -George

On Thu, Jan 20, 2011 at 8:58 AM, xen.org <ian.jackson@xxxxxxxxxxxxx> wrote:
> flight 5124 xen-unstable real [real]
> http://www.chiark.greenend.org.uk/~xensrcts/logs/5124/
>
> Regressions :-(
>
> Tests which did not succeed and are blocking:
>  test-amd64-xcpkern-i386-rhel6hvm-intel  7 redhat-install   fail REGR. vs. 
> 5086
>  test-i386-i386-win           14 guest-start.2              fail REGR. vs. 
> 5086
>
> Tests which are failing intermittently (not blocking):
>  test-amd64-i386-win          12 guest-localmigrate/x10       fail pass in 
> 5102
>  test-amd64-i386-xl           18 leak-check/check             fail pass in 
> 5102
>  test-amd64-xcpkern-i386-pair  8 xen-boot/dst_host            fail pass in 
> 5102
>
> 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-amd  8 guest-saverestore            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-xcpkern-i386-rhel6hvm-amd  8 guest-saverestore      fail never 
> pass
>  test-amd64-xcpkern-i386-win  16 leak-check/check             fail   never 
> pass
>  test-i386-xcpkern-i386-win    5 xen-boot                     fail    like 
> 5086
>
> version targeted for testing:
>  xen                  051a1b1b8f8a
> baseline version:
>  xen                  d1631540bcc4
>
> ------------------------------------------------------------
> People who touched revisions under test:
>  George Dunlap <george.dunlap@xxxxxxxxxxxxx>
>  Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
>  Jim Fehlig <jfehlig@xxxxxxxxxx>
>  Keir Fraser <keir@xxxxxxx>
>  Shriram Rajagopalan <rshriram@xxxxxxxxx>
>  Tim Deegan <Tim.Deegan@xxxxxxxxxx>
> ------------------------------------------------------------
>
> 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                                           fail
>  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                                 fail
>  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-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
>
>
> ------------------------------------------------------------
> 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:   22783:051a1b1b8f8a
> tag:         tip
> user:        Keir Fraser <keir@xxxxxxx>
> date:        Wed Jan 19 18:24:26 2011 +0000
>
>    Disable tmem by default for 4.1 release.
>
>    Although one major source of order>0 allocations has been removed,
>    others still remain, so re-disable tmem until the issue can be fixed
>    properly.
>
>    Signed-off-by: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
>
>
> changeset:   22782:fe8a177ae9cb
> user:        Keir Fraser <keir@xxxxxxx>
> date:        Wed Jan 19 15:29:04 2011 +0000
>
>    x86_emulate: set the operand size for SMSW/reg writeback.
>    Otherwise it defaults to 0 bytes.
>
>    Signed-off-by: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
>    Signed-off-by: Keir Fraser <keir@xxxxxxx>
>
>
> changeset:   22781:3decd02e0b18
> user:        George Dunlap <george.dunlap@xxxxxxxxxxxxx>
> date:        Mon Jan 17 14:29:01 2011 +0000
>
>    PoD,hap: Fix logdirty mode when using hardware assisted paging
>
>    When writing a writable p2m entry for a pfn, we need to mark the pfn
>    dirty to avoid corruption when doing live migration.
>
>    Marking the page dirty exposes another issue, where there are
>    excessive sweeps for zero pages if there's a mismatch between PoD
>    entries and cache entries.  Only sweep for zero pages if we actually
>    need more memory.
>
>    Signed-off-by: George Dunlap <george.dunlap@xxxxxxxxxxxxx>
>    Acked-by: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
>
>
> changeset:   22780:97ab84aca65c
> user:        George Dunlap <george.dunlap@xxxxxxxxxxxxx>
> date:        Mon Jan 17 14:24:13 2011 +0000
>
>    PoD: Allow pod_set_cache_target hypercall to be preempted
>
>    For very large VMs, setting the cache target can take long enough that
>    dom0 complains of soft lockups.  Allow the hypercall to be preempted.
>
>    Signed-off-by: George Dunlap <george.dunlap@xxxxxxxxxxxxx>
>    Acked-by: Tim Deegan <Tim.Deegan@xxxxxxxxxx>
>
>
> changeset:   22779:d1631540bcc4
> user:        Jim Fehlig <jfehlig@xxxxxxxxxx>
> date:        Tue Jan 18 17:23:24 2011 +0000
>
>    xend: improve psudeo-bootloader support for external block scripts
>
>    Userspace tools support external block scripts (e.g. block-drbd
>    provided by drbd project).  The psuedo-bootloader setup code in
>    xend has a few limitations wrt external block scripts, which this
>    patch addresses.
>
>    blkif.py: parse_uname() utility function should be able to parse a
>    disk specifier understood by the rest of the tools.
>
>    XendDomainInfo.py: Block devices using external block scripts must
>    be attached to dom0 before running the psuedo-bootloader.
>
>    Signed-off-by: Jim Fehlig <jfehlig@xxxxxxxxxx>
>    Tested-by: Shriram Rajagopalan <rshriram@xxxxxxxxx>
>    Committed-by: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
>
>
> (qemu changes not included)
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.