[Top] [All Lists]
[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: Fri, 23 Jun 2006 14:52:54 -0500
  • Delivery-date: Fri, 23 Jun 2006 12:54:46 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
June 23, 2006, using xen-unstable changeset:

changeset:   10470:411a3c01bb40
tag:         tip
user:        kaf24@xxxxxxxxxxxxxxxxxxxx
date:        Tue Jun 20 12:51:46 2006 +0100
summary:     [XEN] Xen always relinquishes VGA console to domain0 when domain0

x86_32 (SLES 9 SP2 and FC4 on IBM xSeries 335(512MB RAM)and IBM HS20 Blades 
8843 41U)

* Builds and boots without problems
* Ran xm-test on all boxes

ISSUES:

x86_64 (SLES 9 IBM HS20 Blades 8843 41U)

* Builds and boots without problems
* Ran xm-test on all boxes

ISSUES:
XM-TEST Results *: Platform | PASS | FAIL | XPASS | XFAIL | 
---------------------+------+------+-------+-------+
hs20.1.sles9-x86_64 |  107 |   10 |     0 |     3 |
  hs20.rhel4-x86_32 |   92 |   20 |     0 |     3 |
          x235sles9 |  101 |   10 |     0 |     3 |
            x335fc4 |  101 |   11 |     0 |     3 |
          x335sles9 |  100 |   11 |     0 |     3 |

* With Harry's patch


--

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:  10
  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: 03_memset_random_pos 
         Timed out waiting for console

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 1 48 64 512 1440 1500 1505 4096 4192 32767 65507.

 FAIL: 12_network_domU_tcp_pos 
         TCP hping2 failed for size 16384 24567 32767 65495.

 FAIL: 13_network_domU_udp_pos 
         UDP hping2 failed for size 32767 65495.


Xm-test execution summary:
  PASS:  92
  FAIL:  20
  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 
         (5 nics) Failed to create domain

 FAIL: 14_create_blockroot_pos 
         Failed to create domain

 FAIL: 03_memset_random_pos 
         Timed out waiting for console prompt

 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.

 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


Xm-test execution summary:
  PASS:  101
  FAIL:  10
  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: 03_memset_random_pos 
         Timed out waiting for console command

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 1 48 64 512 1440 1500 1505 4096 4192 32767 65507.

 FAIL: 12_network_domU_tcp_pos 
         TCP hping2 failed for size 16384 24567 32767 65495.

 FAIL: 13_network_domU_udp_pos 
         UDP hping2 failed for size 32767 65495.


Xm-test execution summary:
  PASS:  101
  FAIL:  11
  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: 03_memset_random_pos 
         Timed out waiting for console prompt

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.

 FAIL: 07_network_dom0_udp_pos 
         UDP hping2 to dom0 failed for size 1440 1500 1505 4096 4192.

XFAIL: 11_network_domU_ping_pos 
         Ping failed for size 1 48 64 512 1440 1500 1505 4096 4192 32767 65507.

 FAIL: 12_network_domU_tcp_pos 
         TCP hping2 failed for size 16384 24567 32767 65495.

 FAIL: 13_network_domU_udp_pos 
         UDP hping2 failed for size 32767 65495.


Xm-test execution summary:
  PASS:  100
  FAIL:  11
  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

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.

 FAIL: 06_network_dom0_tcp_pos 
         TCP hping2 to dom0 failed for size 32767.

 FAIL: 07_network_dom0_udp_pos 
         UDP hping2 to dom0 failed for size 64 512 1440 1500 1505 4096 4192 
32767.

XFAIL: 11_network_domU_ping_pos 
         Ping failed for size 1 48 64 512 1440 1500 1505 4096 4192 32767 65507.

 FAIL: 12_network_domU_tcp_pos 
         TCP hping2 failed for size 16384 24567 32767 65495.

 FAIL: 13_network_domU_udp_pos 
         UDP hping2 failed for size 32767 65495.


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

 

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.

Rackspace

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