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

[Xen-devel] Daily Xen Builds


  • To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "David F. Barrera" <dfbp@xxxxxxxxxx>
  • Date: Tue, 09 May 2006 13:08:38 -0500
  • Delivery-date: Tue, 09 May 2006 11:09:05 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>


May 9, 2006, using xen-unstable changeset:

changeset:   9960:1e3977e029fd
tag:         tip
user:        cl349@xxxxxxxxxxxxxxxxxxxx
date:        Mon May  8 13:21:41 2006 +0100
summary:     Fix PAE build: add CONFIG_I2O_EXT_ADAPTEC_DMA64=y to 
linux-defconfig_xen_x86_32.

x86_32 (no PAE support)

 * SLES 9 SP2 on IBM xSeries 235(512MB RAM)
 * Builds and boots without problems
 * Able to create fully functional guest domains
 * Ran xm-test on all boxes

 ISSUES:

x86_32 (PAE)

   * SLES 9 SP2 on xSeries 335 and HS20 Blade 8843and FC4 on IBM
xSeries 335s * Builds and boots without problems
   * Able to create fully functional guest domains
   * Ran xm-test on all boxes

 ISSUES:

x86_64 (SLES 9 SP2 IBM HS20 Blades 8843 41U)

 * Builds and boots without problems
 * Able to create fully functional guest domains
 * Ran xm-test on all boxes

ISSUES:
--XM-TEST Results--

SUMMARY:
           Platform | PASS | FAIL | XPASS | XFAIL |
---------------------+------+------+-------+-------+
hs20.1.sles9-x86_64 |  107 |    8 |     0 |     3 |
hs20.rhel4-x86_32pae |  107 |    8 |     0 |     3 |
    x235sles9nonpae |   96 |   18 |     0 |     3 |
   x335sles9_pae4gb |   74 |   41 |     0 |     3 |

--
Regards,

David F Barrera
Linux Technology Center
Systems and Technology Group, IBM

"The wisest men follow their own direction. "
                                                      Euripides


Xm-test execution summary:
  PASS:  107
  FAIL:  8
  XPASS: 0
  XFAIL: 3


Details:

 FAIL: 01_block_attach_device_pos 
         block-attach failed device did not switch to Connected state

 FAIL: 02_block_attach_file_device_pos 
         block-attach failed device did not switch to Connected state

 FAIL: 04_block_attach_device_repeatedly_pos 
         Device is not actually attached to domU

 FAIL: 05_block_attach_and_dettach_device_repeatedly_pos 
         block-attach failed device did not switch to Connected state

 FAIL: 01_enforce_dom0_cpus_basic_pos 
         /proc/cpuinfo says xend didn't enforce dom0_cpus (3 != 1)

XFAIL: 02_network_local_ping_pos 
         ping loopback failed for size 65507. ping eth0 failed for size 65507.

XFAIL: 05_network_dom0_ping_pos 
         Ping to dom0 failed for size 65507.

XFAIL: 11_network_domU_ping_pos 
         Ping failed for size 65507.

Xm-test execution summary:
  PASS:  107
  FAIL:  8
  XPASS: 0
  XFAIL: 3


Details:

 FAIL: 01_block_attach_device_pos 
         block-attach failed device did not switch to Connected state

 FAIL: 02_block_attach_file_device_pos 
         block-attach failed device did not switch to Connected state

 FAIL: 04_block_attach_device_repeatedly_pos 
         Device is not actually attached to domU

 FAIL: 05_block_attach_and_dettach_device_repeatedly_pos 
         block-attach failed device did not switch to Connected state

 FAIL: 01_migrate_localhost_pos 
         xm migrate returned invalid 256 != 0

XFAIL: 02_network_local_ping_pos 
         ping loopback failed for size 65507. ping eth0 failed for size 65507.

XFAIL: 05_network_dom0_ping_pos 
         Ping to dom0 failed for size 65507.

XFAIL: 11_network_domU_ping_pos 
         Ping failed for size 65507.

Xm-test execution summary:
  PASS:  96
  FAIL:  18
  XPASS: 0
  XFAIL: 3


Details:

 FAIL: 01_block_attach_device_pos 
         block-attach failed device did not switch to Connected state

 FAIL: 02_block_attach_file_device_pos 
         block-attach failed device did not switch to Connected state

 FAIL: 04_block_attach_device_repeatedly_pos 
         Device is not actually attached to domU

 FAIL: 05_block_attach_and_dettach_device_repeatedly_pos 
         block-attach failed device did not switch to Connected state

 FAIL: 13_create_multinic_pos 
         (0 nics) Failed to create domain

