Xen project Mailing List

[Xen-devel] Daily Xen Builds

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>

From: David F Barrera <dfbp@xxxxxxxxxx>

Date: Fri, 05 May 2006 14:23:27 -0500

Delivery-date: Fri, 05 May 2006 12:23:50 -0700

List-id: Xen developer discussion <xen-devel.lists.xensource.com>

May 5, 2006, using xen-unstable changeset: bl2-1:/tmp/xen-unstable.hg # hg tip changeset: 9925:1a84eec74331 tag: tip user: kaf24@xxxxxxxxxxxxxxxxxxxx date: Thu May 4 05:24:19 2006 +0100 summary: Change Mini-OS so that it uses stddef.h to define size_t and x86_32 (no PAE support) * SLES 9 SP2 on IBM xSeries 235(512MB RAM) * Builds and boots without problems * 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

* Ran xm-test on all boxes ISSUES: x86_64 (SLES 9 SP2 IBM HS20 Blades 8843 41U) * Builds and boots without problems * Ran xm-test on all boxes

ISSUES:

--XM-TEST Results-- SUMMARY: Platform | PASS | FAIL | XPASS | XFAIL | ---------------------+------+------+-------+-------+ hs20.1.sles9-x86_64 | 105 | 10 | 0 | 3 | hs20.rhel4-x86_32pae | 105 | 10 | 0 | 3 | x235sles9nonpae | 105 | 9 | 0 | 3 | x335fc4pae | 106 | 9 | 0 | 3 | x335sles9_pae4gb | 107 | 8 | 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: 105 FAIL: 10 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 FAIL: 03_memset_random_pos Expected 63 MB, domU reported 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.

Xm-test execution summary: PASS: 105 FAIL: 10 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: 13_create_multinic_pos (8 nics) Console didn't respond probably crashed! 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.

Xm-test execution summary: PASS: 105 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! 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 1 48 64 512 1440 1500 1505 4096 4192 32767 65507. FAIL: 06_network_dom0_tcp_pos TCP hping2 to dom0 failed for size 1 48 64 512 1440 1500 1505 4096 4192 32767 65495. FAIL: 07_network_dom0_udp_pos UDP hping2 to dom0 failed for size 1 48 64 512 1440 1500 1505 4096 4192 32767 65495. XFAIL: 11_network_domU_ping_pos Ping failed for size 65507.

Xm-test execution summary: PASS: 106 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: 13_create_multinic_pos (9 nics) Console didn't respond probably crashed! 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 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 (2 != 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.

_______________________________________________ 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.