Daily Xen Builds

["David F. Barrera" <dfbp@us.ibm.com>]

[-- Attachment #1: Type: text/plain, Size: 1306 bytes --]

April 20, 2006, using xen-unstable changeset:

changeset:   9671:72f9c751d3ea
tag:         tip
user:        kaf24@firebug.cl.cam.ac.uk
date:        Wed Apr 19 12:32:20 2006 +0100
summary:     Replace &foo[0] with foo where the latter see

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)

  * RHEL 4 on IBM HS20 Blade 8843           
  * 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 Blade 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 |  104 |    9 |     0 |     3 |
hs20.rhel4-x86_32pae |  108 |    6 |     0 |     3 |
          x335fc4pae |  109 |    5 |     0 |     3 |

-- 
Regards,

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

"The wisest men follow their own direction. "
                                                       Euripides



[-- Attachment #2: hs20.1.sles9-x86_64.report --]
[-- Type: text/plain, Size: 891 bytes --]

Xm-test execution summary:
  PASS:  104
  FAIL:  9
  XPASS: 0
  XFAIL: 3


Details:

 FAIL: 01_block_attach_device_pos 
	 Device is not actually connected to the domU

 FAIL: 02_block_attach_file_device_pos 
	 Device is not actually connected to the domU

 FAIL: 04_block_attach_device_repeatedly_pos 
	 Device is not actually attached to domU

 FAIL: 05_block_attach_and_dettach_device_repeatedly_pos 
	 Failed to attach block device /proc/partitions does not show that!

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

 FAIL: 01_memset_basic_pos 
	 DomU reported incorrect memory amount 59 MB

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.


[-- Attachment #3: hs20.rhel4-x86_32pae.report --]
[-- Type: text/plain, Size: 597 bytes --]

Xm-test execution summary:
  PASS:  108
  FAIL:  6
  XPASS: 0
  XFAIL: 3


Details:

 FAIL: 15_create_smallmem_pos 
	 Starting a console with 16 MB failed domain dies immediately!

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

 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.


[-- Attachment #4: x335fc4pae.report --]
[-- Type: text/plain, Size: 524 bytes --]

Xm-test execution summary:
  PASS:  109
  FAIL:  5
  XPASS: 0
  XFAIL: 3


Details:

 FAIL: 15_create_smallmem_pos 
	 Starting a console with 16 MB failed domain dies immediately!

 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.


[-- Attachment #5: Type: text/plain, Size: 138 bytes --]

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