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

[Xen-devel] [libvirt test] 113873: regressions - FAIL

flight 113873 libvirt real [real]

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-armhf-armhf-libvirt      7 xen-boot                 fail REGR. vs. 113851

Tests which did not succeed, but are not blocking:
 test-armhf-armhf-libvirt-xsm 14 saverestore-support-check    fail  like 113851
 test-armhf-armhf-libvirt-raw 13 saverestore-support-check    fail  like 113851
 test-amd64-amd64-libvirt     13 migrate-support-check        fail   never pass
 test-amd64-i386-libvirt-xsm  13 migrate-support-check        fail   never pass
 test-amd64-i386-libvirt      13 migrate-support-check        fail   never pass
 test-amd64-amd64-libvirt-xsm 13 migrate-support-check        fail   never pass
 test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check 
fail never pass
 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 11 migrate-support-check 
fail never pass
 test-amd64-i386-libvirt-qcow2 12 migrate-support-check        fail  never pass
 test-amd64-amd64-libvirt-vhd 12 migrate-support-check        fail   never pass
 test-armhf-armhf-libvirt-xsm 13 migrate-support-check        fail   never pass
 test-armhf-armhf-libvirt-raw 12 migrate-support-check        fail   never pass

version targeted for testing:
 libvirt              5c52aed174b386f897fce870b2453e6cee5ebbc3
baseline version:
 libvirt              01f86fb301a55c15c33dd02e6a7e2aac5ecad93d

Last test of basis   113851  2017-09-27 04:20:16 Z    1 days
Testing same since   113873  2017-09-28 04:28:32 Z    0 days    1 attempts

People who touched revisions under test:
  Erik Skultety <eskultet@xxxxxxxxxx>
  John Ferlan <jferlan@xxxxxxxxxx>
  Ján Tomko <jtomko@xxxxxxxxxx>
  Pavel Hrdina <phrdina@xxxxxxxxxx>
  Peter Krempa <pkrempa@xxxxxxxxxx>
  ZhiPeng Lu <lu.zhipeng@xxxxxxxxxx>

 build-amd64-xsm                                              pass    
 build-armhf-xsm                                              pass    
 build-i386-xsm                                               pass    
 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-libvirt-qemuu-debianhvm-amd64-xsm           pass    
 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm            pass    
 test-amd64-amd64-libvirt-xsm                                 pass    
 test-armhf-armhf-libvirt-xsm                                 pass    
 test-amd64-i386-libvirt-xsm                                  pass    
 test-amd64-amd64-libvirt                                     pass    
 test-armhf-armhf-libvirt                                     fail    
 test-amd64-i386-libvirt                                      pass    
 test-amd64-amd64-libvirt-pair                                pass    
 test-amd64-i386-libvirt-pair                                 pass    
 test-amd64-i386-libvirt-qcow2                                pass    
 test-armhf-armhf-libvirt-raw                                 pass    
 test-amd64-amd64-libvirt-vhd                                 pass    

sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images

Logs, config files, etc. are available at

Explanation of these reports, and of osstest in general, is at

Test harness code can be found at

Not pushing.

commit 5c52aed174b386f897fce870b2453e6cee5ebbc3
Author: Pavel Hrdina <phrdina@xxxxxxxxxx>
Date:   Tue Sep 26 16:47:20 2017 +0200

    rpc: for messages with FDs always decode count of FDs from the message
    The packet with passed FD has the following format:
        | len | header | payload |
    where "payload" has an additional count of FDs before the actual data:
        | nfds | payload |
    When the packet is received we parse the "header", which as a side
    effect updates msg->bufferOffset to point to the beginning of "payload".
    If the message call contains FDs, we need to also parse the count of
    FDs, which also updates the msg->bufferOffset.
    The issue here is that when we attempt to read the FDs data from the
    socket and we receive EAGAIN we finish the reading and call poll()
    to wait for the data the we need.  When the data arrives we already have
    the packet in our buffer so we read the "header" again but this time
    we don't read the count of FDs because we already have it stored.
    That means that the msg->bufferOffset is not updated to point to the
    actual beginning of the payload data, but it points to the count of
    FDs.  After all FDs are processed we dispatch the message to process
    it and decode the payload.  Since the msg->bufferOffset points to wrong
    data, we decode the wrong payload and the API call fails with
    error messages:
        Domain not found: no domain with matching uuid 
'67656e65-7269-6300-0c87-5003ca6941f2' ()
    Broken by commit 133c511b527 which fixed a FD and memory leak.
    Signed-off-by: Pavel Hrdina <phrdina@xxxxxxxxxx>

commit 3685e2dd64f8565d739953bde871860f343436e4
Author: Peter Krempa <pkrempa@xxxxxxxxxx>
Date:   Wed Aug 23 14:19:36 2017 +0200

    qemu: domain: Extract common clearing of VM private data
    VM private data is cleared when the VM is turned off and also when the
    VM object is being freed. Some of the clearing code was duplicated.
    Extract it to a separate function.
    This also removes the now unnecessary function

commit f54f32740fd3c7d1fbb9742a13b83694738cecc2
Author: Erik Skultety <eskultet@xxxxxxxxxx>
Date:   Wed Sep 27 15:08:53 2017 +0200

    docs: Add the closing </address> tag for mdev example
    Signed-off-by: Erik Skultety <eskultet@xxxxxxxxxx>

commit 959fe7de1f0f6fadb86e853edead6d32c3cb3559
Author: Ján Tomko <jtomko@xxxxxxxxxx>
Date:   Tue Aug 16 12:29:05 2016 +0200

    Shrink volume even with ALLOCATE flag
    Calling fallocate on the new (smaller) capacity ensures
    that the whole file is allocated, but it does not reduce
    the file size.
    Also call ftruncate after fallocate.

commit 3f702f5ab1d8cfcfa41a49aa7f6e3881242d5f0f
Author: Ján Tomko <jtomko@xxxxxxxxxx>
Date:   Mon Sep 25 16:35:42 2017 +0200

    virStorageFileResize: fallocate the whole capacity
    We have been trying to implement the ALLOCATE flag to mean
    "the volume should be fully allocated after the resize".
    Since commit b0579ed9 we do not allocate from the existing
    capacity, but from the existing allocation value.
    However this value is a total of all the allocated bytes,
    not an offset.
    For a sparsely allocated file:
    $ perl -e 'print "x"x8192;' > vol1
    $ fallocate -p -o 0 -l 4096 vol1
    $ virsh vol-info vol1 default
    Capacity:       8.00 KiB
    Allocation:     4.00 KiB
    Treating allocation as an offset would result in an incompletely
    allocated file:
    $ virsh vol-resize vol1 --pool default 16384 --allocate
    Capacity:       16.00 KiB
    Allocation:     12.00 KiB
    Call fallocate from zero on the whole requested capacity to fully
    allocate the file. After that, the volume is fully allocated
    after the resize:
    $ virsh vol-resize vol1 --pool default 16384 --allocate
    $ virsh vol-info vol1 default
    Capacity:       16.00 KiB
    Allocation:     16.00 KiB

commit 5463d9596903b370e7d078eeacb0e3f3c71c526f
Author: Ján Tomko <jtomko@xxxxxxxxxx>
Date:   Mon Sep 25 16:29:34 2017 +0200

    use virFileAllocate in virStorageFileResize
    Introduce a new function virFileAllocate that will call the
    non-destructive variants of safezero, essentially reverting
    my commit 1390c268
        safezero: fall back to writing zeroes even when resizing
    back to the state as of commit 18f0316
        virstoragefile: Have virStorageFileResize use safezero
    This means that _ALLOCATE flag will no longer work on platforms
    without the allocate syscalls, but it will not overwrite data

commit 63d3d895a2c00a849440706b3daa7199296b4b33
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Tue Sep 5 13:44:15 2017 -0400

    virsh: Add/allow secret-uuid for pool-{define|create}-as
    For the virsh pool-{define|create}-as command, let's allow using
    --secret-uuid on the command line as an alternative to --secret-usage
    (added for commit id '8932580'), but ensure that they are mutually

commit d957e2366334c467fa8adf2f11738a2032b2c06e
Author: ZhiPeng Lu <lu.zhipeng@xxxxxxxxxx>
Date:   Wed Sep 27 09:01:39 2017 +0800

    nwfilter: Fix memory leak in learnIPAddressThread
    Don't leak @inetaddr within the done: processing when attempting
    to instantiate the filter.
    Signed-off-by: ZhiPeng Lu <lu.zhipeng@xxxxxxxxxx>

commit 7e2086257602a4726e7affd2806f4f984ea6287d
Author: ZhiPeng Lu <lu.zhipeng@xxxxxxxxxx>
Date:   Wed Sep 27 16:53:50 2017 +0800

    nwfilter: Fix memory leak in virNWFilterIPAddrMapAddIPAddr
    If virNWFilterHashTablePut fails, then the @val was leaked.
    Signed-off-by: ZhiPeng Lu <lu.zhipeng@xxxxxxxxxx>

commit 955caf171c0370cf4a32eec9a18aca2b653e6b82
Author: Ján Tomko <jtomko@xxxxxxxxxx>
Date:   Tue Sep 26 13:56:36 2017 +0200

    qemu: fix hotplug of udp device with no connect host
    Use an empty string to let qemu fill out the default.
    This matches what's done in qemuBuildChrChardevStr.
    Signed-off-by: Ján Tomko <jtomko@xxxxxxxxxx>
    Reviewed-by: John Ferlan <jferlan@xxxxxxxxxx>

commit 80740d9c66e377903adb553094f76944b4bd0dfd
Author: Pavel Hrdina <phrdina@xxxxxxxxxx>
Date:   Wed Sep 20 15:59:18 2017 +0200

    Revert "vhost-user: add support reconnect for vhost-user ports"
    This reverts commit edaf4ebe95a5995585c8ab7bc5b92887286d4431.
    This uses "reconnect" as attribute for <source> element, but we already
    have a <reconnect> element for <source> element for chardev devices.
    Since this is the same feature for different device it should be
    presented in XML the same way.
    Signed-off-by: Pavel Hrdina <phrdina@xxxxxxxxxx>

commit 4b480d10768c7a288c10e2e39f6a2bf275a0eb69
Author: Peter Krempa <pkrempa@xxxxxxxxxx>
Date:   Mon Sep 25 16:16:08 2017 +0200

    qemu: process: Refresh data from qemu monitor after migration
    Some values we read from the qemu monitor may be changed with the actual
    state by the incoming migration. This means that we should refresh
    certain things only after the migration has finished.
    This is mostly visible in the cdrom tray state, which is by default
    closed but may be opened by the guest OS. This would be refreshed before
    qemu transferred the actual state and thus libvirt would think that the
    tray is closed.
    Note that this patch moves only a few obvious query commands. Others may
    be moved later after individual assessment.
    Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1463168

commit cf30a8cabd5943992e30c45efdd5fd7b82dd53cc
Author: Peter Krempa <pkrempa@xxxxxxxxxx>
Date:   Mon Sep 25 22:34:44 2017 +0200

    qemu: hotplug: Ignore cgroup errors when hot-unplugging vcpus
    When the vcpu is successfully removed libvirt would remove the cgroup.
    In cases when removal of the cgroup fails libvirt would report an error.
    This does not make much sense, since the vcpu was removed and we can't
    really do anything with the cgroup. This patch silences the errors from
    cgroup removal.
    Resolves: https://bugzilla.redhat.com/show_bug.cgi?id=1462092

Xen-devel mailing list



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