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

[Xen-devel] [xen-4.4-testing test] 95332: regressions - FAIL



flight 95332 xen-4.4-testing real [real]
http://logs.test-lab.xenproject.org/osstest/logs/95332/

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-amd64-xl-qemuu-debianhvm-amd64 15 guest-localmigrate/x10 fail REGR. 
vs. 95234
 test-amd64-amd64-xl-qemuu-win7-amd64 15 guest-localmigrate/x10 fail REGR. vs. 
95234
 test-armhf-armhf-xl-multivcpu  6 xen-boot                 fail REGR. vs. 95234

Regressions which are regarded as allowable (not blocking):
 test-amd64-i386-xl-qemut-win7-amd64 16 guest-stop              fail like 95234
 test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop              fail like 95234

Tests which did not succeed, but are not blocking:
 test-amd64-i386-rumpuserxen-i386  1 build-check(1)               blocked  n/a
 test-amd64-amd64-rumpuserxen-amd64  1 build-check(1)               blocked n/a
 build-amd64-rumpuserxen       6 xen-build                    fail   never pass
 test-armhf-armhf-xl-vhd       9 debian-di-install            fail   never pass
 build-i386-rumpuserxen        6 xen-build                    fail   never pass
 test-armhf-armhf-libvirt-qcow2  9 debian-di-install            fail never pass
 test-amd64-amd64-qemuu-nested-intel 16 debian-hvm-install/l1/l2 fail never pass
 test-amd64-amd64-qemuu-nested-amd 16 debian-hvm-install/l1/l2  fail never pass
 test-armhf-armhf-libvirt-raw  9 debian-di-install            fail   never pass
 test-amd64-amd64-libvirt     12 migrate-support-check        fail   never pass
 test-amd64-i386-libvirt      12 migrate-support-check        fail   never pass
 test-armhf-armhf-xl-arndale  12 migrate-support-check        fail   never pass
 test-armhf-armhf-xl-arndale  13 saverestore-support-check    fail   never pass
 test-armhf-armhf-libvirt     11 guest-start                  fail   never pass
 test-amd64-amd64-xl-qemut-win7-amd64 16 guest-stop             fail never pass
 test-armhf-armhf-xl          13 saverestore-support-check    fail   never pass
 test-armhf-armhf-xl          12 migrate-support-check        fail   never pass
 test-amd64-amd64-libvirt-vhd 11 migrate-support-check        fail   never pass
 test-armhf-armhf-xl-credit2  12 migrate-support-check        fail   never pass
 test-armhf-armhf-xl-credit2  13 saverestore-support-check    fail   never pass
 test-armhf-armhf-xl-cubietruck 12 migrate-support-check        fail never pass
 test-armhf-armhf-xl-cubietruck 13 saverestore-support-check    fail never pass
 test-amd64-i386-xend-qemut-winxpsp3 20 leak-check/check        fail never pass

version targeted for testing:
 xen                  551948806424f8b63b16b9c1bb1b2a792edc9193
baseline version:
 xen                  01311b90ced670a8025690eaa13ab461d1bc5e67

Last test of basis    95234  2016-06-03 10:52:57 Z    4 days
Testing same since    95332  2016-06-06 15:12:10 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>

