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

[Xen-devel] [qemu-mainline test] 29441: regressions - FAIL

flight 29441 qemu-mainline real [real]

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-amd64-xl-qemuu-ovmf-amd64 13 guest-localmigrate/x10 fail REGR. vs. 
 test-amd64-i386-xl-qemuu-win7-amd64 13 guest-localmigrate/x10 fail REGR. vs. 

Tests which did not succeed, but are not blocking:
 test-armhf-armhf-libvirt      9 guest-start                  fail   never pass
 test-amd64-i386-libvirt       9 guest-start                  fail   never pass
 test-armhf-armhf-xl          10 migrate-support-check        fail   never pass
 test-amd64-amd64-xl-pcipt-intel  9 guest-start                 fail never pass
 test-amd64-amd64-libvirt      9 guest-start                  fail   never pass
 test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 14 guest-stop         fail never pass
 test-amd64-amd64-xl-winxpsp3 14 guest-stop                   fail   never pass
 test-amd64-i386-xl-qemut-winxpsp3-vcpus1 14 guest-stop         fail never pass
 test-amd64-amd64-xl-qemut-winxpsp3 14 guest-stop               fail never pass
 test-amd64-amd64-xl-qemut-win7-amd64 14 guest-stop             fail never pass
 test-amd64-amd64-xl-qemuu-winxpsp3 14 guest-stop               fail never pass
 test-amd64-amd64-xl-qemuu-win7-amd64 14 guest-stop             fail never pass
 test-amd64-i386-xl-qemut-winxpsp3 14 guest-stop                fail never pass
 test-amd64-i386-xl-winxpsp3-vcpus1 14 guest-stop               fail never pass
 test-amd64-i386-xl-qemut-win7-amd64 14 guest-stop              fail never pass
 test-amd64-i386-xl-win7-amd64 14 guest-stop                   fail  never pass
 test-amd64-amd64-xl-win7-amd64 14 guest-stop                   fail never pass
 test-amd64-i386-xl-qemuu-winxpsp3 14 guest-stop                fail never pass
 test-amd64-i386-xl-winxpsp3  14 guest-stop                   fail   never pass

version targeted for testing:
 qemuu                f368c33d5ab09dd5656924185cd975b11838cd25
baseline version:
 qemuu                35858955e6c6f9ef41c199d15457c13426ac6434

People who touched revisions under test:
  Alexander Graf <agraf@xxxxxxx>
  Amit Shah <amit.shah@xxxxxxxxxx>
  Chen Gang <gang.chen.5i5j@xxxxxxxxx>
  Gerd Hoffmann <kraxel@xxxxxxxxxx>
  Hu Tao <hutao@xxxxxxxxxxxxxx>
  John Snow <jsnow@xxxxxxxxxx>
  Laszlo Ersek <lersek@xxxxxxxxxx>
  Paolo Bonzini <pbonzini@xxxxxxxxxx>
  Peter Maydell <peter.maydell@xxxxxxxxxx>

 build-amd64                                                  pass    
 build-armhf                                                  pass    
 build-i386                                                   pass    
 build-amd64-libvirt                                          pass    
 build-armhf-libvirt                                          pass    
 build-i386-libvirt                                           pass    
 build-amd64-pvops                                            pass    
 build-armhf-pvops                                            pass    
 build-i386-pvops                                             pass    
 test-amd64-amd64-xl                                          pass    
 test-armhf-armhf-xl                                          pass    
 test-amd64-i386-xl                                           pass    
 test-amd64-i386-rhel6hvm-amd                                 pass    
 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                         fail    
 test-amd64-i386-xl-qemuu-ovmf-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-amd64-amd64-xl-win7-amd64                               fail    
 test-amd64-i386-xl-win7-amd64                                fail    
 test-amd64-i386-xl-credit2                                   pass    
 test-amd64-i386-freebsd10-i386                               pass    
 test-amd64-amd64-xl-pcipt-intel                              fail    
 test-amd64-i386-rhel6hvm-intel                               pass    
 test-amd64-i386-qemut-rhel6hvm-intel                         pass    
 test-amd64-i386-qemuu-rhel6hvm-intel                         pass    
 test-amd64-amd64-libvirt                                     fail    
 test-armhf-armhf-libvirt                                     fail    
 test-amd64-i386-libvirt                                      fail    
 test-amd64-i386-xl-multivcpu                                 pass    
 test-amd64-amd64-pair                                        pass    
 test-amd64-i386-pair                                         pass    
 test-amd64-amd64-xl-sedf-pin                                 pass    
 test-amd64-amd64-xl-sedf                                     pass    
 test-amd64-i386-xl-qemut-winxpsp3-vcpus1                     fail    
 test-amd64-i386-xl-qemuu-winxpsp3-vcpus1                     fail    
 test-amd64-i386-xl-winxpsp3-vcpus1                           fail    
 test-amd64-amd64-xl-qemut-winxpsp3                           fail    
 test-amd64-i386-xl-qemut-winxpsp3                            fail    
 test-amd64-amd64-xl-qemuu-winxpsp3                           fail    
 test-amd64-i386-xl-qemuu-winxpsp3                            fail    
 test-amd64-amd64-xl-winxpsp3                                 fail    
 test-amd64-i386-xl-winxpsp3                                  fail    