XFAIL: 02_network_local_ping_pos 
         Failed to create domain

 FAIL: 03_network_local_tcp_pos 
         Failed to create domain

 FAIL: 04_network_local_udp_pos 
         Failed to create domain

XFAIL: 05_network_dom0_ping_pos 
         Failed to create domain

 FAIL: 06_network_dom0_tcp_pos 
         Failed to create domain

 FAIL: 07_network_dom0_udp_pos 
         Failed to create domain

XFAIL: 11_network_domU_ping_pos 
         Failed to create domain

 FAIL: 12_network_domU_tcp_pos 
         Failed to create domain

 FAIL: 13_network_domU_udp_pos 
         Failed to create domain

 FAIL: 01_network_attach_pos 
         xm network-attach returned invalid 256 != 0

 FAIL: 02_network_attach_detach_pos 
         xm network-attach returned invalid 256 != 0

 FAIL: 03_network_attach_detach_multiple_pos 
         xm network-attach returned invalid 256 != 0

 FAIL: 04_restore_withdevices_pos 
         Failed to create domain

Xm-test execution summary:
  PASS:  74
  FAIL:  41
  XPASS: 0
  XFAIL: 3


Details:

 FAIL: 01_block_attach_device_pos 
         block-attach failed device did not switch to Connected state

 FAIL: 02_block_attach_file_device_pos 
        Unknown reason

 FAIL: 04_block_attach_device_repeatedly_pos 
        Unknown reason

 FAIL: 05_block_attach_and_dettach_device_repeatedly_pos 
         block-attach failed device did not switch to Connected state

 FAIL: 07_block_attach_baddevice_neg 
        Unknown reason

 FAIL: 08_block_attach_bad_filedevice_neg 
        Unknown reason

 FAIL: 09_block_attach_and_dettach_device_check_data_pos 
        Unknown reason

 FAIL: 12_block_attach_shared_domU 
        Unknown reason

 FAIL: 01_block-destroy_btblock_pos 
        Unknown reason

 FAIL: 06_block-destroy_check_list_pos 
        Unknown reason

 FAIL: 01_block-list_pos 
        Unknown reason

 FAIL: 03_block-list_anotherbd_pos 
        Unknown reason

 FAIL: 01_create_basic_pos 
        Unknown reason

 FAIL: 11_create_concurrent_pos 
        Unknown reason

 FAIL: 12_create_concurrent_stress_pos 
        Unknown reason

 FAIL: 13_create_multinic_pos 
        Unknown reason

 FAIL: 01_destroy_basic_pos 
        Unknown reason

 FAIL: 07_destroy_stale_pos 
        Unknown reason

 FAIL: 01_enforce_dom0_cpus_basic_pos 
         /proc/cpuinfo says xend didn't enforce dom0_cpus (2 != 1)

 FAIL: 04_list_goodparm_pos 
        Unknown reason

 FAIL: 01_memset_basic_pos 
        Unknown reason

 FAIL: 03_memset_random_pos 
        Unknown reason

 FAIL: 04_memset_smallmem_pos 
        Unknown reason

 FAIL: 01_migrate_localhost_pos 
        Unknown reason

XFAIL: 02_network_local_ping_pos 
        Unknown reason

 FAIL: 04_network_local_udp_pos 
        Unknown reason

XFAIL: 05_network_dom0_ping_pos 
         Ping to dom0 failed for size 65507.

 FAIL: 06_network_dom0_tcp_pos 
        Unknown reason

 FAIL: 07_network_dom0_udp_pos 
        Unknown reason

XFAIL: 11_network_domU_ping_pos 
         Ping failed for size 65507.

 FAIL: 13_network_domU_udp_pos 
        Unknown reason

 FAIL: 01_network_attach_pos 
        Unknown reason

 FAIL: 02_network_attach_detach_pos 
        Unknown reason

 FAIL: 01_pause_basic_pos 
        Unknown reason

 FAIL: 01_reboot_basic_pos 
        Unknown reason

 FAIL: 01_restore_basic_pos 
        Unknown reason

 FAIL: 03_save_bogusfile_neg 
        Unknown reason

 FAIL: 01_shutdown_basic_pos 
        Unknown reason

 FAIL: 02_sysrq_sync_pos 
        Unknown reason

 FAIL: 03_sysrq_withreboot_pos 
        Unknown reason

 FAIL: 01_unpause_basic_pos 
        Unknown reason

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

 


Rackspace

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