WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] [PATCH 0/4] [XMTEST] Network tests

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [PATCH 0/4] [XMTEST] Network tests
From: James Dykman <dykman@xxxxxxxxxx>
Date: Thu, 8 Dec 2005 17:10:33 -0500
Delivery-date: Thu, 08 Dec 2005 22:11:25 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
Importance: Normal
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Sensitivity:
This is the start of a series of network tests for xm-test. I'd like to 
get comments and/or get these into the tree
before doing similar tests for TCP/UDP/etc.

The tests are all doing simple pings of various sizes in different 
configurations of domUs:
Test 02 uses a single domU, and just pings its lo and eth0 
Test 05 uses a single domU, pinging from the domU to dom0
Test 11 uses two domUs, pinging from one to the other.

None of them pass:

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

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

REASON: Ping failed for size 32767 65507.
XFAIL: 11_network_domU_ping_pos.test

Test 02: Pings fail consistently once the ping size is bigger than 48485 
(ping -s 48486 fails).
Tests 05 and 11: The larger pings drop the first few with reassembly 
timeouts reported by the domU. After a few drops, 
     the pings complete. Since the tests only do one ping of each size, 
they fail.

All three tests have been exercised using -bridge, -route, and -nat 
configurations (-nat requires the vif-nat patch I sent earlier today).
The same failures occur in each configuration.

To start things off, here is the makefile plumbing:

Signed-off-by: Jim Dykman <dykman@xxxxxxxxxx>

Jim

Attachment: nn8.0
Description: Binary data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>