From: "Michael S. Tsirkin" <mst@redhat.com>
To: Amos Kong <akong@redhat.com>
Cc: pradeep <psuriset@linux.vnet.ibm.com>,
Lucas Meneghel Rodrigues <lmr@redhat.com>,
autotest@test.kernel.org, kvm@vger.kernel.org
Subject: Re: Network Patch set V4
Date: Tue, 12 Oct 2010 15:52:30 +0200 [thread overview]
Message-ID: <20101012135230.GC26642@redhat.com> (raw)
In-Reply-To: <20101012072305.GA2073@z>
On Tue, Oct 12, 2010 at 03:23:05PM +0800, Amos Kong wrote:
> On Mon, Oct 11, 2010 at 08:09:27PM +0530, pradeep wrote:
> > Hi Lucas, i covered below tests on RHEL 5.5 , RHEL 6 guests with vhost
> > enbled. Please find the below errors and cause for errros.
> >
> > I also attached few other test cases can be added to out TODO list of
> > network patchset. I am working on couple of these issues.
> >
> > 1. Nice_promisc:
> > -----------------
> > With RHEL 5.5: PASS
>
> ...
>
>
> Thanks for your feedback, I will re-test them with rhel5/6 and reply the test result.
>
>
> > -----------------------------------------------------------------------------
> >
> >
> > We may include below tests to for Network Patch set:
> > I am working on couple of issues among below mentioned.
> >
> > Ping6 testing
> >
> > * ping6 with various message sizes guest to/from local/remote host
> > using link-local addresses
> > By default IPv6 seems to be disabled on virbr0. Enable it by
> > doing
> >
> > NIC bonding test :
> >
> > https://fedoraproject.org/wiki/QA:Testcase_Virtualization_Nic_Bonding
>
> I have a draft patch for bonding testing, will improve and send it to mailist.
>
> > NFS testing
> >
> > * create NFS server on guest, mount dir on host, copy and delete
> > files, do reverse on host
> >
> > Setting and unsetting ethernet adapters.
> >
> > set_link name [up|down]
>
> I only wrote a testcases, didn't automate it, could you help to review ?
>
> Steps:
> 1. boot up a guest with virtio_nic
> 2. login guest through serial
> 3. transfer a big file from guest to host
> guest) # scp a.out $host_ip:~
> 4. put down link by monitor
> qemu) # set_link $nic_model.0 down
> 5. try to capture date by tcpdump
> host)# tcpdump port $scp_port and src $guest_ip -i $tap
> 6. put up link by monitor
> qemu) set_link $nic_model.0 down
> 7. try to capture date by tcpdump
> host)# tcpdump port $scp_port and src $guest_ip -i $tap
> 8. transfer a big file from host to guest
> host) # scp a.out $guest_ip:~
I think we should use something simpler, like ping
guest-host and host-guest at the same time.
> 9. put down link by monitor
> qemu) # set_link $nic_model.0 down
> 10. try to capture date by tcpdump
> guest)# tcpdump port $scp_port and dest $guest_ip -i eth0
> 11. put up link by monitor
> qemu) set_link $nic_model.0 down
> 12. try to capture date by tcpdump
> host)# tcpdump port $scp_port and dest $guest_ip -i eth0
>
> Expected Results:
> 4. it should not capture nothing
> 6. it should capture some packets
> 10. it should not capture nothing
> 12. it should capture some packets
next prev parent reply other threads:[~2010-10-12 13:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-11 14:39 Network Patch set V4 pradeep
2010-10-12 7:23 ` Amos Kong
2010-10-12 13:52 ` Michael S. Tsirkin [this message]
2010-10-13 11:18 ` pradeep
2010-10-13 11:12 ` pradeep
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=20101012135230.GC26642@redhat.com \
--to=mst@redhat.com \
--cc=akong@redhat.com \
--cc=autotest@test.kernel.org \
--cc=kvm@vger.kernel.org \
--cc=lmr@redhat.com \
--cc=psuriset@linux.vnet.ibm.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.