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

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

flight 33443 libvirt real [real]

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-i386-libvirt            5 libvirt-build             fail REGR. vs. 33422
 build-armhf-libvirt           5 libvirt-build             fail REGR. vs. 33422
 build-amd64-libvirt           5 libvirt-build             fail REGR. vs. 33422

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

version targeted for testing:
 libvirt              dd69a14f90b4bde9c07a6ef594914323874a26ce
baseline version:
 libvirt              ce745914b33e3f9a136d91655600b931e7a4178f

People who touched revisions under test:
  Daniel P. Berrange <berrange@xxxxxxxxxx>
  Jim Fehlig <jfehlig@xxxxxxxx>
  Jiri Denemark <jdenemar@xxxxxxxxxx>
  Ján Tomko <jtomko@xxxxxxxxxx>
  Kiarie Kahurani <davidkiarie4@xxxxxxxxx>
  Luyao Huang <lhuang@xxxxxxxxxx>
  Michal Privoznik <mprivozn@xxxxxxxxxx>
  Shivaprasad G Bhat <sbhat@xxxxxxxxxxxxxxxxxx>
  Shivaprasad G Bhat <shivaprasadbhat@xxxxxxxxx>

 build-amd64                                                  pass
 build-armhf                                                  pass
 build-i386                                                   pass
 build-amd64-libvirt                                          fail
 build-armhf-libvirt                                          fail
 build-i386-libvirt                                           fail
 build-amd64-pvops                                            pass
 build-armhf-pvops                                            pass
 build-i386-pvops                                             pass
 test-amd64-amd64-libvirt                                     blocked
 test-armhf-armhf-libvirt                                     blocked
 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 dd69a14f90b4bde9c07a6ef594914323874a26ce
Author: Daniel P. Berrange <berrange@xxxxxxxxxx>
Date:   Tue Nov 18 17:34:42 2014 +0000

    Add support for schema validation when passing in XML

    The virDomainDefineXMLFlags and virDomainCreateXML APIs both
    gain new flags allowing them to be told to validate XML.
    This updates all the drivers to turn on validation in the
    XML parser when the flags are set

commit 6d06b0d89bfeec8c9e04d99bf7b9fc430ed25d37
Author: Daniel P. Berrange <berrange@xxxxxxxxxx>
Date:   Tue Nov 18 14:50:05 2014 +0000

    Add virXMLValidateAgainstSchema helper method

    Add a helper method that can validate an XML document against
    an RNG schema

commit c5b6a4a5cb5ae5cf387c363d84f4b7b21e7fc6fa
Author: Daniel P. Berrange <berrange@xxxxxxxxxx>
Date:   Wed Nov 12 15:42:02 2014 +0000

    Change int to size_t in size var for tap/vhost FDs

    A number of methods take an int for a parameter that indicates
    the size of an array. The correct type for array sizes is

commit d654bc419017cc7cb4376c0b93debfeb02511628
Author: Daniel P. Berrange <berrange@xxxxxxxxxx>
Date:   Tue Nov 11 18:40:16 2014 +0000

    Log dtrace/systemd probes at INFO level instead of DEBUG

    Every dtrace/systemd probe also include a libvirt log message.
    These are logged at level DEBUG currently, which means if you
    want to see all probes they are drowned by the rest of the
    DEBUG messages. Since we don't really use the INFO log level
    for much, it seems reasonable to suggest we log all probes at
    level INFO.

commit d83ce91fd4492c9267ffd2516dc24418b170a572
Author: Daniel P. Berrange <berrange@xxxxxxxxxx>
Date:   Tue Nov 11 18:39:19 2014 +0000

    Add systemd/dtrace probes for DBus APIs

    When debugging libvirt it is helpful to set probes around RPC
    calls. We already have probes for libvirt's native RPC layer,
    so it makes sense to add them for the DBus RPC layer too.

commit 318df5a05f35ceda70822c5f56ac93e21bbfe691
Author: Daniel P. Berrange <berrange@xxxxxxxxxx>
Date:   Tue Nov 11 17:38:43 2014 +0000

    Add support for systemd-machined CreateMachineWithNetwork

    systemd-machined introduced a new method CreateMachineWithNetwork
    that obsoletes CreateMachine. It expects to be given a list of
    VETH/TAP device indexes for the host side device(s) associated
    with a container/machine.

    This falls back to the old CreateMachine method when the new
    one is not supported.

commit 503527919807b03c4e7b5bcf1aef92fa7b3eafb6
Author: Luyao Huang <lhuang@xxxxxxxxxx>
Date:   Tue Jan 13 10:15:52 2015 +0800

    qemu: free priv->origname when qemuMigrationPrepareAny fails


    When we meet error in qemuMigrationPrepareAny and goto
    cleanup with rc < 0, we forget clear the priv->origname and this
    will make this vm migrate fail next time because leave a wrong
    origname in  priv, and will Generate a wrong cookie when do
    migrate next time.

    This patch will make priv->origname is NULL when migrate fail
    in target host.

    Signed-off-by: Luyao Huang <lhuang@xxxxxxxxxx>
    Signed-off-by: Jiri Denemark <jdenemar@xxxxxxxxxx>

commit c749eda4a2220cddb24467fbbcf22c9b7917b8a2
Author: Ján Tomko <jtomko@xxxxxxxxxx>
Date:   Wed Jan 7 14:50:34 2015 +0100

    Fix vmdef usage while in monitor in qemu process

    Make local copy of the disk alias in qemuProcessInitPasswords,
    instead of referencing the one in domain definition, which
    might get freed if the domain crashes while we're in monitor.

    Also copy the memballoon period value.

commit 3f2139843760e6d5596b75db9df6af8c6e9c1ee6
Author: Ján Tomko <jtomko@xxxxxxxxxx>
Date:   Wed Jan 7 14:35:49 2015 +0100

    Fix vmdef usage while in monitor in BlockStat* APIs

    Make a local copy of the disk alias instead of pointing
    to the domain definition, which might get freed if
    the domain dies while we're in monitor.

    Also exit early if that happens.

commit 051add2ff90f7b7f821e274fd318e1d845144157
Author: Ján Tomko <jtomko@xxxxxxxxxx>
Date:   Tue Dec 16 09:30:49 2014 +0100

    Fix vmdef usage while in monitor in qemuDomainHotplugVcpus

    Exit the monitor right after we've done with it to get
    the virDomainObjPtr lock back, otherwise we might be accessing
    vm->def while it's being cleaned up by qemuProcessStop.

    If the domain crashed while we were in the monitor, exit
    early instead of changing vm->def which is now the persistent

commit a5e5996b91129130863be8b5608d47d0ef01e326
Author: Ján Tomko <jtomko@xxxxxxxxxx>
Date:   Tue Dec 16 08:46:44 2014 +0100

    Mark the domain as active in qemuhotplugtest

    This will allow us to call qemuDomainObjIsActive() in
    the tested functions to check if the domain has crashed.

commit dc2fd51fd727bbb6de172e0ca4b7dd307bb99180
Author: Ján Tomko <jtomko@xxxxxxxxxx>
Date:   Fri Dec 12 16:57:21 2014 +0100

    Check for domain liveness in qemuDomainObjExitMonitor

    The domain might disappear during the time in monitor when
    the virDomainObjPtr is unlocked, so the caller needs to check
    if it's still alive.

    Since most of the callers are going to need it, put the
    check inside qemuDomainObjExitMonitor and return -1 if
    the domain died in the meantime.