jobs:
 build-amd64-xend                                             pass    
 build-i386-xend                                              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    
 build-amd64-rumpuserxen                                      fail    
 build-i386-rumpuserxen                                       fail    
 test-amd64-amd64-xl                                          pass    
 test-armhf-armhf-xl                                          pass    
 test-amd64-i386-xl                                           pass    
 test-amd64-amd64-qemuu-nested-amd                            fail    
 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                    fail    
 test-amd64-i386-xl-qemuu-debianhvm-amd64                     pass    
 test-amd64-i386-freebsd10-amd64                              pass    
 test-amd64-amd64-xl-qemuu-ovmf-amd64                         pass    
 test-amd64-i386-xl-qemuu-ovmf-amd64                          pass    
 test-amd64-amd64-rumpuserxen-amd64                           blocked 
 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-armhf-armhf-xl-arndale                                  pass    
 test-amd64-amd64-xl-credit2                                  pass    
 test-armhf-armhf-xl-credit2                                  pass    
 test-armhf-armhf-xl-cubietruck                               pass    
 test-amd64-i386-freebsd10-i386                               pass    
 test-amd64-i386-rumpuserxen-i386                             blocked 
 test-amd64-amd64-qemuu-nested-intel                          fail    
 test-amd64-i386-qemut-rhel6hvm-intel                         pass    
 test-amd64-i386-qemuu-rhel6hvm-intel                         pass    
 test-amd64-amd64-libvirt                                     pass    
 test-armhf-armhf-libvirt                                     fail    
 test-amd64-i386-libvirt                                      pass    
 test-amd64-amd64-xl-multivcpu                                pass    
 test-armhf-armhf-xl-multivcpu                                fail    
 test-amd64-amd64-pair                                        pass    
 test-amd64-i386-pair                                         pass    
 test-amd64-amd64-libvirt-pair                                pass    
 test-amd64-i386-libvirt-pair                                 pass    
 test-amd64-amd64-pv                                          pass    
 test-amd64-i386-pv                                           pass    
 test-amd64-amd64-amd64-pvgrub                                pass    
 test-amd64-amd64-i386-pvgrub                                 pass    
 test-amd64-amd64-pygrub                                      pass    
 test-armhf-armhf-libvirt-qcow2                               fail    
 test-amd64-amd64-xl-qcow2                                    pass    
 test-armhf-armhf-libvirt-raw                                 fail    
 test-amd64-i386-xl-raw                                       pass    
 test-amd64-i386-xl-qemut-winxpsp3-vcpus1                     pass    
 test-amd64-i386-xl-qemuu-winxpsp3-vcpus1                     pass    
 test-amd64-amd64-libvirt-vhd                                 pass    
 test-armhf-armhf-xl-vhd                                      fail    
 test-amd64-i386-xend-qemut-winxpsp3                          fail    
 test-amd64-amd64-xl-qemut-winxpsp3                           pass    
 test-amd64-amd64-xl-qemuu-winxpsp3                           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
    http://logs.test-lab.xenproject.org/osstest/logs

Explanation of these reports, and of osstest in general, is at
    http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
    http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master

Test harness code can be found at
    http://xenbits.xen.org/gitweb?p=osstest.git;a=summary


Not pushing.

------------------------------------------------------------
commit 551948806424f8b63b16b9c1bb1b2a792edc9193
Author: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
Date:   Tue May 3 16:31:07 2016 +0100

    libxl: Do not trust frontend for nic in getinfo
    
    libxl_device_nic_getinfo needs to examine devices without trusting
    frontend-controlled data.  So:
    
    * Use /libxl to find the backend path.
    * Parse the backend path to find the backend domid, rather than
      reading it from the frontend.
    
    This is part of XSA-175.
    
    Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
    Reviewed-by: Wei Liu <wei.liu2@xxxxxxxxxx>

commit 04e831a92bddeccbbeb2bded9d30486cfe98c02d
Author: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
Date:   Tue May 3 15:52:53 2016 +0100

    libxl: Do not trust frontend for nic in libxl_devid_to_device_nic
    
    Find the backend by reading the pointer in /libxl rather than in the
    guest's frontend area.
    
    This is part of XSA-175.
    
    Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
    Reviewed-by: Wei Liu <wei.liu2@xxxxxxxxxx>

commit 9b7d6d20bcc45d43b4b7d11e0efe0419597f64bf
Author: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
Date:   Tue May 3 16:00:20 2016 +0100

    libxl: Do not trust frontend for vtpm in getinfo
    
    libxl_device_vtpm_getinfo needs to examine devices without trusting
    frontend-controlled data.  So:
    
    * Use /libxl to find the backend path.
    * Parse the backend path to find the backend domid, rather than
      reading it from the frontend.
    
    This is part of XSA-175.
    
    Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
    Reviewed-by: Wei Liu <wei.liu2@xxxxxxxxxx>

commit 76a62af5419dc652159daf68f31164c2ef0368d7
Author: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
Date:   Tue May 3 15:58:32 2016 +0100

    libxl: Do not trust frontend for vtpm list
    
    libxl_device_vtpm_list needs to enumerate and identify devices without
    trusting frontend-controlled data.  So
    
    * Use the /libxl path to enumerate vtpms.
    * Use the /libxl path to find the corresponding backends.
    * Parse the backend path to find the backend domid.
    
    This is part of XSA-175.
    
    Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
    Reviewed-by: Wei Liu <wei.liu2@xxxxxxxxxx>

commit 0006b20136204e9341f49671b24d2fa263c0bab8
Author: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
Date:   Fri Apr 29 19:21:51 2016 +0100

    libxl: Do not trust frontend for disk in getinfo
    
    * Rename the frontend variable to `fe_path' to check we caught them all
    * Read the backend path from /libxl, rather than from the frontend
    * Parse the backend domid from the backend path, rather than reading it
      from the frontend (and add the appropriate error path and initialisation)
    
    This is part of XSA-175.
    
    Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
    Reviewed-by: Wei Liu <wei.liu2@xxxxxxxxxx>

commit 08a1d2badb73aee4f9be782b6563f310e68f2b10
Author: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
Date:   Wed Apr 27 16:08:49 2016 +0100

    libxl: Do not trust frontend for disk eject event
    
    Use the /libxl path for interpreting disk eject watch events: do not
    read the backend path out of the frontend.  Instead, use the version
    in /libxl.  That avoids us relying on the guest-modifiable
    $frontend/backend pointer.
    
    To implement this we store the path
      /libxl/$guest/device/vbd/$devid/backend
    in the evgen structure.
    
    This is part of XSA-175.
    
    Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
    Reviewed-by: Wei Liu <wei.liu2@xxxxxxxxxx>

commit 0b5c527d576ecf2415e1f5270ca3e3e720d82218
Author: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
Date:   Wed May 4 15:30:32 2016 +0100

    libxl: Do not trust frontend in libxl__device_nextid
    
    When selecting the devid for a new device, we should look in
    /libxl/device for existing devices, not in the frontend area.
    
    This is part of XSA-175.
    
    Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
    Reviewed-by: Wei Liu <wei.liu2@xxxxxxxxxx>

commit 6e86c877bc685071d8389787a7a2a5b811b26ddc
Author: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
Date:   Tue May 3 18:39:36 2016 +0100

    libxl: Do not trust frontend in libxl__devices_destroy
    
    We need to enumerate the devices we have provided to a domain, without
    trusting the guest-writeable (or, at least, guest-deletable) frontend
    paths.
    
    Instead, enumerate via, and read the backend path from, /libxl.
    
    The console /libxl path is regular, so the special case for console 0
    is not relevant any more: /libxl/GUEST/device/console/0 will be found,
    and then libxl__device_destroy will DTRT to the right frontend path.
    
    This is part of XSA-175.
    
    Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
    Reviewed-by: Wei Liu <wei.liu2@xxxxxxxxxx>

commit cbbb4d17bd80b4bfdf67c5c26d05c31bec8a4e6a
Author: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
Date:   Wed Apr 27 16:34:19 2016 +0100

    libxl: Provide libxl__backendpath_parse_domid
    
    Multiple places in libxl need to figure out the backend domid of a
    device.  This can be discovered easily by looking at the backend path,
    which always starts /local/domain/$backend_domid/.
    
    There are no call sites yet.
    
    This is part of XSA-175.
    
    Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
    Reviewed-by: Wei Liu <wei.liu2@xxxxxxxxxx>

commit e9c81e93165accc08cc91cfa283b37e4f616d6df
Author: Ian Jackson <ian.jackson@xxxxxxxxxxxxx>
Date:   Mon May 16 16:44:31 2016 +0100

    libxl: Record backend/frontend paths in /libxl/$DOMID
    
    This gives us a record of all the backends we have set up for a
    domain, which is separate from the frontends in
      /local/domain/$DOMID/device.
    
    In particular:
    
    1. A guest has write permission for the frontend path:
      /local/domain/$DOMID/device/$KIND/$DEVID
    which means that the guest can completely delete the frontend.
    (They can't recreate it because they don't have write permission
    on the containing directory.)
    
    2. A guest has write permission for the backend path recorded in the
    frontend, ie, it can write to
      /local/domain/$DOMID/device/$KIND/$DEVID/backend
    which means that the guest can break the association between
    frontend and backend.
    
    So we can't rely on iterating over the frontends to find all the
    backends, or examining a frontend to discover how a device is
    configured.
    
    So, have libxl__device_generic_add record the frontend and backend
    paths in /libxl/$DOMID/device, and have libxl__device_destroy remove
    them again.
    
    Create the containing directory /libxl/GUEST/device in
    libxl__domain_make.  The already existing xs_rm in devices_destroy_cb
    will take care of removing it.
    
    This is part of XSA-175.
    
    Backport note: Backported over 7472ced, which fixes a bug in driver
    domain teardown.
    
    Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>
    Reviewed-by: Wei Liu <wei.liu2@xxxxxxxxxx>
========================================

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel

 


Rackspace

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