The following patch allows the network tests to pass with hvm support enabled. More specifically: 02_network_local_ping_pos.py REASON: ping loopback failed for size 65507. ping eth0 failed for size 65507. (but all other size pings work) 05_network_dom0_ping_pos.py REASON: Ping to dom0 failed for size 65507. (but all other size pings work) 11_network_domU_ping_pos.py passes 100% (even the large ping, i know the large ping is another bug but is it supposed to work or fail on this test?) Let me know if there''s anything I should change in the patch, my next step is to try to build some network tests that put a little strain on the network, the hvm image doesn''t appear to have support for ping -f so I''ll need to find another solution, any ideas? (Yes I can probably ping -f from outside the domain at it, but would be nice to have something to test the other direction, or even ssh to test that data isn''t being corrupted.) Adam Wendt IPCoast, Inc. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Hm, hping2 doesn''t appear to work on my disk image: @%@%> hping2 -c 2 127.0.0.1 [open_sockpacket] socket(): Address family not supported by protocol [main] can''t open packet socket Maybe an issue with using the 2.4 kernel or something else? Adam Wendt IPCoast, Inc. On Wed, 01 Feb 2006 12:52 , Dan Smith <danms@us.ibm.com> sent:> >AW> the hvm image doesn''t appear to have support for ping -f so I''ll >AW> need to find another solution, any ideas? > >We put hping is in the disk image for network testing, so perhaps it >can be of use? It looks like you can at least specify the interval >between pings to be a small number of microseconds, with -i uX. > >-- >Dan Smith >IBM Linux Technology Center >Open Hypervisor Team >email: danms@us.ibm.com > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Ya I definatly brought lo up first. Do you have a working 2.6 kernel + pcnet32/mii modules you could send me to test with? Adam Wendt IPCoast, Inc. On Wed, 01 Feb 2006 13:28 , Dan Smith <danms@us.ibm.com> sent:>AQ> Hm, hping2 doesn''t appear to work on my disk image: >AQ> >AQ> @%@%> hping2 -c 2 127.0.0.1 >AQ> [open_sockpacket] socket(): Address family not supported by protocol >AQ> [main] can''t open packet socket > >It seems to work on my HVM box: > > @%@%> hping2 -c 2 127.0.0.1 > HPING 127.0.0.1 (lo 127.0.0.1): NO FLAGS are set, 40 headers + 0 data > bytes > len=40 ip=127.0.0.1 ttl=64 DF id=0 sport=0 flags=RA seq=0 win=0 > rtt=0.0 ms > len=40 ip=127.0.0.1 ttl=64 DF id=1 sport=0 flags=RA seq=1 win=0 > rtt=0.0 ms > > --- 127.0.0.1 hping statistic --- > 2 packets tramitted, 2 packets received, 0% packet loss > round-trip min/avg/max = 0.0/0.0/0.0 ms > >Are you plumbing lo before attempting this? By default, lo is down >and has no IP. > >-- >Dan Smith >IBM Linux Technology Center >Open Hypervisor Team >email: danms@us.ibm.com > >_______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
AW> the hvm image doesn''t appear to have support for ping -f so I''ll AW> need to find another solution, any ideas? We put hping is in the disk image for network testing, so perhaps it can be of use? It looks like you can at least specify the interval between pings to be a small number of microseconds, with -i uX. -- Dan Smith IBM Linux Technology Center Open Hypervisor Team email: danms@us.ibm.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Nivedita Singhvi
2006-Feb-01 21:12 UTC
Re: [Xen-devel] [XM-TEST][PATCH] hvm network test fixes
Dan Smith wrote:> AW> the hvm image doesn''t appear to have support for ping -f so I''ll > AW> need to find another solution, any ideas? > > We put hping is in the disk image for network testing, so perhaps it > can be of use? It looks like you can at least specify the interval > between pings to be a small number of microseconds, with -i uX. >Yep, that was one of the reasons for the hping inclusion.. thanks, Nivedita _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
AQ> Hm, hping2 doesn''t appear to work on my disk image: AQ> AQ> @%@%> hping2 -c 2 127.0.0.1 AQ> [open_sockpacket] socket(): Address family not supported by protocol AQ> [main] can''t open packet socket It seems to work on my HVM box: @%@%> hping2 -c 2 127.0.0.1 HPING 127.0.0.1 (lo 127.0.0.1): NO FLAGS are set, 40 headers + 0 data bytes len=40 ip=127.0.0.1 ttl=64 DF id=0 sport=0 flags=RA seq=0 win=0 rtt=0.0 ms len=40 ip=127.0.0.1 ttl=64 DF id=1 sport=0 flags=RA seq=1 win=0 rtt=0.0 ms --- 127.0.0.1 hping statistic --- 2 packets tramitted, 2 packets received, 0% packet loss round-trip min/avg/max = 0.0/0.0/0.0 ms Are you plumbing lo before attempting this? By default, lo is down and has no IP. -- Dan Smith IBM Linux Technology Center Open Hypervisor Team email: danms@us.ibm.com _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
On Wed, Feb 01, 2006 at 12:41:10PM +0000, Adam Wendt wrote:> The following patch allows the network tests to pass with hvm support enabled. > > More specifically: > 02_network_local_ping_pos.py > REASON: ping loopback failed for size 65507. ping eth0 failed for size 65507. > (but all other size pings work) > > 05_network_dom0_ping_pos.py > REASON: Ping to dom0 failed for size 65507. > (but all other size pings work) > > 11_network_domU_ping_pos.py > passes 100% (even the large ping, i know the large ping is another bug but is it > supposed to work or fail on this test?)Applied, thank you. Could you please include a Signed-off-by: line with your patches? Thanks, Ewan. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel