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

[Xen-devel] [libvirt test] 30630: trouble: blocked/broken/fail/pass

flight 30630 libvirt real [real]

Failures and problems with tests :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-i386-pvops              3 host-install(3)         broken REGR. vs. 30599

Tests which did not succeed, but are not blocking:
 test-amd64-i386-libvirt       1 build-check(1)               blocked  n/a
 test-armhf-armhf-libvirt      9 guest-start                  fail   never pass
 test-amd64-amd64-libvirt      9 guest-start                  fail   never pass

version targeted for testing:
 libvirt              db6b738dde047c9b38ed41add5d00bbbdb7c5daa
baseline version:
 libvirt              34f514778ba55a0031ea21d6b3006317c1f607b5

People who touched revisions under test:
  Chen Hanxiao <chenhanxiao@xxxxxxxxxxxxxx>
  Eric Blake <eblake@xxxxxxxxxx>
  John Ferlan <jferlan@xxxxxxxxxx>
  Ján Tomko <jtomko@xxxxxxxxxx>
  Laine Stump <laine@xxxxxxxxx>

 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                                             broken
 test-amd64-amd64-libvirt                                     fail
 test-armhf-armhf-libvirt                                     fail
 test-amd64-i386-libvirt                                      blocked

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 db6b738dde047c9b38ed41add5d00bbbdb7c5daa
Author: Laine Stump <laine@xxxxxxxxx>
Date:   Wed Sep 24 04:30:04 2014 -0400

    qemu: change macvtap device MAC address in response to NIC_RX_FILTER_CHANGED

    This patch fills in the functionality of
    processNicRxFilterChangedEvent().  It now checks if it is appropriate
    to respond to the NIC_RX_FILTER_CHANGED event (based on device type
    and configuration) and takes appropriate action. Currently it checks
    if the guest interface has been configured with
    trustGuestRxFilters='yes', and if the host side device is macvtap. If
    so, and the MAC address on the guest has changed, the MAC address of
    the macvtap device is changed to match.

    The result of this is that networking from the guest will continue to
    work if the mac address of a macvtap-connected network device is
    changed from within the guest, as long as trustGuestRxFilters='yes'
    (previously changing the MAC address in the guest would break

commit b6bdda458ab08353dc2b664d026de6322c7db680
Author: Laine Stump <laine@xxxxxxxxx>
Date:   Wed Sep 17 13:07:50 2014 -0400

    qemu: setup infrastructure to handle NIC_RX_FILTER_CHANGED event

    NIC_RX_FILTER_CHANGED is sent by qemu any time a NIC driver in the
    guest modified the NIC's RX Filter (for example, if the MAC address of
    the NIC is changed by the guest).

    This patch doesn't do anything useful with that event; it just sets up
    all the plumbing to get news of the event into a worker thread with
    all proper locking/reference counting, and provide an easy place to
    add in desired functionality.

    See src/qemu/EVENTHANDLERS.txt for information/instructions on adding
    a libvirt-internal handler for a qemu event (using
    NIC_RX_FILTER_CHANGED as an example).

commit ac4f8be422521875b64f51bcea953a6d1c6bfb09
Author: Laine Stump <laine@xxxxxxxxx>
Date:   Thu Oct 2 11:46:30 2014 -0400

    qemu: add short document on qemu event handlers

    This text was in the commit log for the patch that added the event
    handler for NIC_RX_FILTER_CHANGED, and John Ferlan expressed a desire
    that the information not be "lost", so I've put it into a file in the
    qemu directory, hoping that it might catch the attention of future
    writers of handlers for qemu events.