sg-report-flight on osstest.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.

commit f368c33d5ab09dd5656924185cd975b11838cd25
Author: Peter Maydell <peter.maydell@xxxxxxxxxx>
Date:   Tue Jul 22 18:17:03 2014 +0100

    Update version for v2.1.0-rc3 release
    Signed-off-by: Peter Maydell <peter.maydell@xxxxxxxxxx>

commit ef493d5c291e4689d64ff4973915a7442109a5c5
Author: Peter Maydell <peter.maydell@xxxxxxxxxx>
Date:   Tue Jul 22 17:10:01 2014 +0100

    hw/misc/imx_ccm.c: Add missing VMState list terminator
    The VMStateDescription for the imx_ccm device was missing its
    terminator. Found by static search of the codebase using
    a regex based on one suggested by Ian Jackson:
      pcregrep -rMi '(?s)VMStateField(?:(?!END_OF_LIST).)*?;' $(git grep -l 
    Signed-off-by: Peter Maydell <peter.maydell@xxxxxxxxxx>
    Cc: qemu-stable@xxxxxxxxxx

commit 3afca1d6d413592c2b78cf28f52fa24a586d8f56
Author: Laszlo Ersek <lersek@xxxxxxxxxx>
Date:   Tue Jul 22 17:26:41 2014 +0200

    vmstate_xhci_event: fix unterminated field list
    "vmstate_xhci_event" was introduced in commit 37352df3 ("xhci: add live
    migration support"), and first released in v1.6.0. The field list in this
    VMSD is not terminated with the VMSTATE_END_OF_LIST() macro.
    During normal use (ie. migration), the issue is practically invisible,
    because the "vmstate_xhci_event" object (with the unterminated field list)
    is only ever referenced -- via "vmstate_xhci_intr" -- if xhci_er_full()
    returns true, for the "ev_buffer" test. Since that field_exists() check
    (apparently) almost always returns false, we almost never traverse
    "vmstate_xhci_event" during migration, which hides the bug.
    However, Amit's vmstate checker forces recursion into this VMSD as well,
    and the lack of VMSTATE_END_OF_LIST() breaks the field list terminator
    check (field->name != NULL) in dump_vmstate_vmsd(). The result is
    undefined behavior, which in my case translates to infinite recursion
    (because the loop happens to overflow into "vmstate_xhci_intr", which then
    links back to "vmstate_xhci_event").
    Add the missing terminator.
    Signed-off-by: Laszlo Ersek <lersek@xxxxxxxxxx>
    Reviewed-by: Amit Shah <amit.shah@xxxxxxxxxx>
    Reviewed-by: Paolo Bonzini <pbonzini@xxxxxxxxxx>
    Cc: qemu-stable@xxxxxxxxxx
    Signed-off-by: Peter Maydell <peter.maydell@xxxxxxxxxx>

commit 3a18d449836d21dee60439b154056cca9a3b6aee
Merge: b64c670 e206ad4
Author: Peter Maydell <peter.maydell@xxxxxxxxxx>
Date:   Tue Jul 22 16:40:34 2014 +0100

    Merge remote-tracking branch 'remotes/agraf/tags/signed-ppc-for-upstream' 
into staging
    Patch queue for ppc - 2014-07-22
    Only a single bug fix to make -mem-path only affect RAM regions.
    # gpg: Signature made Tue 22 Jul 2014 16:38:04 BST using RSA key ID 03FEDC60
    # gpg: Can't check signature: public key not found
    * remotes/agraf/tags/signed-ppc-for-upstream:
      ppc: fix -mem-path failure
    Signed-off-by: Peter Maydell <peter.maydell@xxxxxxxxxx>

commit e206ad48333c50373663945746828fc893b50700
Author: Hu Tao <hutao@xxxxxxxxxxxxxx>
Date:   Mon Jul 21 17:30:17 2014 +0800

    ppc: fix -mem-path failure
    commit e938ba0c tried to enable -mem-path for ppc but breaked some ppc
    The problems are:
    1. it fails when allocating memory for rom, sram whose sizes are less
       than huge page size:
       ./ppc-softmmu/qemu-system-ppc  -m 512 -mem-path /hugepages/ \
       -kernel /home/hutao/Downloads/vmlinux-ppc -initrd \
       qemu-system-ppc: /mnt/data/projects/qemu/exec.c:1184: 
qemu_ram_set_idstr: Assertion `new_block' failed.
    2. if there is a numa node backed by memory backend object, qemu fails
       with message:
       ./ppc-softmmu/qemu-system-ppc  -m 512 \
       -object memory-backend-file,size=512M,mem-path=/hugepages,id=f0 \
       -numa node,nodeid=0,memdev=f0 \
       -kernel /home/hutao/Downloads/vmlinux-ppc \
       -initrd /home/hutao/Downloads/initrd-ppc.gz
       qemu-system-ppc: memory backend f0 is used multiple times. Each -numa 
option must use a different memdev value.
    This patch does following:
    1. replaces memory_region_allocate_system_memory() with
       memory_region_init_ram() for rom, sram. Then only system memory
       is backed by hugepages when specifying mem-path.
    2. for memory banks, allocates all ram with
       one memory_region_allocate_system_memory(), and use
       memory_region_init_alias() to initialize memory banks.
    Tested machines: default(g3beige), mac99, taihu, bamboo, ref405ep.
    Signed-off-by: Hu Tao <hutao@xxxxxxxxxxxxxx>
    Signed-off-by: Alexander Graf <agraf@xxxxxxx>

commit b64c670f1ddcd02d003e701f69cf573d7c559ecb
Merge: 25af8e6 713e8a1
Author: Peter Maydell <peter.maydell@xxxxxxxxxx>
Date:   Tue Jul 22 13:16:04 2014 +0100

    Merge remote-tracking branch 'remotes/amit-virtio-rng/for-2.1' into staging
    * remotes/amit-virtio-rng/for-2.1:
      virtio-rng: Add human-readable error message for negative max-bytes 
    Signed-off-by: Peter Maydell <peter.maydell@xxxxxxxxxx>

commit 713e8a102222b6b8ca65050d13b287f5705831b0
Author: John Snow <jsnow@xxxxxxxxxx>
Date:   Mon Jul 21 17:44:37 2014 -0400

    virtio-rng: Add human-readable error message for negative max-bytes 
    If a negative integer is used for the max_bytes parameter, QEMU currently
    calls abort() and leaves behind a core dump. This patch replaces the
    abort with a simple error message to make the reason for the termination
    clearer. This also ensures device-hotplug with invalid input doesn't
    cause qemu to quit.
    There is an underlying insufficiency in the parameter parsing code of QEMU
    that renders it unable to reject negative values for unsigned properties,
    thus the error message "a non-negative integer below 2^63" is the most
    user-friendly and correct message we can give until the underlying
    insufficiency is corrected.
    Signed-off-by: John Snow <jsnow@xxxxxxxxxx>
    Reviewed-by: Markus Armbruster <armbru@xxxxxxxxxx>
    Signed-off-by: Amit Shah <amit.shah@xxxxxxxxxx>

commit 25af8e6b6106f47f5ee276545fcab47cefa67ba1
Merge: 3585895 dc54e25
Author: Peter Maydell <peter.maydell@xxxxxxxxxx>
Date:   Tue Jul 22 12:03:44 2014 +0100

    Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into 
    One of the two pending migration fix, and a small KVM patch.
    # gpg: Signature made Tue 22 Jul 2014 11:49:30 BST using RSA key ID 9B4D86F2
    # gpg: Can't check signature: public key not found
    * remotes/bonzini/tags/for-upstream:
      kvm-all: Use 'tmpcpu' instead of 'cpu' in sub-looping to avoid 'cpu' be 
      exec: fix migration with devices that use address_space_rw
    Signed-off-by: Peter Maydell <peter.maydell@xxxxxxxxxx>

commit dc54e2525389e903cee2b847cf761b5d857f75cb
Author: Chen Gang <gang.chen.5i5j@xxxxxxxxx>
Date:   Sat Jul 19 09:21:46 2014 +0800

    kvm-all: Use 'tmpcpu' instead of 'cpu' in sub-looping to avoid 'cpu' be NULL
    If kvm_arch_remove_sw_breakpoint() in CPU_FOREACH() always be fail, it
    will let 'cpu' NULL. And the next kvm_arch_remove_sw_breakpoint() in
    QTAILQ_FOREACH_SAFE() will get NULL parameter for 'cpu'.
    And kvm_arch_remove_sw_breakpoint() can assumes 'cpu' must never be NULL,
    so need define additional temporary variable for 'cpu' to avoid the case.
    Cc: qemu-stable@xxxxxxxxxx
    Signed-off-by: Chen Gang <gang.chen.5i5j@xxxxxxxxx>
    Signed-off-by: Paolo Bonzini <pbonzini@xxxxxxxxxx>

commit 6886867e9880830d735d8ae6f6cc63ed9eb2be0c
Author: Paolo Bonzini <pbonzini@xxxxxxxxxx>
Date:   Mon Jul 21 16:45:18 2014 +0200

    exec: fix migration with devices that use address_space_rw
    Devices that use address_space_rw to write large areas to memory
    (as opposed to address_space_map/unmap) were broken with respect
    to migration since fe680d0 (exec: Limit translation limiting in
    address_space_translate to xen, 2014-05-07).  Such devices include
    IDE CD-ROMs.
    The reason is that invalidate_and_set_dirty (called by address_space_rw
    but not address_space_map/unmap) was only setting the dirty bit for
    the first page in the translation.
    To fix this, introduce cpu_physical_memory_set_dirty_range_nocode that
    is the same as cpu_physical_memory_set_dirty_range except it does not
    muck with the DIRTY_MEMORY_CODE bitmap.  This function can be used if
    the caller invalidates translations with tb_invalidate_phys_page_range.
    There is another difference between cpu_physical_memory_set_dirty_range
    and cpu_physical_memory_set_dirty_flag; the former includes a call
    to xen_modified_memory.  This is handled separately in
    invalidate_and_set_dirty, and is not needed in other callers of
    cpu_physical_memory_set_dirty_range_nocode, so leave it alone.
    Just one nit: now that invalidate_and_set_dirty takes care of handling
    multiple pages, there is no need for address_space_unmap to wrap it
    in a loop.  In fact that loop would now be O(n^2).
    Reported-by: Dave Gilbert <dgilbert@xxxxxxxxxx>
    Reviewed-by: Michael S. Tsirkin <mst@xxxxxxxxxx>
    Tested-by: Gerd Hoffmann <kraxel@xxxxxxxxxx>
    Signed-off-by: Paolo Bonzini <pbonzini@xxxxxxxxxx>

Xen-devel mailing list



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