From: Rick Gonzalez <rcgneo@us.ibm.com>
To: Xen Developers <xen-devel@lists.xensource.com>
Subject: Daily Xen-HVM Build Testing: cs11391
Date: Tue, 05 Sep 2006 16:59:09 -0500 [thread overview]
Message-ID: <44FDF32D.6030100@us.ibm.com> (raw)
changeset: 11391:2017f6e92bf8
tag: tip
user: tdeegan@york.uk.xensource.com
date: Thu Aug 31 08:46:28 2006 +0100
summary: [XEN] Fix shadow linear-mapping recopy code for SMP PAE HVM
on 64bit Xen.
Hardware: x460
******************** x86_32(no PAE): ***************************
* dom0: SLES10 GM
* dom0 boots fine
* xend starts without problem
--- Linux HVM domain status: ---
* Xm-test completes.
* Able to boot multiple HVM domains
ISSUES:
* 10 fails on xm-test. Network failures
SUMMARY:
Xm-test execution summary:
PASS: 61
FAIL: 10
XPASS: 0
XFAIL: 3
Details:
FAIL: 16_create_smallmem_neg
Starting a console with 16 MB passed, expected test to fail
XFAIL: 02_network_local_ping_pos
ping loopback failed for size 65507. ping eth0 failed for size
1 48 64 512 1440 1500 1505 4096 4192 32767 65507.
FAIL: 03_network_local_tcp_pos
TCP hping2 over eth0 failed for size 1 48 64 512 1440 1448
1500 1505 4096 4192 32767 65495.
FAIL: 04_network_local_udp_pos
UDP hping2 over eth0 failed for size 1 48 64 512 1440 1448
1500 1505 4096 4192 32767 65495.
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 1 48 64 512 1440 1500 1505 4096 4192
32767 65507.
FAIL: 12_network_domU_tcp_pos
TCP hping2 failed for size 1 48 64 512 1440 1500 1505 4096
4192 16384 24567 32767 65495.
FAIL: 13_network_domU_udp_pos
UDP hping2 failed for size 1 48 64 512 1440 1500 1505 4096
4192 32767 65495.
********************** x86_64: *********************************
* dom0: SLES10 GM
* dom0 boots fine
* xend starts without problems
--- Linux HVM domain status: ---
* Xm-test completes
* Able to boot multiple HVM domains
ISSUES:
* 11 xm-tests failing. Network failures
SUMMERY:
Xm-test execution summary:
PASS: 61
FAIL: 10
XPASS: 0
XFAIL: 3
Details:
FAIL: 16_create_smallmem_neg
Starting a console with 16 MB passed, expected test to fail
XFAIL: 02_network_local_ping_pos
ping loopback failed for size 65507. ping eth0 failed for size
1 48 64 512 1440 1500 1505 4096 4192 32767 65507.
FAIL: 03_network_local_tcp_pos
TCP hping2 over eth0 failed for size 1 48 64 512 1440 1448
1500 1505 4096 4192 32767 65495.
FAIL: 04_network_local_udp_pos
UDP hping2 over eth0 failed for size 1 48 64 512 1440 1448
1500 1505 4096 4192 32767 65495.
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 1 48 64 512 1440 1500 1505 4096 4192
32767 65507.
FAIL: 12_network_domU_tcp_pos
TCP hping2 failed for size 1 48 64 512 1440 1500 1505 4096
4192 16384 24567 32767 65495.
FAIL: 13_network_domU_udp_pos
UDP hping2 failed for size 1 48 64 512 1440 1500 1505 4096
4192 32767 65495.
NOTE: Contact me if you would like to see all the output files.
regards,
------------------------
Rick Gonzalez
Linux Technology Center
IBM Corporation
Phone#: 512-838-0623
reply other threads:[~2006-09-05 21:59 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44FDF32D.6030100@us.ibm.com \
--to=rcgneo@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.