From: Michael Tokarev <mjt@tls.msk.ru>
To: Nils Cant <nils.cant@kangaroot.net>
Cc: kvm@vger.kernel.org
Subject: Re: KVM doesn't send an arp announce after live migrating a domain
Date: Wed, 25 Aug 2010 12:37:21 +0400 [thread overview]
Message-ID: <4C74D641.6020907@msgid.tls.msk.ru> (raw)
In-Reply-To: <4C74CBB0.7080203@kangaroot.net>
25.08.2010 11:52, Nils Cant wrote:
> Hey guys,
>
> not sure if this is a bug or a feature request. It's just something
> we've noticed and are having problems with.
>
> We're using the qemu-kvm lenny-backports package on Debian 5.0.5.
>
> When doing a live migration from the virsh shell, the server in question
> becomes unreachable because the ARP cache on our switches still thinks
> the server is on another port.
>
> As soon as the server sends out some traffic, such as a ping, the ARP
> cache get's updated as expected. If it does nothing, the server remains
> unreachable until the ARP cache expires on the switches. (in our case 4
> hours)
>
> We would like to be able to do live migration for customer machines on
> which we have no access, so we really need KVM to send out an ARP
> announcement/gratuitous ARP when doing a live migration.
>
> Could anyone tell me if this is a bug in KVM, libvirt, or the debian
> qemu-kvm package? (or if I'm doing something wrong? :-) )
It's probably a bug in your understanding ;)
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.
These ARPs should be sent by guest. Another question is
how to force/tell it to do so, and this is, again, depends
on the guest operating system, number of addresses assigned
to the interface and so on.
The mechanism to trigger it may be based on link status
of the card for example - kvm may lower it for a few ms
right after migration, to indicate that the "cord" were
un-plugged and plugged back, to force the guest to do
whatever it needs to do... But that's just a possibility
for future development.
/mjt
next prev parent reply other threads:[~2010-08-25 8:37 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-25 7:52 KVM doesn't send an arp announce after live migrating a domain Nils Cant
2010-08-25 8:37 ` Michael Tokarev [this message]
2010-08-25 8:43 ` Gleb Natapov
2010-08-25 10:51 ` Michael Tokarev
2010-08-25 10:59 ` Gleb Natapov
2010-08-25 11:07 ` Gleb Natapov
2010-08-25 11:36 ` Michael Tokarev
2010-08-25 12:15 ` Gleb Natapov
2010-08-25 8:38 ` Gleb Natapov
2010-08-25 9:21 ` Nils Cant
2010-08-25 10:40 ` Avi Kivity
2010-08-25 10:52 ` Daniel P. Berrange
2010-08-25 11:05 ` Avi Kivity
2010-08-25 11:15 ` Daniel P. Berrange
2010-08-25 11:30 ` Avi Kivity
2010-08-25 11:36 ` Daniel P. Berrange
2010-08-25 11:38 ` Avi Kivity
2010-08-25 11:42 ` Daniel P. Berrange
2010-08-25 11:59 ` Avi Kivity
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=4C74D641.6020907@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=kvm@vger.kernel.org \
--cc=nils.cant@kangaroot.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox