On Wed, 2010-09-29 at 17:03 +0530, pradeep wrote:
> On Wed, 29 Sep 2010 08:07:19 -0300
> Lucas Meneghel Rodrigues <[email protected]> wrote:
>
>
> >
> > 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.
> >
>
> from guest i tried to remove arp entry from cache as mentioned in code.
>
> arp -d 10.168.0.6 -i kvmbr0
>
> It never worked for me. I guess this is the reason for this error.
I spend some time on this test today and got it working. The bottom line
is, we add a static arp cache entry for:
(IP of vm + MAC of vm interface) + corresponding tap interface
^ Guest side info ^ Host side info
If you issue a ifconfig on host while tests are running, you'll see the
tap interface:
virtio_0_5900 Link encap:Ethernet HWaddr 8A:65:51:1F:6A:95
inet6 addr: fe80::8865:51ff:fe1f:6a95/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:65520 Metric:1
RX packets:560511 errors:0 dropped:0 overruns:0 frame:0
TX packets:565406 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:36697168035 (34.1 GiB) TX bytes:36697563087 (34.1 GiB)
Then, if you run:
arp -s 10.16.74.148 9a:0b:5d:7a:e6:eb -i virtio_0_5900
It will work. Of course, the actual values of the ip and MAC addresses
have to be checked on guest side.
I have rebased this test and re-sent. You might try it, but now I think
it's going to work for you, as it did for me.
Moving closer to the completion of this patchset,
Lucas
--
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