commit 7e72de49fe63f3c4892b26002928252d45cc3822
Author: Shivaprasad G Bhat <shivaprasadbhat@xxxxxxxxx>
Date:   Wed Jan 14 06:03:28 2015 -0500

    check IOMMU group devices usage when preparing device for vfio passthrough

    The virsh start <domain> fails with qemu error when the hostdevices of the
    same iommu group are used actively by other vms. It is not clear which
    hostdev from the same iommu group is used by any of the running guests.
    User has to go through every guest xml to figure out who is using the
    hostdev of same iommu group.

    Iterate the iommu group of the hostdev and error our neatly in case a
    device in the same iommu group is busy. Reattach code also does the same
    kind of check, remove duplicate code as well.

    Signed-off-by: Shivaprasad G Bhat <sbhat@xxxxxxxxxxxxxxxxxx>
    Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit 6af9bb35608e8b14533e973cd46abfc17d516d77
Author: Shivaprasad G Bhat <shivaprasadbhat@xxxxxxxxx>
Date:   Wed Jan 14 06:02:40 2015 -0500

    virpci: Implement virPCIDeviceGetAddress function

    Basically a getter function which is implemented for accessing the
    address fields in virPCIDevice.

    Signed-off-by: Shivaprasad G Bhat <sbhat@xxxxxxxxxxxxxxxxxx>
    Signed-off-by: Michal Privoznik <mprivozn@xxxxxxxxxx>

commit cec71a6ba6d733b1c1a3fa4f3dcb252d0cb5bfd0
Author: Kiarie Kahurani <davidkiarie4@xxxxxxxxx>
Date:   Mon Dec 15 21:30:06 2014 -0700

    libxl: Add support for parsing/formating Xen XL config

    Now that xenconfig supports parsing and formatting Xen's
    XL config format, integrate it into the libxl driver's
    connectDomainXML{From,To}Native functions.

    Signed-off-by: Kiarie Kahurani <davidkiarie4@xxxxxxxxx>
    Signed-off-by: Jim Fehlig <jfehlig@xxxxxxxx>

commit 4ed5fb91934cbad53cc4128030869f4b46e0811d
Author: Kiarie Kahurani <davidkiarie4@xxxxxxxxx>
Date:   Mon Dec 15 21:30:05 2014 -0700

    tests: Tests for the xen-xl parser

    Add disk and spice config tests for the xen_xl config parser

    Signed-off-by: Kiarie Kahurani <davidkiarie4@xxxxxxxxx>
    Signed-off-by: Jim Fehlig <jfehlig@xxxxxxxx>

commit 4689cdf779066861116995085a6424fe3c50f64a
Author: Jim Fehlig <jfehlig@xxxxxxxx>
Date:   Fri Jan 9 17:12:52 2015 -0700

    Introduce support for parsing/formatting Xen xl config format

    Introduce a parser/formatter for the xl config format.  Since the
    deprecation of xm/xend, the VM config file format has diverged as
    new features are added to libxl.  This patch adds support for parsing
    and formating the xl config format.  It supports the existing xm config
    format, plus adds support for spice graphics and xl disk config syntax.

    Disk config is specified a bit differently in xl as compared to xm.  In
    xl, disk config consists of comma-separated positional parameters and
    keyword/value pairs separated by commas. Positional parameters are
    specified as follows

       target, format, vdev, access

    Supported keys for key=value options are

      devtype, backendtype

    The positional paramters can also be specified in key/value form.  For
    example the following xl disk config are equivalent

        format=raw, vdev=hda, access=rw, target=/dev/vg/guest-volume

    See $xen_sources/docs/misc/xl-disk-configuration.txt for more details.

    xl disk config is parsed with the help of xlu_disk_parse() from
    libxlutil, libxl's utility library.  Although the library exists
    in all Xen versions supported by the libxl virt driver, only
    recently has the corresponding header file been included.  A check
    for the header is done in configure.ac.  If not found, xlu_disk_parse()
    is declared externally.

    Signed-off-by: Kiarie Kahurani <davidkiarie4@xxxxxxxxx>
    Signed-off-by: Jim Fehlig <jfehlig@xxxxxxxx>

Xen-devel mailing list



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