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

[seabios baseline-only test] 71557: regressions - FAIL

This run is configured for baseline tests only.

flight 71557 seabios real [real]

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 build-amd64-libvirt           5 libvirt-build             fail REGR. vs. 71250
 build-i386-libvirt            5 libvirt-build             fail REGR. vs. 71250
 test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm 14 guest-saverestore.2 fail 
REGR. vs. 71250
 test-amd64-i386-xl-qemuu-win7-amd64 15 guest-localmigrate/x10 fail REGR. vs. 

Regressions which are regarded as allowable (not blocking):
 test-amd64-amd64-xl-qemuu-win7-amd64 15 guest-localmigrate/x10 fail like 71250
 test-amd64-amd64-xl-qemuu-winxpsp3 17 guest-start/win.repeat   fail like 71250
 test-amd64-i386-xl-qemuu-winxpsp3-vcpus1  9 windows-install    fail like 71250

Tests which did not succeed, but are not blocking:
 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 1 build-check(1) blocked n/a
 test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 1 build-check(1) blocked n/a
 test-amd64-amd64-qemuu-nested-amd 16 debian-hvm-install/l1/l2  fail never pass

version targeted for testing:
 seabios              58953eb793b7f43f9cbb72bd7802922746235266
baseline version:
 seabios              3fdabaee7d4c36231fe2f052b2d3464dba690acc

Last test of basis    71250  2017-05-03 20:20:55 Z   40 days
Testing same since    71557  2017-06-13 06:20:39 Z    0 days    1 attempts

People who touched revisions under test:
  Kevin O'Connor <kevin@xxxxxxxxxxxx>
  Roman Kagan <rkagan@xxxxxxxxxxxxx>

 build-amd64-xsm                                              pass    
 build-i386-xsm                                               pass    
 build-amd64                                                  pass    
 build-i386                                                   pass    
 build-amd64-libvirt                                          fail    
 build-i386-libvirt                                           fail    
 build-amd64-pvops                                            pass    
 build-i386-pvops                                             pass    
 test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm           blocked 
 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm            blocked 
 test-amd64-amd64-xl-qemuu-debianhvm-amd64-xsm                fail    
 test-amd64-i386-xl-qemuu-debianhvm-amd64-xsm                 pass    
 test-amd64-amd64-qemuu-nested-amd                            fail    
 test-amd64-i386-qemuu-rhel6hvm-amd                           pass    
 test-amd64-amd64-xl-qemuu-debianhvm-amd64                    pass    
 test-amd64-i386-xl-qemuu-debianhvm-amd64                     pass    
 test-amd64-amd64-xl-qemuu-win7-amd64                         fail    
 test-amd64-i386-xl-qemuu-win7-amd64                          fail    
 test-amd64-amd64-qemuu-nested-intel                          pass    
 test-amd64-i386-qemuu-rhel6hvm-intel                         pass    
 test-amd64-i386-xl-qemuu-winxpsp3-vcpus1                     fail    
 test-amd64-amd64-xl-qemuu-winxpsp3                           fail    
 test-amd64-i386-xl-qemuu-winxpsp3                            pass    

sg-report-flight on osstest.xs.citrite.net
logs: /home/osstest/logs
images: /home/osstest/images

Logs, config files, etc. are available at

Test harness code can be found at

Push not applicable.

commit 58953eb793b7f43f9cbb72bd7802922746235266
Author: Roman Kagan <rkagan@xxxxxxxxxxxxx>
Date:   Thu Jun 8 12:58:08 2017 +0300

    Revert "lsi-scsi: reset in case of a serious problem"
    This reverts commit 11277846e819b9eef3db5ac833a6a47f95f5ef15.
    It was originally introduced to deal with the case when REPORT_LUNS
    caused an error in QEMU implementation of lsi53c895a and left it in a
    "confused" state making further interaction impossible.
    However the remedy was worse than the disease: the reset was
    controller-wide causing all luns to reset, losing all in-flight requests;
    upon that all luns lit up unit_attention condition, so that any
    non-informational request would fail with check_condition status.  As a
    result, the lun enumeration succeeded and I saw the respective entries
    in the boot menu during my testing, but the read from those luns ended
    with an error and booting failed, which I didn't bother to test.
    So this reverts to the original error handling behavior.  The problem
    with the failing REPORT_LUNS is addressed in the preceding patch, by
    making it unlikely to fail.
    Reported-by: Maciej Józefczyk <maciej.jozefczyk@xxxxxxxxxxxx>
    Signed-off-by: Roman Kagan <rkagan@xxxxxxxxxxxxx>

