Gleb Natapov wrote: > On Wed, Aug 25, 2010 at 12:37:21PM +0400, Michael Tokarev wrote: [] >> Jokes aside, the thing is that kvm does not know what is >> an ARP and what is an IP address. It emulates a hardware >> network card, which never sends any ARP out by its own, >> it is the operating system IP stack who's doing that. >> That network card as emulated by kvm does not know what >> IP addresses are assigned to it inside the guest (there >> may be many, or may be none at all), so it just can not >> send the ARPs. >> > True. Although qemu sends gratuitous ARP the IP field there is > incorrect. It is done to update layer 2 topology, not layer 3. Actually, the more I think about that, the more it looks like a job for "external" (for the guest) piece. For example, we may teach libvirt or kvm about IP addresses the guest is using, so that kvm will send these ARPs automatically after migration has completed. It shouldn't be difficult to implement. Something like: -net nic,model=virtio,arp=1.2.3.4:5.6.7.8,mac=foo:bar or, even, -net tap,arp=...,... for the command-line interface, and/or a 'sendarp' monitor command that expects a network device and a list of ip addresses. Kvm is the most natural place to do that, I think, and it's easy to implement there too (it has the tun device which can inject packets on behalf of the guest) Yes, the configuration will be duplicated somehow, but that's not a big problem, and it will make things much more reliable. /mjt -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
