From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lucas Meneghel Rodrigues Subject: Re: [PATCH 07/18] KVM test: Add a subtest jumbo Date: Wed, 29 Sep 2010 08:07:19 -0300 Message-ID: <1285758439.2505.9.camel@freedom> References: <1285627444-2732-1-git-send-email-lmr@redhat.com> <1285627444-2732-8-git-send-email-lmr@redhat.com> <20100929121233.430ac5ef@skywalker> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: autotest@test.kernel.org, kvm@vger.kernel.org, mst@redhat.com, akong@redhat.com, jasowang@redhat.com, mgoldish@redhat.com To: pradeep Return-path: Received: from mx1.redhat.com ([209.132.183.28]:11891 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752008Ab0I2LHZ (ORCPT ); Wed, 29 Sep 2010 07:07:25 -0400 In-Reply-To: <20100929121233.430ac5ef@skywalker> Sender: kvm-owner@vger.kernel.org List-ID: On Wed, 2010-09-29 at 12:12 +0530, pradeep wrote: > O > > > + Test the RX jumbo frame function of vnics: > > + > > + 1) Boot the VM. > > + 2) Change the MTU of guest nics and host taps depending on the > > NIC model. > > + 3) Add the static ARP entry for guest NIC. > > + 4) Wait for the MTU ok. > > + 5) Verify the path MTU using ping. > > + 6) Ping the guest with large frames. > > + 7) Increment size ping. > > + 8) Flood ping the guest with large frames. > > + 9) Verify the path MTU. > > + 10) Recover the MTU. > > + > > Thanks for new set of patches. > > Jumbo fails again since MTU is not as expected even. Not as expected even after 10 seconds. The idea is to change the MTU, wait a little while and check it again. Yes, I also got this problem doing my test of the patch. Need to check why that is happening. > 02:46:14 INFO | Removing the temporary ARP entry > 02:46:14 DEBUG| Running 'arp -d 10.168.0.6 -i kvmbr0' > 02:46:14 ERROR| Test failed: TestError: MTU is not as expected even > after 10 seconds 02:46:14 DEBUG| Postprocessing VM 'vm2'... > 02:46:14 DEBUG| VM object found in environment > 02:46:14 DEBUG| Terminating screendump thread... > > > > + logging.info("Removing the temporary ARP entry") > > + utils.run("arp -d %s -i %s" % (ip, bridge)) > > > > I am just trying to understand, why are we trying to remove same > guest ip arp cache. For sure host ip will be there in arp cache. > Try with host ip @eth*. It works fine for me. > > > > Thanks > Pradeep > >