commit ab989962d4c2ef9045a9b8344b8e6f4094027c7c
Author: Laine Stump <laine@xxxxxxxxx>
Date:   Mon Sep 22 12:19:41 2014 -0400

    qemu: qemuMonitorQueryRxFilter - retrieve guest netdev rx-filter

    This function can be called at any time to get the current status of a
    guest's network device rx-filter. In particular it is useful to call
    after libvirt recieves a NIC_RX_FILTER_CHANGED event - this event only
    tells you that something has changed in the rx-filter, the details are
    retrieved with the query-rx-filter monitor command (only available in
    the json monitor). The command sent to the qemu monitor looks like this:

      {"execute":"query-rx-filter", "arguments": {"name":"net2"} }'

    and the results will look something like this:

        "return": [
                "promiscuous": false,
                "name": "net2",
                "main-mac": "52:54:00:98:2d:e3",
                "unicast": "normal",
                "vlan": "normal",
                "vlan-table": [
                "unicast-table": [

                "multicast": "normal",
                "multicast-overflow": false,
                "unicast-overflow": false,
                "multicast-table": [
                "broadcast-allowed": false
        "id": "libvirt-14"

    This is all parsed from JSON into a virNetDevRxFilter object for
    easier consumption. (unicast-table is usually empty, but is also an
    array of mac addresses similar to multicast-table).

    (NB: LIBNL_CFLAGS was added to tests/Makefile.am because virnetdev.h
    now includes util/virnetlink.h, which includes netlink/msg.h when
    appropriate. Without LIBNL_CFLAGS, gcc can't find that file (if
    libnl/netlink isn't available, LIBNL_CFLAGS will be empty and
    virnetlink.h won't try to include netlink/msg.h anyway).)

commit aa7c595a31d11e019ee7c6bdf59e52bba41d066e
Author: Laine Stump <laine@xxxxxxxxx>
Date:   Sat Sep 20 14:39:44 2014 -0400

    util: define virNetDevRxFilter and basic utility functions

    This same structure will be used to retrieve RX filter info for
    interfaces on the host via netlink messages, and RX filter info for
    interfaces on the guest via the qemu "query-rx-filter" command.

commit cfddf59cee42a74f327b358a78c9663cd21364f0
Author: Laine Stump <laine@xxxxxxxxx>
Date:   Tue Sep 23 14:54:16 2014 -0400

    network: set interface actual trustGuestRxFilters from network/portgroup

    As is done with other items such as vlan, virtualport, and bandwidth,
    set the actual trustGuestRxFilters value to be used by a domain
    interface according to a merge of the same attribute in the interface,
    portgroup, and network in use. the interface setting always takes
    precedence (if specified), followed by portgroup, and finally the
    setting in the network is used if it's not specified in the interface
    or portgroup.

commit 07450cd42951d5007ab28d8e522f65d948181674
Author: Laine Stump <laine@xxxxxxxxx>
Date:   Tue Sep 23 14:19:08 2014 -0400

    conf: add trustGuestRxFilters attribute to network and domain interface

    This new attribute will control whether or not libvirt will pay
    attention to guest notifications about changes to network device mac
    addresses and receive filters. The default for this is 'no' (for
    security reasons). If it is set to 'yes' *and* the specified device
    model and connection support it (currently only macvtap+virtio) then
    libvirt will watch for NIC_RX_FILTER_CHANGED events, and when it
    receives one, it will issue a query-rx-filter command, retrieve the
    result, and modify the host-side macvtap interface's mac address and
    unicast/multicast filters accordingly.

    The functionality behind this attribute will be in a later patch. This
    patch merely adds the attribute to the top-level of a domain's
    <interface> as well as to <network> and <portgroup>, and adds
    documentation and schema/xml2xml tests. Rather than adding even more
    test files, I've just added the net attribute in various applicable
    places of existing test files.

commit b7890a8c28f79e958e5146c85e366f1c69ca1304
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Wed Sep 24 08:30:09 2014 -0400

    qemu: Remove possible NULL deref in debug output

    Check for !dev->info.alias was done after a VIR_DEBUG() statement
    that already tried to print - just flip sequence

commit 99186c4103cf1e035fed1de6baa575edac9ed53a
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Wed Sep 24 08:31:32 2014 -0400

    qemu: Remove need for virConnectPtr in hotunplug detach host, net

    Prior patch removed the need for the virConnectPtr in the unplug
    detach host path which caused ripple effect to remove in multiple
    callers.  The previous patch just left things as ATTRIBUTE_UNUSED -
    this patch will remove the variable.

commit d2774e54cde2377c78a7572eb3fec0a663e5017f
Author: John Ferlan <jferlan@xxxxxxxxxx>
Date:   Tue Sep 23 18:53:25 2014 -0400

    qemu: Fix hot unplug of SCSI_HOST device


    Introduced by commit id '8f76ad99' the logic to detach a scsi_host
    device (SCSI or iSCSI) fails when attempting to remove the 'drive'
    because as I found in my investigation - the DelDevice takes care of
    that for us.

    The investigation turned up commits to adjust the logic for the
    qemuMonitorDelDevice and qemuMonitorDriveDel processing for interfaces
    (commit id '81f76598'), disk bus=VIRTIO,SCSI,USB (commit id '0635785b'),
    and chr devices (commit id '55b21f9b'), but nothing with the host devices.

    This commit uses the model for the previous set of changes and applies
    it to the hostdev path. The call to qemuDomainDetachHostSCSIDevice will
    return to qemuDomainDetachThisHostDevice handling either the audit of
    the failure or the wait for the removal and then call into
    qemuDomainRemoveHostDevice for the event, removal from the domain hostdev
    list, and audit of the removal similar to other paths.

    NOTE: For now the 'conn' param to +qemuDomainDetachHostSCSIDevice is left
    as ATTRIBUTE_UNUSED.  Removing requires a cascade of other changes to be
    left for a future patch.

commit 9d31c0487c0b2ec4f21ada489041e73658ef8d53
Author: Eric Blake <eblake@xxxxxxxxxx>
Date:   Mon Oct 6 08:23:47 2014 -0600

    maint: update .mailmap

    Consolidate several commits made by James:

    Signed-off-by: Eric Blake <eblake@xxxxxxxxxx>

commit 16ca322630e6aac5493735ea7367526d4d517b73
Author: Ján Tomko <jtomko@xxxxxxxxxx>
Date:   Wed Oct 1 14:46:54 2014 +0200

    Include .libs in libdir in source tree pkg-config files

    This lets me build against an uninstalled source tree without

commit 906eefb2e997e516617fb059b16ebaded6164a92
Author: Chen Hanxiao <chenhanxiao@xxxxxxxxxxxxxx>
Date:   Mon Oct 6 17:28:40 2014 +0800

    docs: fix a typo in drvlxc


    Signed-off-by: Chen Hanxiao <chenhanxiao@xxxxxxxxxxxxxx>

Xen-devel mailing list



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