commit 6345621ded7fe999084501ba9382913b079acc9c
Author: Roman Kagan <rkagan@xxxxxxxxxxxxx>
Date:   Thu Jun 8 12:58:07 2017 +0300

    blockcmd: start REPORT_LUNS with the smallest buffer
    A number of emulated SCSI devices in QEMU incorrectly return an error
    to REPORT_LUNS command when the size of the data returned is smaller
    than the allocation length passed in.
    To work it around, start with the smallest allocation length possible:
    for 1 entry.  This is a slight pessimization because it would require
    another REPORT_LUNS iteration if the target has more than a single LUN,
    but this appears to have negligible impact on boot times, and makes
    REPORT_LUNS enumeration work for more QEMU devices (lsi53c895a,
    Reported-by: Maciej Józefczyk <maciej.jozefczyk@xxxxxxxxxxxx>
    Signed-off-by: Roman Kagan <rkagan@xxxxxxxxxxxxx>

commit dee3c1535d5550fab914cd181cbb02741d749e2a
Author: Kevin O'Connor <kevin@xxxxxxxxxxxx>
Date:   Tue May 16 11:59:10 2017 -0400

    stacks: There is no need to disable NMI if it is already disabled
    Don't write to the cmos index port on a mode switch if NMI is already
    disabled.  This reduces the number of outb() calls.
    Signed-off-by: Kevin O'Connor <kevin@xxxxxxxxxxxx>

commit 8ebb33b1588d6be4241a70e7daabdab4eb076cd8
Author: Kevin O'Connor <kevin@xxxxxxxxxxxx>
Date:   Tue May 16 11:47:27 2017 -0400

    stacks: Don't update the A20 settings if they haven't changed
    The A20 setting is almost always enabled - only issue an outb() if the
    A20 is actually changing.  This reduces the number of outb() calls.
    Signed-off-by: Kevin O'Connor <kevin@xxxxxxxxxxxx>

commit 5869a6b58745e3e83f4b9257cf6f64216d5e61dc
Author: Kevin O'Connor <kevin@xxxxxxxxxxxx>
Date:   Tue May 16 11:36:43 2017 -0400

    stacks: Make sure to initialize Call16Data
    Initialize the Call16Data at startup - otherwise some early yield()
    calls may check for interrupts without using the preferred A20
    Signed-off-by: Kevin O'Connor <kevin@xxxxxxxxxxxx>

commit d8b308077e984d4baf852448536ae59307efd808
Author: Kevin O'Connor <kevin@xxxxxxxxxxxx>
Date:   Tue May 16 11:32:49 2017 -0400

    smm: Backup and restore A20 on an SMI based mode switch
    QEMU does not store the A20 setting in the SMM cpu environment area
    (and it does not look like real CPUs do either).  So, manually backup
    and restore A20 on a mode switch.
    Signed-off-by: Kevin O'Connor <kevin@xxxxxxxxxxxx>

commit 235a8190a05b29cb0fd2eaa3a4c9ed8cb651d96e
Author: Kevin O'Connor <kevin@xxxxxxxxxxxx>
Date:   Wed May 10 16:14:39 2017 -0400

    NVMe: Allow NVMe to be enabled on real hardware
    A couple of users have reported success with the NVMe driver on real
    hardware, so allow it to be enabled outside of QEMU.
    Signed-off-by: Kevin O'Connor <kevin@xxxxxxxxxxxx>

osstest-output mailing list



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