public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: Nils Cant <nils.cant@kangaroot.net>,
	Gleb Natapov <gleb@redhat.com>,
	kvm@vger.kernel.org, libvir-list@redhat.com
Subject: Re: KVM doesn't send an arp announce after live migrating a domain
Date: Wed, 25 Aug 2010 11:52:32 +0100	[thread overview]
Message-ID: <20100825105232.GE13337@redhat.com> (raw)
In-Reply-To: <4C74F313.6040604@redhat.com>

On Wed, Aug 25, 2010 at 01:40:19PM +0300, Avi Kivity wrote:
>  On 08/25/2010 12:21 PM, Nils Cant wrote:
> >On 08/25/2010 10:38 AM, Gleb Natapov wrote:
> >>qemu sends gratuitous ARP after migration. Check forward delay 
> >>setting on your
> >>bridge interface. It should be set to zero.
> >>
> >
> >Aha! That fixed it. Turns out that debian bridge-utils sets the 
> >default to 15 for bridges.
> >Manually setting it to 0 with 'brctl setfd br0 0' or setting the 
> >'bridge_fd' parameter to 0 in /etc/network/interfaces solves the issue.
> >
> 
> I think libvirt is doing something about this, copying list for further 
> info.

libvirt doesn't set a policy for this. It provides an API for 
configuring host networking, but we don't override the kernel's
forward delay policy, since we don't presume that all bridges 
are going to have VMs attached. In any case the API isn't available
for Debian yet, since no one has ported netcf to Debian, so I 
assume the OP set bridging up manually. The '15' second default is
actually a kernel level default IIRC. 

The two main host network configs recommended for use with libvirt+KVM
(either NAT or bridging) are documented here:

  http://wiki.libvirt.org/page/Networking

Regards,
Daniel
-- 
|: Red Hat, Engineering, London    -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://deltacloud.org :|
|: http://autobuild.org        -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

  reply	other threads:[~2010-08-25 10:52 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
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 [this message]
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=20100825105232.GE13337@redhat.com \
    --to=berrange@redhat.com \
    --cc=avi@redhat.com \
    --cc=gleb@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=libvir-list@redhat.com \
    --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