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.
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
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
