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

[Xen-devel] [seabios baseline-only test] 38549: tolerable FAIL

This run is configured for baseline tests only.

flight 38549 seabios real [real]

Failures :-/ but no regressions.

Regressions which are regarded as allowable (not blocking):
 test-amd64-amd64-xl-qemuu-winxpsp3  9 windows-install   fail baseline untested

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check 
fail never pass
 test-amd64-amd64-qemuu-nested-amd 16 debian-hvm-install/l1/l2  fail never pass
 test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop              fail never pass
 test-amd64-i386-libvirt-qemuu-debianhvm-amd64-xsm 10 migrate-support-check 
fail never pass
 test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop             fail never pass

version targeted for testing:
 seabios              76327b9f32a009245c215f4a3c5d58a01b5310ae
baseline version:
 seabios              948f3c9b5f74f265bd171ee367a632a8f7c81f68

Last test of basis    38383  2015-11-29 07:20:01 Z   23 days
Testing same since    38549  2015-12-22 02:02:51 Z    0 days    1 attempts

People who touched revisions under test:
  Marcel Apfelbaum <marcel@xxxxxxxxxx>
  Michael S. Tsirkin <mst@xxxxxxxxxx>
  Stefan Berger <stefanb@xxxxxxxxxxxxxxxxxx>

 build-amd64-xsm                                              pass    
 build-i386-xsm                                               pass    
 build-amd64                                                  pass    
 build-i386                                                   pass    
 build-amd64-libvirt                                          pass    
 build-i386-libvirt                                           pass    
 build-amd64-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-xl-qemuu-debianhvm-amd64-xsm                pass    
 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-ovmf-amd64                         pass    
 test-amd64-i386-xl-qemuu-ovmf-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                     pass    
 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 76327b9f32a009245c215f4a3c5d58a01b5310ae
Author: Marcel Apfelbaum <marcel@xxxxxxxxxx>
Date:   Mon Dec 7 14:05:14 2015 +0200

    fw/pci: do not automatically allocate IO region for PCIe bridges
    PCIe downstream ports (Root Ports and switches Downstream Ports) appear
    to firmware as PCI-PCI bridges and a 4K IO space is allocated for them
    even if there is no device behind them requesting IO space,
    all that for hotplug purpose.
    However, PCIe devices can work without IO, so there is no need
    to allocate IO space for hotplug.
    Acked-by: Michael S. Tsirkin <mst@xxxxxxxxxx>
    Signed-off-by: Marcel Apfelbaum <marcel@xxxxxxxxxx>

commit 320df85010401c6d3ee189a54c63b937d1dcade9
Author: Stefan Berger <stefanb@xxxxxxxxxxxxxxxxxx>
Date:   Mon Nov 30 11:14:19 2015 -0500

    tpm: Add a menu for TPM configuration
    This patch adds an new menu entry to the main menu. This menu item enables
    the user to enter a TPM control menu which allows control of those aspects
    of the TPM's state that can only be controlled while in the firmware
    and while physical presence can be asserted.
    If the machine has a TPM, the boot menu will look as follows, with
    the new menu item accessible by pressing the 't' key.
    Select boot device:
    1. ata0-1: QEMU HARDDISK ATA-7 Hard-Disk (6144 MiBytes)
    2. Legacy option rom
    3. iPXE (PCI 00:03.0)
    t. TPM Menu
    Upon pressing t the TPM submenu will be shown:
    The Trusted Platform Module (TPM) is a hardware device in this machine.
    It can help verify the integrity of system software.
    The current state of the TPM is:
      Enabled and active
      Ownership has not been taken
      A user can take ownership of the TPM
    Available options are:
     d. Disable the TPM
     v. Deactivate the TPM
     p. Prevent installation of an owner
    If no change is desired or if this menu was reached by mistake, press ESC to
    reboot the machine.
    The TPM menu only shows those options that are currently accessible 
    the state of the TPM.
    The patch adds several functions for sending those messages to the TPM
    required for supporting those menu items.
    Signed-off-by: Stefan Berger <stefanb@xxxxxxxxxxxxxxxxxx>

commit 4cdbc4105499f9ec872fff929e9ab5296b294903
Author: Stefan Berger <stefanb@xxxxxxxxxxxxxxxxxx>
Date:   Mon Nov 30 11:14:18 2015 -0500

    tpm: Check length parameter of the array
    Check the length parameter that indicates the length of the array
    for whether it has a minimum value of 0x200.
    Signed-off-by: Stefan Berger <stefanb@xxxxxxxxxxxxxxxxxx>

commit 15f192fbc765ce364bc93cd6c6c974a5bb32b854
Author: Stefan Berger <stefanb@xxxxxxxxxxxxxxxxxx>
Date:   Mon Nov 30 11:14:17 2015 -0500

    tpm: Remove check for working TPM from TPM interrupt handler
    Remove the check for a working TPM from the TPM interrupt handler. This then
    allows the individual API calls to return information even if the TPM was 
    working correctly. Some API calls will still run into the check.
    Signed-off-by: Stefan Berger <stefanb@xxxxxxxxxxxxxxxxxx>

Xen-devel mailing list



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